public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mandeep Sandhu <mandeepsandhu.chd@gmail.com>
To: ecos-discuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Re: unable to build linux synthetic target
Date: Mon, 20 Jul 2009 11:51:00 -0000	[thread overview]
Message-ID: <b18c5f790907200450h38b8ea1ftacc45419697eb5a6@mail.gmail.com> (raw)
In-Reply-To: <b18c5f790907200442w3c7ee0b2q9b1214b83a4d9151@mail.gmail.com>

Got it to work! :)

Went into the build dir and did:

$make
$make tests

Why doesn't it work from the GUI tool?

-mandeep

On Mon, Jul 20, 2009 at 5:12 PM, Mandeep
Sandhu<mandeepsandhu.chd@gmail.com> wrote:
> Hi All,
>
> I'm trying to build the linux synthetic target with the lwip_eth config using
> the GUI tool.
>
> I get the following error:
>
> 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"
>
> make: Entering directory `/home/mandeep/ecos/linux-synth/linux-synth_build'
> make -r -C hal/synth/arch/v3_0 headers
> make[1]: Entering directory
> `/home/mandeep/ecos/linux-synth/linux-synth_build/hal/synth/arch/v3_0'
> make[1]: Nothing to be done for `headers'.
> ...
> ...
> make[1]: Nothing to be done for `headers'.
> make[1]: Leaving directory
> `/home/mandeep/ecos/linux-synth/linux-synth_build/io/common/v3_0'
> make -r -C infra/v3_0 headers
> make[1]: Entering directory
> `/home/mandeep/ecos/linux-synth/linux-synth_build/infra/v3_0'
> gcc: error trying to exec 'cc1plus': execvp: No such file or directory
> make[1]: Nothing to be done for `headers'.
> make[1]: *** [heapgeninc.tcl] Error 1
> make[1]: Leaving directory
> `/home/mandeep/ecos/linux-synth/linux-synth_build/infra/v3_0'
> make: *** [build] Error 2
> make -r -C kernel/v3_0 headers
>
> Initially it was because I did not have g++.
>
> But even after installing g++ (using apt on ubuntu), it's giving me
> the same error.
>
> Is the exported PATH variable also ok? I guess it should be, as we are
> keeping the existing
> PATH variable.
>
> Thanks,
> -mandeep
>

-- 
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 11:51 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 ` Mandeep Sandhu [this message]
2009-07-20 13:00   ` [ECOS] " Ross Younger
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=b18c5f790907200450h38b8ea1ftacc45419697eb5a6@mail.gmail.com \
    --to=mandeepsandhu.chd@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).