----- Original Message -----
From: Philip Blundell <[EMAIL PROTECTED]>
To: Bas Mevissen <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, November 10, 1999 11:55
Subject: Re: GCC 2.95.2 new patch made for cross-compiler inhibit_libc stuff
and still some questions
| >- Should I apply patches to the binutils package or use
binutils-2.9.5.x.x?
| >Did i compile the binutils right?
|
| Use 2.9.5. Yes, your compilation options were fine.
|
OK. Can I safely upgrade my native binutils for i686 too or can the two
versions (2.9.1.x.x and 2.9.5.x.x) coexist?
| >- I put everything in /opt/arm because the files of the binutils are
| >interfering with the ones installed for the native compiler. Is there an
| >elegant way to let them coexist?
|
| It should happen automatically. What are the actual problems you see?
|
I did not try it, I just looked for duplicate, different(*) files and found
them: /usr/lib/lib{bfd,opcodes,iberty}*. I understand that when you compile
a new binutils, it will read the current supported targets. But what if I
distribute it in binaire form?
(*) different from the native binutils already installed.
What I would like to do is build separate cross packages that just add files
and do not replace anything. I have to get deeper into this.
| >- Is it right to use the kernel includes the way I do? Wouldn't it be
better
| >to use a --local-include=/opt/arm/include to force using
| >/opt/arm/include/{asm,linux} for the kernel includes? In that case, I can
| >use /opt/arm/include for the glibc includes.
|
| No. The cross-compiler will look in $PREFIX/arm-linux/include and this is
| where you should put the headers.
|
Just to be sure: that's the right place for the glibc header files too? That
makes sense to me, because then you can use an other version of the
c-library for the arm cross-builds.
| >- Do I need libio? Does it really need the glibc header files? How can I
| >avoid libio from building?
|
| No, you probably don't want it. Yes, it really does need the header
files.
| The easy way to stop it building is just to delete it from your source
tree
| before running configure.
|
OK. I'll see if I can make a patch for cleanly exclude it from the build,
without removing files.
BTW. Where is libio for?
Thanks for the answers so far.
Bas.
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
++ Please use [EMAIL PROTECTED] for ++
++ kernel-related discussions. ++
