From: "Øyvind Harboe" <oyvind.harboe@zylin.com>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] Linker problems when trying to upgrade gcc
Date: Tue, 13 Oct 2009 11:22:00 -0000 [thread overview]
Message-ID: <c09652430910130421h1038666dma782824e3de25ba8@mail.gmail.com> (raw)
I tried to upgrade to gcc 4.x and got lots of these error messages
during linking:
install/include/cyg/libc/time/time.inl:210: multiple definition of
`cyg_libc_time_setzoneoffsets'
Does it ring any bells?
This was with an arm-elf toolchain.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2009-10-13 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 11:22 Øyvind Harboe [this message]
2009-10-13 15:28 ` [ECOS] Solid State IDE (again!) Jim Bradleigh
2009-10-13 15:48 ` Jim Bradleigh
2009-10-13 16:33 ` [ECOS] Attempt to load ELF data xxx which is not valid Jim Bradleigh
2009-10-13 16:38 ` Gary Thomas
2009-10-13 16:43 ` David Brennan
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=c09652430910130421h1038666dma782824e3de25ba8@mail.gmail.com \
--to=oyvind.harboe@zylin.com \
--cc=ecos-discuss@ecos.sourceware.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).