From: Thiemo Seufer <ica2_ts@csv.ica.uni-stuttgart.de>
To: Eric Christopher <echristo@redhat.com>
Cc: Atsushi Nemoto <anemo@mba.ocn.ne.jp>,
jsun@mvista.com, linux-mips@linux-mips.org,
binutils@sources.redhat.com
Subject: Re: Huge dynamically linked program does not run on mips-linux
Date: Fri, 7 Nov 2003 17:40:43 +0100 [thread overview]
Message-ID: <20031107164043.GA24269@rembrandt.csv.ica.uni-stuttgart.de> (raw)
In-Reply-To: <1067968386.3491.7.camel@ghostwheel.sfbay.redhat.com>
Eric Christopher wrote:
[snip]
> > Yes. mips-linux and mipsel-linux target (host is i386). Both target
> > generate broken binary for my test program.
> >
> > eric> And where would I find the sources?
> >
> > I'm using plain binutils 2.14 and gcc 3.3.2 from gnu.org FTP site,
> > binutils 2.14.90.0.7 from
> > http://www.kernel.org/pub/linux/devel/binutils/.
>
> I'm using mainline gcc, but I meant the python-qt sources you were
> compiling.
It was python-qt-3.8 from debian unstable, compiled with
"gcc (GCC) 3.3.2 (Debian)" and binutils
"2.14.90.0.7 20031029 Debian GNU/Linux"
An attempt to link with CVS ld shows the same BFD assertion.
Thiemo
next prev parent reply other threads:[~2003-11-07 16:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 8:11 Huge dynamically linked program does not run on mips-linux Atsushi Nemoto
2003-10-29 7:32 ` Atsushi Nemoto
2003-10-29 18:14 ` Jun Sun
2003-10-29 18:15 ` Daniel Jacobowitz
2003-10-30 1:53 ` Thiemo Seufer
2003-10-30 2:25 ` Eric Christopher
2003-11-04 5:21 ` Atsushi Nemoto
2003-11-04 8:05 ` Eric Christopher
2003-11-04 11:02 ` Atsushi Nemoto
2003-11-04 17:53 ` Eric Christopher
2003-11-06 16:54 ` Atsushi Nemoto
2003-12-01 5:07 ` Atsushi Nemoto
2003-11-07 16:40 ` Thiemo Seufer [this message]
2003-11-07 20:51 ` Eric Christopher
2003-10-30 12:54 ` Atsushi Nemoto
2003-11-04 16:17 ` Daniel Jacobowitz
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=20031107164043.GA24269@rembrandt.csv.ica.uni-stuttgart.de \
--to=ica2_ts@csv.ica.uni-stuttgart.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=binutils@sources.redhat.com \
--cc=echristo@redhat.com \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.