This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: unable to build linux synthetic target
- From: Mandeep Sandhu <mandeepsandhu dot chd at gmail dot com>
- To: ecos-discuss <ecos-discuss at ecos dot sourceware dot org>
- Date: Mon, 20 Jul 2009 17:20:55 +0530
- Subject: [ECOS] Re: unable to build linux synthetic target
- References: <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