From: Peter Allin <pallists@peca.dk>
To: sid@sourceware.org
Subject: Build problems - no libiberty/pic
Date: Sun, 26 Mar 2006 21:16:00 -0000 [thread overview]
Message-ID: <442704BE.4080008@peca.dk> (raw)
Hi,
I've tried to build the three SID snapshots currently found on
sources.redhat.com and the latest from CVS.
In all four cases I got the following error:
/bin/sh ./libtool --tag=CXX --mode=link c++ -g -O2 -o libcgencpu.la
-rpath /home/pal/local/arm-tools//lib/sidcomp -module -no-undefined
compCGEN.lo cgen-fpu.lo fp.lo tracedis.lo arm7t/libarm7t.la
m32r/libm32r.la mt/libmt.la xstormy16/libxstormy16.la
-L../../../libiberty/pic -liberty cgen-asm.lo cgen-dis.lo cgen-opc.lo
dis-buf.lo dis-init.lo -lpthread -lm
./libtool: line 1803: cd: ../../../libiberty/pic: No such file or directory
libtool: link: cannot determine absolute directory name of
`../../../libiberty/pic'
make[7]: *** [libcgencpu.la] Error 1
Any hints on how to get past this woul be greatly appreciated.
Best regards,
Peter Allin
next reply other threads:[~2006-03-26 21:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-26 21:16 Peter Allin [this message]
2006-03-27 22:28 ` Frank Ch. Eigler
2006-03-30 4:59 ` Peter Allin
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=442704BE.4080008@peca.dk \
--to=pallists@peca.dk \
--cc=sid@sourceware.org \
/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).