All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: linux-mips@linux-mips.org
Cc: binutils@sources.redhat.com
Subject: Problems generating shared library for MIPS using binutils-2.13...
Date: Fri, 25 Oct 2002 11:38:25 -0500	[thread overview]
Message-ID: <3DB97381.8070501@realitydiluted.com> (raw)

Greetings.

I'm doing something stupid here, so please help me out. I am trying
to create a shared library with gcc passing parameters to the linker
and it is not working.

I compiled all the object files with '-mips2' and then I attempt to
create the shared library with:

    mipsel-linux-gcc -shared -Wl,-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

The object files are all mips2, but the generated '.so' object
is mips1?! What am I not understanding? I am using binutils-2.13,
gcc-3.2 and uClibc-0.9.15. The use of uClibc is not the problem.

-Steve

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

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 16:38 Steven J. Hill [this message]
2002-10-25 16:44 ` Problems generating shared library for MIPS using binutils-2.13 Daniel Jacobowitz
2002-10-25 16:54   ` Steven J. Hill
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=3DB97381.8070501@realitydiluted.com \
    --to=sjhill@realitydiluted.com \
    --cc=binutils@sources.redhat.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.