Re: Cross gcc build problem

[Kai Ruottu <karuottu at mbnet dot fi>]

NightStrike wrote:
> On 7/10/07, David Daney <ddaney@avtrex.com> wrote:
> > If that is because you are bootstrapping a toolchain, then you should
> > disable the generation of a shared version of libgcc by supplying
> > something like --disable-shared to the GCC configure.
>
> Would you need just "disable-shared", or both that as well as
> "enable-static"?  Is specifying both required, or is that redundant?
I would interpret the "bootstrapping a toolchain" as "building the toolchain
for the first time"...  And if the toolchain is for an existing system 
target, it
also has those shared runtime libraries (the '.so' files) if it has 
those static
"development" libraries (the '.a' archives) and the startups (crt*.o).  
So the
'libc.so.6' missing from Laine is really weird and one simple explanation
can be that only the '/usr/lib' stuff was copied onto the cross host or was
unpacked from the 'glibc-devel-something.deb' package and the runtime
parts in '/lib' or 'glibc-something.deb' weren't copied onto the cross host
at all...

So copying also the shared libraries onto the cross host would be the
right action, not thinking that they don't exist!   When "bootstraping" a
toolchain the 'glibc-something' and the 'glibc-devel-something' packages
will be the "minimum glibc" to be installed!  The 'glibc-debug-something',
'glibc-prof-something' etc. extra packages are not necessary....