Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 21 Dec 1995 16:56:26 -0700
From:      Nate Williams <nate@rocky.sri.MT.net>
To:        =?KOI8-R?Q?=E1=CE=C4=D2=C5=CA_=FE=C5=D2=CE=CF=D7?= (aka Andrey A. Chernov, Black Mage) <ache@astral.msk.su>
Cc:        Nate Williams <nate@rocky.sri.MT.net>, current@freebsd.org, nate@freebsd.org
Subject:   Re: LD hits again :-(
Message-ID:  <199512212356.QAA04638@rocky.sri.MT.net>
In-Reply-To: <lzonUsm8R1@ache.dialup.ru>
References:  <MHL6QsmaU9@deep-thought.demos.su> <199512211857.LAA03453@rocky.sri.MT.net> <lzonUsm8R1@ache.dialup.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
> 
> >I'm pretty sure it's the linker stating that warning (whether it needs
> >to or not) and not an actual link bug.  I verified this by adding
> >warning symbols to the crypt.c in libcipher, and the linker now says.
> 
> >/usr/bin/ld -e start -dc -dp -o bdes /usr/lib/crt0.o -L../../lib/libcipher bdes.o -lcipher /usr/lib/libgcc.a -lc /usr/lib/libgcc.a
> 						      ^^^^^^^^^^^^^^^^^^^^
> 						      Your linker path is wrong, here
> 						      you need to update Makefile to -current

Read what I have above Andrey.  That's not a 'cc' line, that's a ld line
which is *exactly* the same line as cc uses.

> >For now, I'm going to ignore it.  Although it is still a bug, I don't
> >consider it a critical bug.
> 
> Secure is always critical.

But the bug is not a link bug, but a 'warning' bug.  The reason it shows
up in -current and not in -stable is because Poul added the warning
symbols to the crypt sources in libc/gen/crypt.c.

The bug is a 'visual' bug, and not a functional bug.


Nate



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512212356.QAA04638>