This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
Re: Rutger's NAND flash now has a synth package
- From: Sergei Gavrikov <sergei dot gavrikov at gmail dot com>
- To: Simon Kallweit <simon dot kallweit at intefo dot ch>
- Cc: Rutger Hofman <rutger at cs dot vu dot nl>, "ecos-devel at ecos dot sourceware dot org" <ecos-devel at ecos dot sourceware dot org>
- Date: Mon, 29 Jun 2009 10:55:08 +0300
- Subject: Re: Rutger's NAND flash now has a synth package
- References: <4A475994.7010203@cs.vu.nl> <4A48623F.2080500@intefo.ch>
On Mon, Jun 29, 2009 at 08:42:07AM +0200, Simon Kallweit wrote:
> Rutger Hofman wrote:
> >An aside: I run Ubuntu. At first, I couldn't run synth at all.
> >Applications would crash, and gdb would crash on the application too!
> >After some list searching, I found out that this probably is
> >Ubuntu-specific. We need to include -fno-stack-protector in the
> >GLOBAL_CFLAGS configure flag. Request: cannot this be automated for
> >synth building? My guess is that it will not harm on systems other than
> >Ubuntu, and it will save Ubuntu users effort.
>
> I observed the same bug. But I started using eCosCentrics i386 toolchain
> for my synth builds which works fine with standard configuration. It
> will also make sure that I don't run into GCC specifics from time to
> time, as the distro's toolchain is updated quite often.
Hi
My 2 cents. That i386-elf GCC build has not `libgcc_eh.a' library
find /opt/ecos/gnutools/i386-elf/ -name libgcc_eh.a
<< no output >>
but the library is "used" for synth
hal/synth/arch/current/src/synth.ld:
#if (__GNUC__ >= 3)
GROUP(libtarget.a libgcc.a libsupc++.a libgcc_eh.a)
#else
GROUP(libtarget.a libgcc.a)
#endif
Can we manage the check the above with CDL?
Because 2 odd? steps to make synth tests are necessary
1) Import this option
cdl_option CYGBLD_GLOBAL_COMMAND_PREFIX {
user_value i386-elf
};
2) Workaround for the absent libgcc_eh.a in ld GROUP
sed -i 's/ libgcc_eh.a//' install/lib/target.ld
Sergei