From: John Dallaway <john@dallaway.org.uk>
To: Michael Bergandi <mbergandi@gmail.com>
Cc: eCos Developer List <ecos-devel@ecos.sourceware.org>
Subject: Re: Build error on 'make tests' for synthetic target
Date: Wed, 02 Feb 2011 21:06:00 -0000 [thread overview]
Message-ID: <4D49C758.6050705@dallaway.org.uk> (raw)
In-Reply-To: <AANLkTimfYPuqVHHSuZ82F0vhjG8=Co3tdDdEM_8EyyFP@mail.gmail.com>
Michael
Michael Bergandi wrote:
> In the mean time, I tried to just build all of the tests and the build
> errored out with the following:
>
> make -r -C infra/current tests
> make[1]: Entering directory `/home/mike/ecos-cvs/synthbuild/infra/current'
> gcc -L/home/mike/ecos-cvs/synthbuild/install/lib -Ttarget.ld -o
> /home/mike/ecos-cvs/synthbuild/install/tests/infra/current/tests/cxxsupp
> tests/cxxsupp.o -g -nostdlib -Wl,-static -Wl,--fatal-warnings
> /usr/lib/gcc/i486-linux-gnu/4.4.3/libsupc++.a(cp-demangle.o): In
> function `.L644':
> (.text+0x3317): undefined reference to `__sprintf_chk'
> collect2: ld returned 1 exit status
> make[1]: *** [/home/mike/ecos-cvs/synthbuild/install/tests/infra/current/tests/cxxsupp]
> Error 1
> make[1]: Leaving directory `/home/mike/ecos-cvs/synthbuild/infra/current'
> make: *** [tests] Error 2
>
> I am running on Ubuntu 10.04.1 LTS. Here is some config info:
This looks like a build issue related to your Linux distro. Please raise
a bug report at http://bugs.ecos.sourceware.org and include the above
error message plus the output of "gcc -v" and "uname -a".
Thank you
John Dallaway
eCos maintainer
next prev parent reply other threads:[~2011-02-02 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 20:41 Michael Bergandi
2011-02-02 21:06 ` John Dallaway [this message]
2011-02-02 22:20 ` Michael Bergandi
2011-02-02 21:42 ` Sergei Gavrikov
2011-02-03 13:45 ` Michael Bergandi
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=4D49C758.6050705@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@ecos.sourceware.org \
--cc=mbergandi@gmail.com \
/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).