Re: Building a Linux->AIX crosscompiler -- problem with libgcc_s.a

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Kai Ruottu wrote:
> I didn't use the '--with-sysroot=$sysroot' to point to the
> (unexisting) AIX5.3 C library...

What is that business? Would you have a pointer to dome f* manual I could use to educate myself? Even if the AIX C library is not freely available, I could get a hold of one, but what would I have to do with it?
Putting it below some thought-out $sysroot and pointing to it using '--with-sysroot=$sysroot'
when configuring binutils and GCC could be a good idea!
The "traditional" install place is the '$tooldir' aka '$prefix/$target', where $prefix and $target are the values given in the '--prefix=$prefix' and '--target=$target' configure options. The target binutils (with bare names) are still in the '$tooldir/bin' although the new '--with-sysroot=$sysroot' would be used to change the places for the 'include' and 'lib' from that '$tooldir' to '$sysroot/usr' ! The target binutils are executable binaries for the $host but they will handle binaries for the $target. With GCCs for embedded targets the $tooldir/include and $tooldir/lib will still keep the target headers and the target libraries, one can think them being some "data" which the binutils will handle... The reason why the '--with-sysroot=' is suggested is that there aren't just that '/usr/include' and '/usr/lib' but many other 'lib's and maybe also 'include's which will belong to the "AIX C library". The traditional install scheme doesn't cater these extra includes and libs in any way. I myself browsed the 'gcc/config/rs6000/*aix*' files and the '*_SPEC's in the config headers told there being many 'lib' directories in use in an AIX system...


[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux