public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sergei.gavrikov@gmail.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: Rutger Hofman <rutger@cs.vu.nl>,
		"ecos-devel@ecos.sourceware.org"
	<ecos-devel@ecos.sourceware.org>
Subject: Re: Rutger's NAND flash now has a synth package
Date: Mon, 29 Jun 2009 07:52:00 -0000	[thread overview]
Message-ID: <20090629075442.GA30703@sg-ubuntu.local> (raw)
In-Reply-To: <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

  reply	other threads:[~2009-06-29  7:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-28 11:46 Rutger Hofman
2009-06-29  6:42 ` Simon Kallweit
2009-06-29  7:52   ` Sergei Gavrikov [this message]
2009-06-29 11:32   ` Rutger Hofman
2009-06-29  7:24 ` GCC stack protector with linux synthetic target John Dallaway
2009-06-29  7:50   ` Andrew Lunn
2009-06-29  9:50   ` Bart Veer
2009-06-30  8:55     ` John Dallaway

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=20090629075442.GA30703@sg-ubuntu.local \
    --to=sergei.gavrikov@gmail.com \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=rutger@cs.vu.nl \
    --cc=simon.kallweit@intefo.ch \
    /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).