crossdev fails building glibc on amd64

Freespirit · Tux's lil' helper Joined: 14 Aug 2003 Posts: 84

Hi!

I'm geeting pretty good at getting into trouble with Gentoo, guess I'm always pushing the envelope just a little too far.... :-)

I'm trying to build a i686 cross compiler on my athlon64 based system to help out my p4 laptop when compiling.

I am using the crossdev script and will install and configure distcc once that is up and running. The problem is that crossdev is unable to successfully build glibc.

I run something like: crossdev --arch=i686 --vbinutils=2.14.90.0.8-r1 --vgcc=3.3.3 --vglibc=2.3.2-r2 --vheaders=2.4.21 --pcflags

and it fails with:

crossdev/i686/include -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DASSEMBLER -DGAS_SYNTAX -g -Wa,--noexecstack -o /var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-i686/setjmp/bsd-setjmp.o -MD -MP -MF /var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-i686/setjmp/bsd-setjmp.o.dt
../sysdeps/i386/elf/bsd-setjmp.S: Assembler messages:
../sysdeps/i386/elf/bsd-setjmp.S:71: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/bsd-setjmp.S:72: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/bsd-setjmp.S:73: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/bsd-setjmp.S:74: Error: unrecognized symbol type ""
../sysdeps/i386/elf/bsd-setjmp.S:74: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/bsd-setjmp.S:75: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/bsd-setjmp.S:78: Error: expected comma after name `' in .size directive
../sysdeps/i386/elf/bsd-setjmp.S:78: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S: Assembler messages:
../sysdeps/i386/elf/setjmp.S:63: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S:64: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S:65: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S:66: Error: unrecognized symbol type ""
../sysdeps/i386/elf/setjmp.S:66: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S:67: Warning: rest of line ignored; first ignored character is `1'
../sysdeps/i386/elf/setjmp.S:70: Error: expected comma after name `' in .size directive
../sysdeps/i386/elf/setjmp.S:70: Warning: rest of line ignored; first ignored character is `1'
make[2]: *** [/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-i686/setjmp/bsd-setjmp.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[2]: *** [/var/tmp/portage/crossdevbuild/glibc-2.3.2/buildhere-i686/setjmp/setjmp.o] Error 1
make[2]: Leaving directory `/var/tmp/portage/crossdevbuild/glibc-2.3.2/setjmp'
make[1]: *** [setjmp/subdir_lib] Error 2
make[1]: Leaving directory `/var/tmp/portage/crossdevbuild/glibc-2.3.2'
make: *** [all] Error 2

* InstallGlibcCore(): Failed to compile!

Had a look at the setjmp.S souce files, but even though I have dabbeled a little in assembler, I could not figure out what was wrong...

Have tried with several different versions og glibc, all produce the same result!

I have been unable to find any info on the forums... Any help would be greatly appreciated! :-)

Thank you! :-)

NeddySeagoon · Posted: Thu Mar 04, 2004 7:41 pm Post subject:

Freespirit,

crossdev is a bit simplistic in its approach to making cross tool chains. It takes the sources you already have, sets everything up for a cross compile, shuts its eyes and goes for it.

For many crosses this isn't enough. You need the right versions of everything with the right patches, or it breaks. See if you can google for a ready made toolchain.

I've been trying to add arm-linux to crossdev but without success so far.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Freespirit · Tux's lil' helper Joined: 14 Aug 2003 Posts: 84

Thanks for the reply!

As far as i can tell, you can get crossdev to use whatever version of glibc (and other stuff) you specify while running the script. It will download the appropriate sources if they are not already on your system!

The thing I dont get though, is that it is trying to use the same glibc that i have in my main toolchain wich compiled just fine when doing the original install... All the other things crossdev needed to build were build without problems.... Does it have something to do with the fact that my primary glibc is buildt for amd64 and the one I am trying to build with crossdev is for i686?

*really stomped on this issue*

NeddySeagoon · Posted: Thu Mar 04, 2004 10:40 pm Post subject:

Freespirit,

You have got your ARCH set to AMD64, so all the sources you have are aimed at AMD 64. Cross compiling by setting the flags is a start but not suffcient. The toolchain sources are not generic. You may well need patches for x86 that you won't have. crossdev doesnot pull these in.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Freespirit · Tux's lil' helper Joined: 14 Aug 2003 Posts: 84

Ok

Will have a go at google and see what i can come up with!

Thanks! :-)

Freespirit · Tux's lil' helper Joined: 14 Aug 2003 Posts: 84

Bump!

Still no luck! Anybody have this working?

Nikolaj

NeddySeagoon · Posted: Wed Mar 17, 2004 8:12 pm Post subject:

Freespirit,

Well, I'm still looking at the ARM tartget, but thats not what you want to hear.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Gr|ffous · n00b Joined: 27 Apr 2004 Posts: 35

I'm in exactly the same boat.
Also using amd64 trying to cross compile i686.

Exactly the same error too I'm afraid.

No updated to this yet?

Gr|ffous · n00b Joined: 27 Apr 2004 Posts: 35

I guess not

It's a shame because I have 5 other machines I'm moving over to gentoo from whitebox, and I'd really like to get them helping!

Gr|ffous

ASpott · n00b Joined: 23 Sep 2004 Posts: 33 Location: California

Very wierd, I did it and it worked fine. Of course I'm a complete noob with linux so I probably pressed some magic button without knowing it, but still, it worked fine.
_________________
"Amidst the numerous processors and network cards I have sacrificed for their sake, why is that the computer gods still continue to hate me?"

bridge_builder · n00b Joined: 08 Feb 2005 Posts: 7

I also have exactly the same error. glibc seems to be the problem.

Can anyone wise think of a shortcut - like bringing in pre-compiled glibc stuff that's been built on another machine with the target architecture?

There's got to be a solution somewhere. Googling away...