public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Sergei Gavrikov <sg@sgs.gomel.by>
To: Alexander Neundorf <neundorf@kde.org>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] Re: GCC 3.2.1 libgcc_eh.a issue
Date: Tue, 10 Jul 2007 06:09:00 -0000	[thread overview]
Message-ID: <1184047997.4819.15.camel@sg-ubuntu> (raw)
In-Reply-To: <200707100019.50947.neundorf@kde.org>

Alexander Neundorf writes:
> On Sunday 27 May 2007 12:36, Sergei Gavrikov wrote:
> 
> >Hello,
> >
> > Sometimes, I use the i386-elf-gcc (GCC 3.2.1) from the public
> > ecoscentric toolchain for I386 to build/debug some test using the eCos
> > synth target.
> >
> > AFAIK, they don't recommend to use native GCC for that. The synth.ld
> > script (hal/synth/arch/current/src/synth.ld) contains a point
> >
> > #if (__GNUC__ >= 3)
> > GROUP(libtarget.a libgcc.a libsupc++.a libgcc_eh.a)
> > #else
> > GROUP(libtarget.a libgcc.a)
> > #endif
> >
> > According a ChangeLog, that was Jonathan Larmour's tweak.
> >
> > But their GCC 3.2.1 has no libgcc_eh.a at all:
> >
> > ~/ecos/gnutools/i386-elf/i386-elf/lib/libcygmon.a
> > ~/ecos/gnutools/i386-elf/i386-elf/lib/libsupc++.a
> > ~/ecos/gnutools/i386-elf/i386-elf/lib/libstdc++.a
> > ~/ecos/gnutools/i386-elf/i386-elf/lib/libnosys.a
> > ~/ecos/gnutools/i386-elf/lib/gcc-lib/i386-elf/3.2.1/libgcc.a
> >
> > So, I have to fix the GROUP description in the result ld script
> > (install/lib/target.ld) every time to build the test, i.e. to replace
> > the line
> >
> > GROUP(libtarget.a libgcc.a libsupc++.a libgcc_eh.a)
> >
> > by
> >
> > GROUP(libtarget.a libgcc.a libsupc++.a libgcc.a)
> >
> > Well, that isn't an issue for the sed, but...
> 
> same here, using the gcc toolchain from ecoscentric, on kubuntu 06.10.
> 
> Using the same modification as you it works for me, the executables for the 
> synth. target run.
> Using gcc from the distribution it builds and links also without the 
> modification, but they don't run, they get a SIGSEGV in synth_intr.c, void 
> synth_hardware_init(void).
> 
> I didn't dig deeper into the problem yet.
> Are there any known problems with this (k)ubuntu version and ecos ?
> 
> Alex

Ah, I didn't think that is distro issue. It's pity what I don't remember
about this fail when I used elder Slackware, but I will try this ASAP.
So, do you think that problem is these Ubuntu freshmeat dependences?

ldd `which i386-elf-gcc`
        linux-gate.so.1 =>  (0xffffe000)
        libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7dd1000)
        /lib/ld-linux.so.2 (0xb7f15000)

Nowadays, I use Ubuntu 6.10/7.04. And I have this problem. But if you
are right... AFAIK, we cannot get a static compiled GCC. Is it time to
change GCC generation? :-)

Thanks for your feedback,

Regards,

Sergei



-- 
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:[~2007-07-10  6:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10  4:19 Alexander Neundorf
2007-07-10  6:09 ` Sergei Gavrikov [this message]
2007-07-10 23:57   ` Alexander Neundorf

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=1184047997.4819.15.camel@sg-ubuntu \
    --to=sg@sgs.gomel.by \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=neundorf@kde.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).