I don't know which version you're using (of gcc), but one of them notes that
when configuring as a cross-compiler, to specify --use-gas or something like
that. (I also realize that it says that that doesn't matter for certain
configs, but I don't have INSTALL around right now to read it). If the
loader or 'file' is barking about a bad magic number, it sounds like
either the wrong assembler or the wrong loader is being envoked. (Or
both). I also think (but I'm probably wrong) that the as86 should be in
the same directory as cc1, cpp, ld, libgcc.a, as 'as', and, failing to
find it as that, gcc will envoke 'as' w/o the gcc directory prefix,
finding the system assembler, which will then assemble the .s file to a
sysV image. If gnu's ld is then run, it will complain about 'bad magic
number'.
Of course, I could be mistaken...
--
;abdsf;alshnt;laiwkejr;abndsf;alsdkjf;sf
Steve Rich
a;lsdkfab;wekja;sdfjh;alfdj;lkjf;lkjsadf| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Justin C. Sherrill | Re: pkgsrc bulk build and tiff |
| Jeremy Allison | Re: [RFC] Heads up on sys_fallocate() |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
| Matt Thomas | Re: Add a MAP_ALIGNED flag for mmap(2). |
| Vsevolod Stakhov | Unicode support in iso9660. |
| Jaromir Dolecek | Re: Speeding up fork/wait path |
| matthew green | re: merge of freebsd eventhandler |
git: | |
| Petr Janda | KDE and OpenSSL = Broken |
| sam | Re: Loader not found |
| Erick Perez | Re: dragonfly pdf documentation |
| Michel Talon | Re: Compatability with FreeBSD Ports [debian package tools] |
