This is the mail archive of the crossgcc@sourceware.org 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] |
Le 23/03/2010 19:52, Yann E. MORIN a écrit : > Bruno, > All, > > On Tuesday 23 March 2010 11:44:50 Bruno Tarquini wrote: > >>> That's absolutely not the purpose of those tarballs. What you really want >>> to package is the resulting toolchain. The bckup tarballs are only for >>> debug purposes. >>> >> It wasn't to make a package to distribute but to make faked packages for >> the target system: >> basically, sys-kernel/linux-headers and sys-libs/glibc (gentoo >> embedded). The entire toolchain shouldn't be installed on the target >> (and will not run). And, yeah, I should have rebuilt >> libc but importing faked package from the toolchain was easier and less >> time consuming. >> > I still don't understand. What do you want those packages for? Do you > mean you want to copy something on the target? > > If you mean that your root file system is missing the libraries from > the toolchain, then look at the populate script (that is installed > with your toolchain): > > # arm-unknown-linux-uclibc-populate -h [...] > Basically, you use it like that: > > 1) Build all your packages (adapt as needed!): > # cd my-package > # ./configure --prefix=/usr \ > --build="build-tuple" \ > --host="host-tuple" \ > CFLAGS="-I/some/where/staging/usr/include \ > LDFLAGS="-L/some/where/staging/usr/lib > # make > # make DESTDIR=/some/where/staging install > And so on for all your packages... > > 2) And finally: > # host-tuple-populate -s /some/where/staging \ > -d /some/where/staging-full > > At this point, staging-full/ contains all that your package(s) did install > *and* the required libraries from the toolchain (eg. libc.so, ld-linux.so...) > without touching the staging/ area, thus leaving in staging/ *only* the files > that your packages did install. > > Yeah, I know about <tuple>-populate, but as I use gcc --sysroot=/my/staging/root, some files from the toolchain aren't found at build time (like all crt?.o files). So I came with the idea to copy them to the staging root, and being proper, I tried to make a faked package of sys-libc/glibc by importing the version compiled in the toolchain. Other solution should be to build (again) the real package from gentoo, I may try this someday, but laziness forbids me to do this for now ;-) Well, I stop to annoy you with my non-standards uses cases for now, and let you work to this very good tool. Thanks ! Bruno TARQUINI. -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |