From: "Robert Cragie" <rcc@jennic.com>
To: <sid@sources.redhat.com>
Subject: Can't build sid
Date: Thu, 09 Aug 2001 04:21:00 -0000 [thread overview]
Message-ID: <NDBBLOIOMLKELOJBAPAGKEAHCIAA.rcc@jennic.com> (raw)
I am trying to build SID, CVS version checked out at approx. 9th August 2001
0900 GMT, and I get the following error.
I did the following:
configure --prefix=/usr/local/sid/bin
make -w all install 2>&1 | tee make.out
I am using gcc version 2.95.3.
Here is the offending stuff from make.out:
[snip]
Making all in arm7t
make[6]: Entering directory
`/usr/src/sid/build/sid/component/cgen-cpu/arm7t'
/bin/sh ./libtool --mode=compile
++ -DPACKAGE=\"sidcomp\" -DVERSION=\"0.1\" -I. -I../../../../../src/sid/com
ponent/cgen-cpu/arm7t -I../../../../../src/sid/component/cgen-cpu/arm7t -I.
./../../../../src/sid/component/cgen-cpu/arm7t/.. -I../../../include -I../..
/../../../src/sid/component/cgen-cpu/arm7t/../../../include -I../../../../bf
d -I../../../../../src/sid/component/cgen-cpu/arm7t/../../../../include -
g -O2 -c ../../../../../src/sid/component/cgen-cpu/arm7t/arm7f.cxx
c++ -DPACKAGE=\"sidcomp\" -DVERSION=\"0.1\" -I. -I../../../../../src/sid/com
ponent/cgen-cpu/arm7t -I../../../../../src/sid/component/cgen-cpu/arm7t -I..
/../../../../src/sid/component/cgen-cpu/arm7t/.. -I../../../include -I../../
../../../src/sid/component/cgen-cpu/arm7t/../../../include -I../../../../bfd
-I../../../../../src/sid/component/cgen-cpu/arm7t/../../../../include -g -O
2 -Wp,-MD,.deps/arm7f.pp -c
../../../../../src/sid/component/cgen-cpu/arm7t/arm7f.cxx -o arm7f.o
In file included from
../../../../../src/sid/component/cgen-cpu/arm7t/arm7f.h:13,
from
../../../../../src/sid/component/cgen-cpu/arm7t/arm7f.cxx:8:
../../../../../src/sid/component/cgen-cpu/arm7t/../cgen-cpu.h:27: dis-asm.h:
No such file or directory
make[6]: *** [arm7f.lo] Error 1
make[6]: Leaving directory `/usr/src/sid/build/sid/component/cgen-cpu/arm7t'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/usr/src/sid/build/sid/component/cgen-cpu'
make[4]: *** [all-recursive-am] Error 2
make[4]: Leaving directory `/usr/src/sid/build/sid/component/cgen-cpu'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/sid/build/sid/component'
make[2]: *** [all-recursive-am] Error 2
make[2]: Leaving directory `/usr/src/sid/build/sid/component'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/sid/build/sid'
make: *** [all-sid] Error 2
make: Leaving directory `/usr/src/sid/build'
Can anyone help?
Robert Cragie
Design Engineer
Jennic Ltd.
Furnival Street
Sheffield
S1 4QT
United Kingdom
Tel: +44 (0) 114 281 4512
Fax: +44 (0) 114 281 2951
Mob: +44 (0) 7940 558520
mailto:rcc@jennic.com
http://www.jennic.com
next reply other threads:[~2001-08-09 4:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-09 4:21 Robert Cragie [this message]
2001-08-09 4:42 ` Frank Ch. Eigler
2001-08-09 5:18 ` Robert Cragie
2001-08-09 5:22 ` Frank Ch. Eigler
2001-08-09 5:45 ` Robert Cragie
2001-08-09 6:35 ` Frank Ch. Eigler
2001-08-09 10:33 ` Robert Cragie
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=NDBBLOIOMLKELOJBAPAGKEAHCIAA.rcc@jennic.com \
--to=rcc@jennic.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).