From: Grant Edwards <grante@visi.com>
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] Trying to build ecosconfig (again).
Date: Fri, 14 Sep 2007 20:36:00 -0000 [thread overview]
Message-ID: <fcerbn$c19$1@sea.gmane.org> (raw)
Once again, I need to build ecosconfig. Once again, it's a
struggle.
I create an empty directory and do
"configure path/to/host/configure"
That seems to go OK, but then the subsequent "make" sprays
warnings for a couple minutes and then fails like this:
c++ -pipe -Wall -Wpointer-arith -Wbad-function-cast -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wnested-externs -Woverloaded-virtual -O0 -o ecosconfig ecosconfig.o cdl_exec.o build.o flags.o -lcdl -lcyginfra -L/usr/lib -ltcl8.4 -L/home/grante/ecos/build/libcdl -L/home/grante/ecos/build/infra
c++: ecosconfig.o: No such file or directory
c++: cdl_exec.o: No such file or directory
make[2]: *** [ecosconfig] Error 1
make[2]: Leaving directory /home/grante/ecos/build/tools/configtool/standalone/common'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory /home/grante/ecos/build/tools/configtool/standalone/common'
make: *** [all-recursive] Error 1
Sure enough, neither ecosconfig.o nor cdl_exec.o are anywhere
to be found in the build tree. Neither can I find any thing in
the output from the make that indicates an attempt to build
either one of them.
IIRC, this is with a CVS snapshot from May 2007.
--
Grant Edwards grante Yow! I'm having a RELIGIOUS
at EXPERIENCE ... and I don't
visi.com take any DRUGS
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2007-09-14 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-14 20:36 Grant Edwards [this message]
2007-09-14 20:57 ` [ECOS] " Grant Edwards
2007-09-14 21:09 ` Grant Edwards
2007-09-14 21:01 ` [ECOS] " Andrew Lunn
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='fcerbn$c19$1@sea.gmane.org' \
--to=grante@visi.com \
--cc=ecos-discuss@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).