From: Dave Brolley <brolley@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: SID configury, libtoolery updated
Date: Fri, 10 Jun 2005 20:21:00 -0000 [thread overview]
Message-ID: <42A9F652.3050802@redhat.com> (raw)
In-Reply-To: <vt2k6lan75v.fsf@zenia.home>
Jim Blandy wrote:
>I've upgraded SID's libtool, autoconf, and automake machinery, fixed
>some warnings, and fixed a long-standing problem with components that
>link against libiberty.
>
>
>
>
I seem to be having trouble building sid now. Specifically
o The generate libtool scripts seem to expect the environment variable
SED to be set to a working sed
o I'm getting this error when linking in cgen-cpu
/bin/sh ./libtool --tag=CXX --mode=link c++ -g -o libcgencpu.la
-rpath /notnfs/brolley/sources/install/i686-pc-linux-gnu/lib/sidcomp
-module -no-undefined compCGEN.lo tracedis.lo ms1/libms1.la
-L../../../libiberty/pic -liberty cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo dis-init.lo -lpthread -lm
./libtool: line 1: cd: ../../../libiberty/pic: No such file or directory
...worked around by creating an empty libibrty/pic directory) but then
later...
if c++ -DHAVE_CONFIG_H -I. -I/home/brolley/sources/src/sid/main/dynamic
-I. -I. -I../../include
-I/home/brolley/sources/src/sid/main/dynamic/../../include
-I/home/brolley/sources/src/sid/main/dynamic/../../../include -g -MT
commonCfg.o -MD -MP -MF ".deps/commonCfg.Tpo" -c -o commonCfg.o
/home/brolley/sources/src/sid/main/dynamic/commonCfg.cxx; \
then mv -f ".deps/commonCfg.Tpo" ".deps/commonCfg.Po"; else rm -f
".deps/commonCfg.Tpo"; exit 1; fi
make[4]: *** No rule to make target
`../../../libiberty/pic/libiberty.a', needed by `sid'. Stop.
I've refreshed libiberty and rebuilt it from scratch, bit I don't get a
libiberty/pic directory in my build tree. Is there some configure option
I need? I'm using autoconf 2.59, automake 1.9.5 and libtool 1.5.18
uname -a says
Linux to-hpws2.toronto.redhat.com 2.4.21-27.0.2.ELsmp #1 SMP Wed Jan 12
23:35:44 EST 2005 i686 i686 i386 GNU/Linux
src/config.guess says
i686-pc-linux-gnu
Thanks,
Dave
next prev parent reply other threads:[~2005-06-10 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 3:18 Jim Blandy
2005-06-04 12:25 ` Frank Ch. Eigler
2005-06-04 15:22 ` Jim Blandy
2005-06-10 20:21 ` Dave Brolley [this message]
2005-06-10 20:34 ` Dave Brolley
2005-06-17 19:18 ` Jim Blandy
2005-06-17 19:24 ` Frank Ch. Eigler
2005-06-17 21:20 ` Dave Brolley
2005-06-20 15:22 ` Jim Blandy
2005-06-20 16:00 ` Dave Brolley
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=42A9F652.3050802@redhat.com \
--to=brolley@redhat.com \
--cc=jimb@redhat.com \
--cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).