From: Bart Veer <bartv@ecoscentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: john@dallaway.org.uk, ecos-maintainers@ecos.sourceware.org
Subject: Re: eCos 3.0 beta 1 punch list #1
Date: Wed, 04 Feb 2009 10:08:00 -0000 [thread overview]
Message-ID: <pn63jqfrb3.fsf@delenn.bartv.net> (raw)
In-Reply-To: <20090204064729.GA22904@donkey.ma.tech.ascom.ch> (message from Andrew Lunn on Wed, 4 Feb 2009 07:47:29 +0100)
>>>>> "Andrew" == Andrew Lunn <andrew.lunn@ascom.ch> writes:
>> The synthetic target builds fine, but there is a run-time problem with
>> cxxsupp. It appears that libgcc now assumes that glibc has done some
>> initialization, setting up the %gs register to point at per-thread
>> data. This came up previously in the context of the -fstack-protector
>> flag, see the mailing list archives, but at the time we decided we
>> could live with the problem. It looks like there are now more
>> dependencies on getting this sorted - which I suspect will prove
>> challenging.
Andrew> What gcc and glibc are you using? For me cxxsupp runs and
Andrew> passes. So as always, it seems to very from system to
Andrew> system:
Andrew> lunn@londo:~/eCos/work$ gcc -v
Andrew> Using built-in specs.
Andrew> Target: i486-linux-gnu
Andrew> Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-3' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targets=all --enable-cld --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Andrew> Thread model: posix
Andrew> gcc version 4.3.3 (Debian 4.3.3-3)
Andrew> $ /lib/libc.so.6
Andrew> GNU C Library stable release version 2.7, by Roland McGrath et al.
Andrew> Copyright (C) 2007 Free Software Foundation, Inc.
Andrew> This is free software; see the source for copying conditions.
Andrew> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
Andrew> PARTICULAR PURPOSE.
Andrew> Compiled by GNU CC version 4.3.2.
Andrew> Compiled on a Linux >>2.6.26.1<< system on 2009-01-04.
An up-to-date Fedora 10 system. gcc 4.3.2-7, libc 2.9.
However I am not sure that really matters. The writing is on the wall:
the synthetic target will need %gs support in the not too distant
future to remain fully functional on a range of Linux distributions.
I don't know when I'll have time to look into this.
Bart
--
Bart Veer eCos Configuration Architect
eCosCentric Limited The eCos experts http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
next prev parent reply other threads:[~2009-02-04 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 17:51 John Dallaway
2009-02-03 22:10 ` Bart Veer
2009-02-04 0:56 ` Jonathan Larmour
2009-02-04 6:47 ` Andrew Lunn
2009-02-04 10:08 ` Bart Veer [this message]
2009-02-04 9:22 ` Target-specific build failures [ was Re: eCos 3.0 beta 1 punch list #1 ] 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=pn63jqfrb3.fsf@delenn.bartv.net \
--to=bartv@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).