This is the mail archive of the libc-alpha@cygnus.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: __OPTIMIZE__ & __ctype32_b


>>>>> Franz Sirl writes:

Franz> 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.

Franz> OK, then somebody should update INSTALL with the allowed/working
Franz> procedures. Currently it quite clearly states:

Franz> [...]

Here's a fix which should go in if somebody has tested that building
in the source dir really works.

Andreas


1999-01-31  Andreas Jaeger  <aj@arthur.rhein-neckar.de>

	* manual/install.texi (Configuring and compiling): Building in the 
	source directory works, change paragraph stating the opposite.

--- manual/install.texi.~2~	Sun Jan 24 19:32:55 1999
+++ manual/install.texi	Sun Jan 31 21:09:07 1999
@@ -48,10 +48,9 @@
 @cindex configuring
 @cindex compiling
 
-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 @file{/src/gnu/glibc-2.1.0}, create a directory
+GNU Libc can be compiled in the source directory but we'd advise to
+build in a separate build directory.  For example, if you have unpacked
+the glibc sources in @file{/src/gnu/glibc-2.1.0}, create a directory
 @file{/src/gnu/glibc-build} to put the object files in.
 
 From your object directory, run the shell script @file{configure} found


-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]