Glibc headers in one directory and linux headers in another
Bryan Hundven
bryanhundven@gmail.com
Tue Sep 2 19:05:00 GMT 2014
Shaun,
On Tue, Sep 2, 2014 at 10:25 AM, Shaun Jackman <sjackman@gmail.com> wrote:
> The simple work around to this problem is to symlink both the glibc
> and Linux headers into the single directory specified with
> --with-native-system-header-dir. It would still be nice to be able to
> specify multiple header directories. gettext (libintl.h) seems to be a
> third dependency of building GCC --with-sysroot.
>
> Cheers,
> Shaun
>
> http://sjackman.ca
> http://sjackman.ca
>
>
> On 28 August 2014 11:30, Shaun Jackman <sjackman@gmail.com> wrote:
>> I'm attempting to compile a native GCC compiler that uses a newly
>> downloaded set of Linux headers and a newly compiled glibc. These two
>> packages are installed in different directories. I'd like to specify
>> --with-native-system-header-dir twice, once for each set of headers. I
>> didn't in fact try that, but I'm guessing that it's not supported. I
>> tried using --with-headers, but it's supported only for cross
>> compiles. Is there a set of configuration parameters that I can use to
>> accomplish this? My configure line is:
>>
>> ../configure --with-sysroot=/home/sjackman/.linuxbrew
>> --prefix=/Cellar/xgcc/4.9.1
>> --with-native-system-header-dir=/opt/glibc/include
>>
>> The glibc headers are installed in $sysroot/opt/glibc/include.
>> The linux headers are installed in $sysroot/opt/linux-headers/include
>> and also symlinked into $sysroot/include.
>>
>> Thanks,
>> Shaun
>>
>> http://sjackman.ca
I understand what you are trying to do. My question is to find out
your intentions; Why do you feel it is necessary to separate headers
that belong in one $sysroot/$prefix/include directory?
-Bryan
More information about the Gcc-help
mailing list