This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: [BUG] ports using --with-headers
- From: Atsushi Nemoto <anemo at mba dot ocn dot ne dot jp>
- To: drow at false dot org
- Cc: maillist at jg555 dot com, libc-ports at sourceware dot org
- Date: Sat, 25 Mar 2006 01:03:32 +0900 (JST)
- Subject: Re: [BUG] ports using --with-headers
- References: <20060321210749.GB16706@nevyn.them.org>
>>>>> On Tue, 21 Mar 2006 16:07:49 -0500, Daniel Jacobowitz <drow@false.org> said:
> On Sat, Mar 18, 2006 at 04:49:42PM -0800, Jim Gifford wrote:
>> Is --with-headers={location of headers} suppose to work with the
>> glibc-ports. My testing shows that it doesn't wanted to know if
>> others are seeing the same thing.
> Ports or not shouldn't have any affect on this. Did sysincludes get
> set? Check config.status and config.make.
I also see the problem. I'm trying cross-compile glibc 2.4 with gcc
4.1, and the gcc 4.1 was built without libc header (build from
scratch).
I suppose the error was caused by following lines in nscd/Makefile:
# The configure.in check for libselinux and its headers did not use
# $SYSINCLUDES. The directory specified by --with-headers usually
# contains only the basic kernel interface headers, not something like
# libselinux. So the simplest thing is to presume that the standard
# system headers will be ok for this file.
$(objpfx)nscd_stat.o: sysincludes = # nothing
$(objpfx)selinux.o: sysincludes = # nothing
The 'standard system headers' are not yet built in this stage of
cross-compiling from scratch. How can we resolve this ?
---
Atsushi Nemoto