This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.
Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Fri, Nov 26, 2004 at 12:56:07AM +0100, Andreas Schwab wrote: > Jakub Jelinek <jakub@redhat.com> writes: > > > @@ -260,3 +262,13 @@ bug-glob2-ENV = MALLOC_TRACE=$(objpfx)bu > > > > $(objpfx)bug-glob2-mem: $(objpfx)bug-glob2.out > > $(common-objpfx)malloc/mtrace $(objpfx)bug-glob2.mtrace > $@ > > + > > +$(inst_libexecdir)/getconf: $(objpfx)getconf FORCE > > + $(addprefix $(..)./scripts/mkinstalldirs ,\ > > + $(filter-out $(wildcard $@),$@)) > > + for spec in `LC_ALL=C GETCONF_DIR=/dev/null \ > > + $(run-program-prefix) $< \ > > + _POSIX_V6_WIDTH_RESTRICTED_ENVS`; do \ > > This will fail when installing a cross-compiled glibc. Would _POSIX_V6_WIDTH_RESTRICTED_ENVS || :`; do \ be ok for you? Duplicating the relevant information from bits/environments.h somewhere would be a nightmare and other alternative that comes up is grepping bits/environments.h that will be used (or preprocessing it and grepping the preprocessed source). Jakub
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |