Manolis Ragkousis skribis:
> In the debian package I saw there are 2 patches that add this.
>
>> +libc_add_on_canonical=libpthread
>> +libc_add_on_subdirs=.
>
> How does this change the configure process?
Libc’s top-level configure file expects these two variables to be set by
the add-on’s ‘co
In the debian package I saw there are 2 patches that add this.
> +libc_add_on_canonical=libpthread
> +libc_add_on_subdirs=.
How does this change the configure process?
As Ludovic wrote
> Actually libc's configure doesn't use the normal AC_CONFIG_SUBDIRS
> mechanism, and instead runs add-on configure scripts by itself, without
> arguments AFAICS.
The part responsible for this is in the attached file and specifically the
part:
> libc_add_on_frag=$libc_add
> (This is libpthread's config.log, right?)
It's the config.log generated in the build folder of glibc.
There is no config.log file generated from libpthread.
Manolis
>
starting phase `configure'
source directory:
"/tmp/nix-build-glibc-hurd-cross-i686-pc-gnu-2.18.drv-4/source" (relative from
(Hurd people: this is about a configure error when cross-compiling glibc
with libpthread as an add-on.)
Manolis Ragkousis skribis:
> when building glibc with libpthread as an addon I get this
>
> configure: running configure fragment for add-on libpthread
> configure: WARNING: you should use --b
