This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
By the way, I am having this problem with crosstool-0.28-rc32. (I forgot to include that critical bit of info in my first email)
I just read the crossgcc archives a little more carefully, and I saw that building an x86-64 toolchain on i386 userspace running on a 64-bit x86_64 kernel has exactly the same problem. Unfortunately glibc-2.3.2-cross-2.patch doesn't seem to be all that's required in my ppc32 userspace on ppc64 kernel setup (I just checked, and the patch definitely applied to glibc in my build tree).
As a ludicrous workaround for the moment, I put the following in /usr/local/bin/uname:
#!/bin/sh /bin/uname $@ | sed -e's/ppc64/ppc/'
and glibc successfully configures.
That workaround could be done without being root, by playing with PATH. It could even be done inside a demo-* shell script for this situation. I guess I should add something like this to the crosstool-howto...
-- My technical stuff: http://kegel.com My politics: see http://www.misleader.org for examples of why I'm for regime change
------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |