Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: linux-mips@linux-mips.org, binutils@sources.redhat.com
Subject: Re: Problems generating shared library for MIPS using binutils-2.13...
Date: Fri, 25 Oct 2002 11:54:28 -0500	[thread overview]
Message-ID: <3DB97744.2010707@realitydiluted.com> (raw)
In-Reply-To: 20021025164402.GB6451@nevyn.them.org

Daniel Jacobowitz wrote:
> 
> More information:
> 
> Add -Wl,-v and give us the linker command line.
> 
> Is every object or library mentioned on that line already marked as
> MIPS-2 by readelf?  Even crt*, libc*?
>
I knew I was being stupid, crt* and libc* are mips1 *sigh*. Looks
like I have more work to do for my build system. Below is the verbose
output, but I think that's the problem for sure.

-Steve

mipsel-linux-gcc -shared -Wl,-v,-Amips2,-soname,libz.so.1 -o 
libz.so.1.1.4 adler32.o compress.o crc32.o gzio.o uncompr.o deflate.o 
trees.o zutil.o inflate.o infblock.o inftrees.o infcodes.o infutil.o 
inffast.o
collect2 version 3.2 (MIPSel GNU/Linux with ELF)
/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/../../../../mipsel-linux/bin/ld 
--eh-frame-hdr -EL -shared -o libz.so.1.1.4 
/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/../../../../mipsel-linux/lib/crti.o 
/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/crtbeginS.o 
-L/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2 
-L/opt/toolchains/uclibc/bin/../lib/gcc-lib 
-L/opt/toolchains/uclibc-crosstools-1.0.0/lib/gcc-lib/mipsel-linux/3.2 
-L/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/../../../../mipsel-linux/lib 
-L/opt/toolchains/uclibc-crosstools-1.0.0/lib/gcc-lib/mipsel-linux/3.2/../../../../mipsel-linux/lib 
-L/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/../../.. -v 
-Amips2 -soname libz.so.1 adler32.o compress.o crc32.o gzio.o uncompr.o 
deflate.o trees.o zutil.o inflate.o infblock.o inftrees.o infcodes.o 
infutil.o inffast.o -lgcc -lc -lgcc 
/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/crtendS.o 
/opt/toolchains/uclibc/bin/../lib/gcc-lib/mipsel-linux/3.2/../../../../mipsel-linux/lib/crtn.o
GNU ld version 2.13

  reply	other threads:[~2002-10-25 16:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 16:38 Problems generating shared library for MIPS using binutils-2.13 Steven J. Hill
2002-10-25 16:44 ` Daniel Jacobowitz
2002-10-25 16:54   ` Steven J. Hill [this message]
2002-10-25 17:06     ` Maciej W. Rozycki
2002-11-04 14:49       ` Steven J. Hill
2002-11-04 15:02         ` H. J. Lu
2002-11-04 16:57           ` Steven J. Hill
2002-11-04 17:11             ` H. J. Lu
2002-11-04 17:16               ` Steven J. Hill
2002-11-04 17:24                 ` H. J. Lu
2002-11-05 15:19         ` Richard Sandiford
2002-11-05 17:15           ` H. J. Lu
2002-11-05 17:26           ` Daniel Jacobowitz
2002-11-05 17:33             ` H. J. Lu
2002-11-05 18:17             ` Richard Sandiford
2002-11-05 18:32               ` Daniel Jacobowitz
2002-11-05 19:21                 ` Eric Christopher
2002-10-25 17:50 ` H. J. Lu

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=3DB97744.2010707@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=binutils@sources.redhat.com \
    --cc=dan@debian.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox