[Scratchbox-users] Re: Foreign toolchain imports don't always create libc packages

[Matt Hoosier]

On 7/11/06, Matt Hoosier <mwhoosier at gmail.com> wrote:
> Hi,
>
> I've noticed that when importing a foreign toolchain, the libc6 and
> libc6-dev packages aren't always produced.
>
> My particular case is a Crosstool 0.42 toolchain built in-place at
> /scratchbox/compilers/i686-gcc-3.4.5-glibc-2.3.6. The configuration is
> a lightly modified (only to change the name of the generated Debian
> package) version of the default output from create_toolchain_conf.py.
>
> After the first cycle in which no libc6 and libc6-dev Debian packages
> were generated, I noticed that default values of LIBC_FILES_BINS and
> LIBC_FILES_LIBS pointed at directories whose contents weren't really
> the main C libraries and utilities. So I updated their definitions to:
>
> LIBC_FILES_BINS = $(TARGET)/bin
> LIBC_FILES_LIBS = $(TARGET)/lib
>
> Compare my values [above] to those which are given for the
> CodeSourcery 2005q3 foreign toolchain import, whose results do include
> a Debian package for the C library:
>
> LIBC_FILES_BINS = $(TARGET)/libc/usr/bin $(TARGET)/bin
> LIBC_FILES_LIBS = $(TARGET)/libc/lib $(TARGET)/libc/usr/lib
>
> Although the exact paths for the C library binaries and libs [within
> $(TARGET)] are somewhat different in my config than in the example
> config for CodeSourcery 2005q3, this is only a compensation for the
> fact that Crosstool puts its results in a slightly different path than
> does CodeSourcery.
>
> What am I doing wrong, such that the cs-gcc3.4.4-glibc.conf example
> manages to create Debian packages for the C library, but a
> Crosstool-based build does not?

Solved this problem. Some stray stamp files in
sb-toolchain-extras/libc/glibc-alienbase-debian/cookies were causing
Make to skip processing on that directory.

>