K. Richard Pixley
Cygnus Support
- Last Mod 19 Jul 1991 by gnu@cygnus.com
+ Last Mod Tue Oct 1 21:20:21 PDT 1991, by rich@cygnus.com
INTRO
-----
structure, the intermediate pieces used in the build process must
be kept separate.
- ./configure sun4 +forcesubdirs +notation=postfix
- ./configure sun3 +forcesubdirs +notation=infix
+ ./configure sun4 +subdirs +notation=postfix
+ ./configure sun3 +subdirs +notation=infix
will create subdirectories for the intermediate pieces of the sun4
and sun3 configurations. This is necessary as previous systems
were only capable of one configuration at a time. A second
configuration overwrote the first. We've chosen to retain this
- behaviour so the "+forcesubdirs" configuration option is necessary
+ behaviour so the "+subdirs" configuration option is necessary
to get the new behaviour. The order of the arguments doesn't
matter. There should be exactly one argument without a leading
'+' sign and that argument will be assumed to be the host name.
From here on the examples will assume that you want to build the
- tools "in place" and won't show the "+forcesubdirs" option, but
+ tools "in place" and won't show the "+subdirs" option, but
remember that it is available.
In order to actually install the program, the configuration system
default location is /usr/local. We refer to this location as
$(destdir). All user visible programs will be installed in
$(destdir)/bin. All other programs and files will be installed in
- a subdirectory of $(destdir)/lib. For the tools in this
- directory, the files not normally user visible will be installed
- in $(destdir)/lib/gcc.
+ a subdirectory of $(destdir)/lib.
You can elect to change $(destdir) only as a configuration time
option.
In this example, like before, we create two configurations. The
first is intended to be built in a sun4 environment, in
subdirectories, to be installed in /local. The second is intended
- to be build in a sun3 environment, in subdirectories, to be
+ to be built in a sun3 environment, in subdirectories, to be
installed in /local.
Unlike the previous example, the first configuration will produce
hostname and target is targetname. If a previous configuration
existed, it will be overwritten.
-* "./configure +forcesubdirs hostname +target=targetname" creates a
- subdirectories Host-hostname and Host-hostname/Target-targetname and
- configures Host-hostname/Target-targetname. For now, makes should
- be done from Host-hostname/Target-targetname. "./configure +f name"
- works as expected. That is, it creates Host-name and
- Host-name/Target-name and configures the latter.
+* "./configure +subdirs hostname +target=targetname" creates a
+ subdirectories H-hostname and H-hostname/T-targetname and
+ configures H-hostname/T-targetname. For now, makes should
+ be done from H-hostname/T-targetname. "./configure +sub name"
+ works as expected. That is, it creates H-name and
+ H-name/T-name and configures the latter.
Hacking configurations: