This is the mail archive of the
libc-hacker@cygnus.com
mailing list for the glibc project.
Re: __OPTIMIZE__ & __ctype32_b
- To: Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>
- Subject: Re: __OPTIMIZE__ & __ctype32_b
- From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
- Date: Fri, 29 Jan 1999 11:54:12 +0100
- Cc: drepper@cygnus.com (Ulrich Drepper), libc-alpha@cygnus.com
- References: <Franz Sirl's message of "Wed, 27 Jan 1999 19:21:27 +0100"><Christopher Seawood's message of "Tue, 26 Jan 1999 23:17:11 -0800 (PST)"><Pine.LNX.4.02A.9901262311560.1057-100000@panic.can.seawood.org><4.1.19990127190505.0437c030@mail.lauterbach.com>
At 10:24 29.01.99 , Andreas Schwab wrote:
>Franz Sirl <Franz.Sirl-kernel@lauterbach.com> writes:
>
>|> "Always build _outside_ the source dir"
>
>There was never such a problem. Even building in the source dir should
>work again.
OK, then somebody should update INSTALL with the allowed/working
procedures. Currently it quite clearly states:
Configuring and compiling GNU Libc
==================================
GNU Libc cannot be compiled in the source directory. You must
create a separate directory for the object files. This directory
should be outside the source tree. For example, if you have unpacked
the glibc sources in `/src/gnu/glibc-2.1.0', create a directory
`/src/gnu/glibc-build' to put the object files in.
From your object directory, run the shell script `configure' found
at the top level of the source tree. In the scenario above, you'd type
$ ../glibc-2.1.0/configure ARGS...
Franz.