From: Bob Brusa <bob.brusa@gmail.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: : "recipe for target `arm.inc' failed" while building library
Date: Wed, 23 Jan 2013 18:20:00 -0000 [thread overview]
Message-ID: <510029DB.3050300@gmail.com> (raw)
In-Reply-To: <51001DA3.9000501@dallaway.org.uk>
Am 23.01.2013 18:28, schrieb John Dallaway:
> Hi Bob
>
> On 23/01/13 17:08, Bob Brusa wrote:
>
>> makefile:37: recipe for target `arm.inc' failed
>> arm-none-eabi-gcc.exe: error:
>> /opt/ecos/packages/hal/arm/arch/current/src/hal_mk_defs.c: No error
>> make[1]: Leaving directory
>> `/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_build/hal/arm/arch/current'
>> arm-none-eabi-gcc.exe: fatal error: no input files
>> makefile:15: recipe for target `build' failed
>> compilation terminated.
>> make: Leaving directory `/cygdrive/c/Projekte/TDSsw/libs/tds_lib_17_build'
>> make[1]: *** [arm.inc] Error 1
>> make: *** [build] Error 2
>>
>> This is when using the codesourcery lite 4.7.1 and eCos Configuration
>> Tool3.net. When building the library using the toolchain that came with
>> eCos3.0, it works.
>> Thanks for help - Bob
>
> The Sourcery build of the arm-none-eabi toolchain is a native Windows
> build (not using Cygwin). It is likely that one of the POSIX-style file
> paths used by the eCos build system is not being recognized.
>
> I hope this helps...
>
> John Dallaway
> eCos maintainer
> http://www.dallaway.org.uk/john
>
Hi John,
Unfortunately it did not help. When deleting c:\cygwin\bin from my PATH,
the configtool produces a "can not find cygwin1.dll"-error. The
config-tool has an entry Tools>Path>usertools where I specified the
cygwin-path. Obviously this is not enough.....
The funny thing is: I once succeeded in building a lib with this
cs-lite-toolchain - but later I always just got build errors and no lib.
No idea how I did this earlier. Do you have any further advice?
Thanks and regards - Bob
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2013-01-23 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:08 [ECOS]: " Bob Brusa
2013-01-23 17:28 ` [ECOS] Re: : " John Dallaway
2013-01-23 18:20 ` Bob Brusa [this message]
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=510029DB.3050300@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).