This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
In a message dated 3/27/99 2:37:23 AM Pacific Standard Time, girod@stybba.ntc.nokia.com writes: > I tried to put gas both as "as" and as "gas" in the directory reported > with: > > gcc -print-prog-name=cc1 > > with no affect. This is for my HP-UX 10.20 installation. > Or do you mean at the time of building egcs? > > % ./configure -with-gas The preferred procedure is to build the code in a directory separate from the source; e.g. a new directory just below the source. If you use the --with- gas, it points to the installed as: % ../configure --with-gas=<pathname of installed as> Apparently, you're planning to install into /usr/local but your gnu-as is installed somewhere else. Along this line, my system has insufficient disk space at /usr/local, so I have symlinks under /usr/local to my installation directories. However, configure doesn't follow the links backwards to find gnu-as, so I must specify the true installation directory (where both binutils and the compilers are installed) in --prefix, if I wish to use --with-gnu-as.