From: Bob Brusa <bob.brusa@gmail.com>
To: ecos discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Problems with conifgtool Version of 120425
Date: Mon, 13 Jan 2014 17:06:00 -0000 [thread overview]
Message-ID: <52D41D0E.7040909@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
Hi,
the new configtool seems to have some problems:
1
I long ago prepared an epk-file to add my platform to ecos.db. This is
done usinge Tools>Administration - Add-button and diging and selecting
the epk-file (icb_net.epk in my case). When I do this, configtool
creates a crash and outputs a stack dump.
2
I added the stuff I need manually to ecos.db. Start configtool and
Build>template and dig for and select my icb_net package. Then I save to
a suitable file e. g. icb_1.ecc
Result: configtool closes - but the file is there!
3
Start configtool and read in icb_1.ecc. Then Build>Generate Build Tree
Result: The program closes....but the "tree" is there.
4
Start config and read in icb_1.ecc. Then Build>Library and I get the
response:
make -j2 --directory "/projects/icb_em/icb_lib/icb_1_build"
make: Entering directory `/projects/icb_em/icb_lib/icb_1_build'
make: *** No targets specified and no makefile found. Stop.
make: Leaving directory `/projects/icb_em/icb_lib/icb_1_build'
I am clue-less why all this happens. Has anybody any help?
Thanks and best regards,
Bob
[-- Attachment #2: icb_net.epk --]
[-- Type: application/octet-stream, Size: 4652 bytes --]
[-- Attachment #3: Type: text/plain, Size: 148 bytes --]
--
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:[~2014-01-13 17:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 17:06 Bob Brusa [this message]
2014-01-14 17:10 ` [ECOS] Re: Problems with configtool " John Dallaway
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=52D41D0E.7040909@gmail.com \
--to=bob.brusa@gmail.com \
--cc=ecos-discuss@ecos.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).