From: Gary Thomas <gary@mlbassoc.com>
To: sid@sources.redhat.com
Subject: SID won't build
Date: Wed, 29 Jan 2003 22:24:00 -0000 [thread overview]
Message-ID: <1043879041.24759.4217.camel@hermes.chez-thomas.org> (raw)
I updated from CVS today and SID no longer builds. (Actually, I was
trying to look at Stefano's problem, but I ran into other difficulties)
Here's the crux of the error:
gcc -DHAVE_CONFIG_H -I../../../../opcodes -I../../../../bfd
-I../../../../intl
-I/work2/sid/src/sid/component/cgen-cpu/m32r/../../../../opcodes
-I/work2/sid/src/sid/component/cgen-cpu/m32r/../../../../include
-I/work2/sid/src/sid/component/cgen-cpu/m32r/../../../../bfd
-I/work2/sid/src/sid/component/cgen-cpu/m32r/../../../../intl
-D_GNU_SOURCE -g -O2 -c -fPIC -DPIC
/work2/sid/src/sid/component/cgen-cpu/m32r/../../../../opcodes/m32r-asm.c -o .libs/m32r-asm.lo
In file included from /work2/sid/src/opcodes/m32r-asm.c:28:
/work2/sid/src/opcodes/sysdep.h:28:20: config.h: No such file or
directory
make[5]: *** [m32r-asm.lo] Error 1
make[5]: Leaving directory `/work/sid/component/cgen-cpu/m32r'
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory `/work/sid/component/cgen-cpu'
make[3]: *** [all-recursive-am] Error 2
make[3]: Leaving directory `/work/sid/component/cgen-cpu'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/work/sid/component'
make[1]: *** [all-recursive-am] Error 2
make[1]: Leaving directory `/work/sid/component'
make: *** [all-recursive] Error 1
--
------------------------------------------------------------
Gary Thomas |
MLB Associates | Consulting for the
+1 (970) 229-1963 | Embedded world
http://www.mlbassoc.com/ |
email: <gary@mlbassoc.com> |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------
next reply other threads:[~2003-01-29 22:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 22:24 Gary Thomas [this message]
2003-01-30 17:21 ` Frank Ch. Eigler
2003-01-30 19:36 ` Gary Thomas
2003-01-30 19:56 ` Frank Ch. Eigler
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=1043879041.24759.4217.camel@hermes.chez-thomas.org \
--to=gary@mlbassoc.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).