From: Jeffrey A Law <law@redhat.com>
To: Alan Modra <alan@linuxcare.com.au>
Cc: Paul Bame <bame@fc.hp.com>,
John David Anglin <dave@hiauly1.hia.nrc.ca>,
parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] where to put 64 bit libmilli?
Date: Tue, 02 Jan 2001 21:15:51 -0700 [thread overview]
Message-ID: <2276.978495351@upchuck> (raw)
In-Reply-To: Your message of Wed, 03 Jan 2001 15:11:33 +1100. <Pine.LNX.4.21.0101031509470.24351-100000@front.linuxcare.com.au>
In message <Pine.LNX.4.21.0101031509470.24351-100000@front.linuxcare.com.au>y
ou write:
> Ah, but that's where the automagic linker search for libmilli come into
> play. Effectively, libmilli is always mentioned on the "command line"
Does this automagic search also happen when you build shared libraries?
[ Yes, I'm very familiar with HP's automagic searching for libmilli.a. I also
think it's a terrible mistake as a design decision. ]
jeff
next prev parent reply other threads:[~2001-01-03 4:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 19:25 [parisc-linux] where to put 64 bit libmilli? Paul Bame
2001-01-02 19:39 ` John David Anglin
2001-01-02 19:58 ` Paul Bame
2001-01-02 20:17 ` Jeffrey A Law
2001-01-03 1:46 ` Alan Modra
2001-01-03 1:57 ` Matthew Wilcox
2001-01-03 2:34 ` Alan Modra
2001-01-03 3:37 ` Jeffrey A Law
2001-01-03 4:11 ` Alan Modra
2001-01-03 4:15 ` Jeffrey A Law [this message]
2001-01-03 4:44 ` Alan Modra
2001-01-04 4:04 ` Jeffrey A Law
2001-01-04 5:20 ` Alan Modra
2001-01-04 6:18 ` John David Anglin
2001-01-04 7:03 ` Alan Modra
2001-01-04 16:36 ` Paul Bame
2001-01-04 17:06 ` Jeffrey A Law
2001-01-04 17:29 ` Jeffrey A Law
2001-01-04 17:37 ` Jeffrey A Law
2001-01-04 17:41 ` Paul Bame
2001-01-04 23:52 ` Alan Modra
-- strict thread matches above, loose matches on Subject: below --
2001-01-04 19:00 Cary Coutant
2001-01-04 19:15 ` Grant Grundler
2001-01-04 21:20 Cary Coutant
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=2276.978495351@upchuck \
--to=law@redhat.com \
--cc=alan@linuxcare.com.au \
--cc=bame@fc.hp.com \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@thepuffingroup.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 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.