Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Adrian.Hulse@taec.toshiba.com
Cc: linux-mips@oss.sgi.com
Subject: Re: libtool warning on redhat 7.1 native mipsel compile
Date: Fri, 11 Jan 2002 11:56:43 -0800	[thread overview]
Message-ID: <20020111115643.A28700@lucon.org> (raw)
In-Reply-To: <OFC2A7FD37.680D7B25-ON88256B3E.00695F38@taec.com>; from Adrian.Hulse@taec.toshiba.com on Fri, Jan 11, 2002 at 11:53:42AM -0800

On Fri, Jan 11, 2002 at 11:53:42AM -0800, Adrian.Hulse@taec.toshiba.com wrote:
> 
> I have come across many libtool warnings when native compiling redhat 7.1
> packages on my mips board.
> 
> An example warning is :
> 
> *** Warning: This library needs some functionality provided by -lc
> *** I have the capability to make that library automatically link in when
> *** you link to this library. But I can only do this if you have a
> *** shared version of the library, which you do not appear to have.
> 

Does that cause any problems?


H.J.

  reply	other threads:[~2002-01-11 20:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-11 19:53 libtool warning on redhat 7.1 native mipsel compile Adrian.Hulse
2002-01-11 19:56 ` H . J . Lu [this message]
2002-01-11 20:12 ` Maciej W. Rozycki
  -- strict thread matches above, loose matches on Subject: below --
2002-01-11 20:08 Adrian.Hulse
2002-01-11 20:08 ` H . J . Lu
2002-01-12  5:26   ` Ralf Baechle
2002-01-12  5:42     ` H . J . Lu
2002-01-12  5:48       ` Ralf Baechle
2002-01-12 13:36       ` Robin Humble
2002-01-12 17:22         ` H . J . Lu
2002-01-13  4:04           ` Robin Humble
2002-01-13  6:27             ` H . J . Lu
2002-01-14 11:44               ` Maciej W. Rozycki
2002-01-14 17:50                 ` H . J . Lu
2002-01-15 12:57                   ` Brian Murphy
2002-01-15 15:46                     ` H . J . Lu
2002-01-14 11:35       ` Maciej W. Rozycki
2002-01-14 17:56         ` 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=20020111115643.A28700@lucon.org \
    --to=hjl@lucon.org \
    --cc=Adrian.Hulse@taec.toshiba.com \
    --cc=linux-mips@oss.sgi.com \
    /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