From: Dan Dickey <ddickey@charter.net>
To: Marcus Sundberg <erammsu@kieraypc01.p.y.ki.era.ericsson.se>
Cc: Rene Pachernegg <rene.pachernegg@apus.co.at>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: Building Glibc
Date: Tue, 11 Jan 2000 20:54:08 -0600 [thread overview]
Message-ID: <387BECD0.4FFDB494@charter.net> (raw)
In-Reply-To: kfyr9fo77re.fsf@kieraypc07.p.y.ki.era.ericsson.se
Marcus Sundberg wrote:
>
> "Rene Pachernegg" <rene.pachernegg@apus.co.at> writes:
>
> > Hello,
> >
> > When building the GNU libc on a cross-compiler (i686 --> PowerPc 603e)
> > I get the following linker error (current directory: elf):
> > ../libc_pic.a(init-first.os): In function '_dl_start':
> > init-first.os(.text+0xb8): multiple definition of '_dl_start'
> > dl-allobjs.os(.text0x0): first defined here Warning: size of symbol
> > '_dl_start' changed from 1576 to 16 in init-first.os collect2: ld
> > returned 1 exit status make[1]: *** [librtld.os] Error 1 make: ***
> > [elf/subdir_lib] Error2
> >
> > What can I do? Are there special linker/compiler options?
>
> What version of glibc are you using?
> How did you configure glibc?
> What make command line (s) did you use?
I'd also chime in with,
What version of the compiler are you using?
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-01-12 2:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-11 8:52 Building Glibc Rene Pachernegg
2000-01-11 19:01 ` Marcus Sundberg
2000-01-12 2:54 ` Dan Dickey [this message]
2000-01-12 8:10 ` Reni Pachernegg
2000-01-12 12:01 ` Marcus Sundberg
-- strict thread matches above, loose matches on Subject: below --
2000-01-12 11:37 kd
2000-01-12 12:29 ` Reni Pachernegg
2000-01-12 13:21 kd
2000-01-12 15:03 ` René Pachernegg
2000-01-12 22:55 ` Graham Stoney
2000-01-13 16:52 ` Reni Pachernegg
2000-01-13 17:23 ` Ben Sapp
2000-01-13 17:39 kd
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=387BECD0.4FFDB494@charter.net \
--to=ddickey@charter.net \
--cc=erammsu@kieraypc01.p.y.ki.era.ericsson.se \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=rene.pachernegg@apus.co.at \
/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 NNTP newsgroup(s).