supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: yoppo@jippii.fi
Subject: Re: Cross compiling for VIA C3?
Date: Wed, 24 Nov 2004 02:58:46 +0200 (EET)	[thread overview]
Message-ID: <29331726.1101257926558.JavaMail.yoppo@jippii.fi> (raw)

>>>> Is it possible to cross-compile runit for VIA C3 system? If yes then how?
>>>> If I compile it normally on my athlon machine it doesn't work at all in 
>>> my NAT-machine (VIA).
>>> afair via c3 lack of cmov, what produce 'some' problems when 
>>> crosscompiling, what optimizations are you using?
>> The latest try was with -O2 -march=i586 -mcpu=i586 don't know if Iam 
>> missing something, but it seems like it could not be cross compiled just 
>> changing the optimizations.
>> 
>> Now after studying the compile process it seems like it makes some kind 
>> of testing on compile time but I dont have any clues how to "hack" the 
>> compile process so it would work in the VIA C3. And because I have only 
>
> Yes, the runit package's build process (just as the daemontools' one)
> includes some tests to configure system dependencies.  This includes
> three runtime tests where a test program is compiled, linked, and then
> run.  These runtime tests obviously won't work when cross-compiling.
>
> More precisely it's the targets hasshsgr.h:, iopause.h:, and uint64.h:,
> in the Makefile which test setgroups(), poll(), and the size of uint64,
> to select *.h1 or *.h2 respectively.  You can compile and link the test
> programs, and then run them on the target device to check the exit code
> and choose the correct header.
>
>> 64Mb Usb drive as a "hard drive" on that VIA I can't even test compiling 
>> the runit directly there to see if it works when not cross compiling and 
>> what the compile process does when compiling on that platform.
>
> A nfs mount could help.
>
> HTH, Gerrit.

I compiled the package now on i586 machine and the runit works fine on 
VIA. Too bad that I don't allways have this possibility so I still need 
to get the cross compiling to work. I compared the choices which was 
made during compiling and all of them are the same as on my athlon 
machine so they can't be causing the problems.

When I tried the "cross compiled" binaries only the runit-init seems to 
fail with illegal instruction other binaries works. Right now I don't 
have a clue what to try next...



__
Hanki uusi täysin ilmainen netti.fi-sähköposti, jopa 10 Mt tilaa viesteillesi!
http://webmail.saunalahti.fi/



             reply	other threads:[~2004-11-24  0:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  0:58 yoppo [this message]
2004-11-24  9:15 ` Rafal Bisingier
2005-04-28  3:44 ` Charlie Brady
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 11:24 yoppo
2004-11-19 23:44 yoppo
2004-11-22 15:08 ` Gerrit Pape
2004-12-01  5:17   ` Charlie Brady
2005-04-28  3:42 ` Charlie Brady
2004-11-19  2:29 yoppo
2004-11-19 14:19 ` Alejandro Mery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=29331726.1101257926558.JavaMail.yoppo@jippii.fi \
    --to=yoppo@jippii.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).