From: cgd@broadcom.com
To: dj@redhat.com
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: [PATCH RFA] tweak expect EXP_LIB_SPEC to use libdir.
Date: Thu, 02 Oct 2003 04:40:00 -0000 [thread overview]
Message-ID: <yov53cectfpg.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
Problem found on mips64-linux. On that system type (with default
compile flags), one configures with --prefix=/usr --libdir=/usr/lib32,
since the default ABI is n32 and you want the n32 libs to go in the
right place.
(exec_prefix not specially defined, so it's ${prefix}. By default,
libdir is ${exec_prefix}/lib.)
expect would install its lib under ${libdir} as expected, but would
try to link the expect-to-be-installed against the expect library
under ${exec_prefix}/lib.
Once that's fixed, it works quite nicely. 8-)
cgd
--
2003-10-01 Chris Demetriou <cgd@broadcom.com>
* configure.in (EXP_LIB_SPEC): Use ${libdir} rather than
${exec_prefix}/lib.
* configure: Regenerate.
Index: configure.in
===================================================================
RCS file: /cvs/src/src/expect/configure.in,v
retrieving revision 1.7
diff -u -p -r1.7 configure.in
--- configure.in 29 Jan 2003 23:46:22 -0000 1.7
+++ configure.in 2 Oct 2003 04:22:24 -0000
@@ -1165,7 +1165,7 @@ if test $ac_cv_sys_long_file_names = no;
fi
EXP_BUILD_LIB_SPEC="-L`pwd` -lexpect${EXP_LIB_VERSION}"
-EXP_LIB_SPEC="-L\${exec_prefix}/lib -lexpect${EXP_LIB_VERSION}"
+EXP_LIB_SPEC="-L\${libdir} -lexpect${EXP_LIB_VERSION}"
EXP_UNSHARED_LIB_FILE=libexpect${EXP_LIB_VERSION}.a
EXP_BUILD_LIB_SPEC=${EXP_UNSHARED_LIB_FILE}
next reply other threads:[~2003-10-02 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-02 4:40 cgd [this message]
2003-10-02 4:53 ` DJ Delorie
[not found] ` <mailpost.1065070425.24076@news-sj1-1>
2003-10-02 5:25 ` cgd
2003-10-02 5:29 ` cgd
[not found] ` <mailpost.1065072338.24856@news-sj1-1>
2003-10-02 18:10 ` cgd
2003-10-02 18:35 ` DJ Delorie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yov53cectfpg.fsf@ldt-sj3-010.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=binutils@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox