public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Ross Younger <wry@ecoscentric.com>
To: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: unable to build linux synthetic target
Date: Mon, 20 Jul 2009 13:00:00 -0000	[thread overview]
Message-ID: <4A646A6C.6020003@ecoscentric.com> (raw)
In-Reply-To: <b18c5f790907200450h38b8ea1ftacc45419697eb5a6@mail.gmail.com>

Mandeep Sandhu wrote:
> [synth build]
> Why doesn't it work from the GUI tool?

Doesn't work for me either. Looks like configtool is setting up the wrong
PATH for a synth build:

>> sh -c "export PATH=/home/mandeep/ecos/gnutools/arm-eabi/arm-eabi/bin:$PATH;
>> unset GDBTK_LIBRARY; unset GCC_EXEC_PREFIX; export
>> ECOS_REPOSITORY=/home/mandeep/ecos/ecos-3.0/packages; make -j2
>> --directory /home/mandeep/ecos/linux-synth/linux-synth_build"

arm-eabi?? It does that for me as well. Experimentally, it seems that that
PATH setting is the problem; but does the configtool even need to edit the
PATH for a synth build if the compiler prefix is empty?


Ross

-- 
Embedded Software Engineer, eCosCentric Limited.
Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK.
Registered in England no. 4422071.                  www.ecoscentric.com

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  reply	other threads:[~2009-07-20 13:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-20 11:42 [ECOS] " Mandeep Sandhu
2009-07-20 11:51 ` [ECOS] " Mandeep Sandhu
2009-07-20 13:00   ` Ross Younger [this message]
2009-07-20 17:06   ` John Dallaway
2009-07-21  7:58     ` Mandeep Sandhu

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=4A646A6C.6020003@ecoscentric.com \
    --to=wry@ecoscentric.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).