Re: [ns] nam build fails (cannot find -lnsl) on FreeBSD 4.4

[Lloyd Wood <l.wood@eim.surrey.ac.uk>]

On Tue, 16 Oct 2001, Shill wrote:

> > I'd just delete -nsl from the makefile flags and see what happens.
>
> /home/abalk/ns-allinone-2.1b8/lib/libtcl8.3.a(tclUnixPipe.o): In
> function `TclpCreateTempFile':
> tclUnixPipe.o(.text+0xee): warning: tmpnam() possibly used unsafely;
> consider using mkstemp()
>
> Aside from this warning, it works.
>
> Any idea why ./configure doesn't detect the absence of libnsl?
 
there's a

LIBS="-lnsl  $LIBS" (even if $LIBS is empty)

and later a separate

  V_LIB="$V_LIB -lnsl" (even if V_LIB is empty)

making it very likely to get in there all by itself.


> >> The problem has already been documented:
> >> http://www.isi.edu/nsnam/archive/ns-users/webarch/current/msg02326.html
> 
> > That 'current' is going to haunt us in the long term.
> > Needs forcing to a year...
> 
> Wow... I have *no idea* what these sentences mean :)
> 
> Could you explain?

If you look at the web list archive, you'll see that the mhonarc
archives are split up, since they're large. There's one for each year.

http://www.isi.edu/nsnam/archive/ns-users/webarch/

There's a tendency to reference previous discussion via archive url,
as you have done above. Problem is, next year 'current' will be for
2002, breaking your link. And I hoped the berkeley->isi move breaking
all links was a one-off....

I'd have used '2001' for 2001 from the start. It's permanent.
(any retromangling of \/current\/ to \/2001\/ will, of course,
render this explanation impossible to follow.)

L.

<L.Wood@surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>