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]

RE: glibc-2.3.3 failing


Thanks appreciate it.

Here's a bit of the "problem".

Intention is trying to update "snapgear" distro to later gcc (3.4.2) and glibc.
So that I can build 2.6 reliably. Snapgear is currently using gcc 3.3.2 and glibc 2.2.5
which needless to say 2.6 linux is not at all happy. So here's the "plan" so far.


Use cross tool to build a armeb cross compiler thats more up to date. Cross tool
does that great. We take the "build" of gcc binary and copy to /usr/local since snapgear
and developers using snapgear expect it there. with that snapgear can compile 2.6.x (.8 or .11)
with no issue. Including with optimize on the kernel.


The issue is then I need a "snapgear" glibc. Since crosstool does some lovely "patching" of
the source, copy the "patched" source into the right place in snapgear directory. To "connect"
it into the distro, there is a "snapgear" makefile (Verses Makefile for glibc) that basically controls
the configure. So the previous configure had lots of issues since it was for 2.2.5, so I updated the
"makefile" (smallcase) to use the crosstool/glibc crosstool configure options. configure and compile
is now clean, and I belive on the tail end of this while processing the elf directory something is going
haywire. Missing "target". Funny thing is crosstool had no problem with the same source and the
same configure/build. Noticed a "optimize" option was walking "thru" the snapgear side, killed that,
far as I can tell binutil looks to be the correct versions. So its got me stumped.


So the glibc "Makefile" has no change, other than a copy of the "source" tree to another location.
Configure is the same.
Some leakage is possible for enviornment variables, been scanning looking for other things that could polute the compile,
or a version issue.


On a native compiler patchset, I'd really really love that. That helps with all the tools that cannot be built in cross.


2.6.11-rc3 or better compiles lovely.


At 10:27 AM 2/23/2005, Steve Magnani wrote:
Hi Glenn,

> I first use crosstool to create a gcc 3.4.2 armeb tool chain.
> Copy it to /usr/local on my mandrake 10.1 system. The build of
> gcc/glibc and kernel are ok. I copy the patched source from crosstool
> into my snapgear distro, and edit the makefile so the configure for glibc
> is correct compared to the original build.

I'm a little fuzzy on what you're trying to do. Are you trying to build a
native armeb toolchain? If so, I posted a patch recently which should
allow you to cross-build what you need. I used it for armv4tb-softfloat so
I would think it would work for you too.

Regards,
Steve Magnani
www.digidescorp.com


------
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]