[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Why relink the library during make install?
From: |
Paul Lew |
Subject: |
Why relink the library during make install? |
Date: |
Wed, 24 Jul 2002 10:06:40 -0700 |
Sorry to email to this address, I could not find a mailing list for
this.
I have a problem build and install gettext-1.11.3. In our environment
the build prefix specified with the configure phase is different than
the prefix specified in the make install.
We have another process which will setup the symbolic links *after*
make install so for the users the application can be accessed from the
prefix as defined in the configure phase.
We have been using this method for years until recently we noticed
that the make install process will attempt to relink the program with
the prefix for installation. This is not a desired behavior for us,
in other words, the make install is a bit too smart in this case.
Attached is the excerpt of the difference. Is there a way to achieve
what I wanted? i.e., tell make to install in a different directory and
not trying to recompile.
Thanks.
> configure --prefix=/auto/insbu-cnstools
> make
...
/usr/ccs/bin/ld -G -z defs -h libgettextlib-0.11.3.so -o
.libs/libgettextlib-0.11.3.so argmatch.lo backupfile.lo addext.lo
basename.lo c-ctype.lo copy-file.lo error.lo execute.lo findprog.lo
fstrcmp.lo full-write.lo gcd.lo getopt.lo getopt1.lo hash.lo
javacomp.lo javaexec.lo linebreak.lo localcharset.lo mbswidth.lo
obstack.lo concatpath.lo pipe-bidi.lo pipe-in.lo pipe-out.lo
progname.lo safe-read.lo sh-quote.lo stpncpy.lo strtoul.lo tmpdir.lo
wait-process.lo xerror.lo xmalloc.lo xstrdup.lo xsetenv.lo stpcpy.lo
vasprintf.lo getline.lo mkdtemp.lo setenv.lo unsetenv.lo
-R/auto/insbu-cnstools/build/gettext-0.11.3/intl/.libs
-R/auto/insbu-cnstools/lib -R/auto/insbu-cnstools/lib
-L/auto/insbu-cnstools/lib ../intl/.libs/libintl.so
/auto/insbu-cnstools/lib/libiconv.so -lc -lc
...
> make install
prefix=/auto/insbu-cnstools/kit/gettext-0.11.3/auto/insbu-cnstools
...
/usr/ccs/bin/ld -G -z defs -h libgettextlib-0.11.3.so -o
.libs/libgettextlib-0.11.3.so argmatch.lo backupfile.lo addext.lo
basename.lo c-ctype.lo copy-file.lo error.lo execute.lo findprog.lo
fstrcmp.lo full-write.lo gcd.lo getopt.lo getopt1.lo hash.lo
javacomp.lo javaexec.lo linebreak.lo localcharset.lo mbswidth.lo
obstack.lo concatpath.lo pipe-bidi.lo pipe-in.lo pipe-out.lo
progname.lo safe-read.lo sh-quote.lo stpncpy.lo strtoul.lo tmpdir.lo
wait-process.lo xerror.lo xmalloc.lo xstrdup.lo xsetenv.lo stpcpy.lo
vasprintf.lo getline.lo mkdtemp.lo setenv.lo unsetenv.lo
-R/auto/insbu-cnstools/lib -L/auto/insbu-cnstools/lib
-L/auto/insbu-cnstools/kit/gettext-0.11.3/auto/insbu-cnstools/lib
-lintl -liconv -liconv -lc -lc
- Why relink the library during make install?,
Paul Lew <=
- Re: Why relink the library during make install?, Bruno Haible, 2002/07/24
- Re: Why relink the library during make install?, Paul Lew, 2002/07/24
- Re: Why relink the library during make install?, Alfred M. Szmidt, 2002/07/24
- Re: Why relink the library during make install?, Russ Allbery, 2002/07/24
- Re: Why relink the library during make install?, Ralph Corderoy, 2002/07/31
- Re: Why relink the library during make install?, Miles Bader, 2002/07/31
- Re: Why relink the library during make install?, Thomas Bushnell, BSG, 2002/07/24