This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Re: remote linking.
Elias Athanasopoulos <eathan@otenet.gr> writes:
|> On Fri, May 10, 2002 at 09:04:56AM -0400, Diego Novillo wrote:
|> >
|> > > > > % gcc -static foo.c -L192.168.1.2:/usr/lib/ -lbar -o foo
|> > > >
|> > > > Sorry, I don't think such a feature makes any sense. You can nfs
|> > > > mount remote directories if you want to do this.
|> > >
|> > I agree. What's wrong with
|> >
|> > $ wget 192.168.1.2:/usr/lib/libbar.a
|> > $ gcc -static foo.c -L. -lbar -o foo
|> >
|> > No need to re-invent the wheel.
|>
|> Only the static case resembles to a single file transfer. Consider
|> the dynamic case.
|>
|> An example: a user wants to run the new version of gfoo. 'gfoo' is a
|> Gnome application with N depedencies. Normally, he/she must upgrade
|> all the required libraries. Using remote linking, he/she can compile
|> the source and run it, as long as he/she maintains an Internet
|> connection and permissions to use a lib server. That is zero modifi-
|> cations to the local system.
And what are you missing that NFS does not implement?
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE GmbH, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."