Mark Murray wrote:
>
> > Why does crypt need to be in libc? Not even a significant fraction of
> > applications need crypt?
>
> Goes for very many libc components. Quite a lot of userland needs libcrypt
> (not much as a proportion, but a non-insignificant number).
This runs counter to my gut i
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
>-=-=-
>===> libexec/fingerd
>cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi
>ngerd.c
>cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil
>/usr/obj/src/src/i386/usr/lib/l
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
>Brian, I'm afraid you broke libutil... Every program using libutil now must
>depend on libcrypt too.
>
>-=-=-
>===> libexec/fingerd
>cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi
>ngerd.c
>cc -O -p
On Tue, 22 Aug 2000, Garrett Wollman wrote:
> > -On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
> >> Brian, I'm afraid you broke libutil... Every program using libutil now must
> >> depend on libcrypt too.
>
> No. This is precisely why shared libraries have dependencies. For
>
On Tue, 22 Aug 2000, Garrett Wollman wrote:
> <<[EMAIL PROTECTED]> said:
>
> > -On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
> >> Brian, I'm afraid you broke libutil... Every program using libutil now must
> >> depend on libcrypt too.
>
> No. This is precisely why shared lib
< said:
> -On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
>> Brian, I'm afraid you broke libutil... Every program using libutil now must
>> depend on libcrypt too.
No. This is precisely why shared libraries have dependencies. For
static linking, what Brian has done Just Works.
> A growing libc makes static binaries grow and makes it more difficult to
> strip out unneeded functionality from a minimalist system install. I'd
> been inclined to try and move things the other way and strip stuff out
> of libc into separate libraries but that's obviously not in vogue at the
>
> -On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
> >Brian, I'm afraid you broke libutil... Every program using libutil now must
> >depend on libcrypt too.
>
> Alternatively the sentiment just rose why we couldn't just collapse the
> crypt/hash functions of libcrypt into libc.
A
> > >> Alternatively the sentiment just rose why we couldn't just collapse the
> > >> crypt/hash functions of libcrypt into libc.
> > >>
> > >> It would make sense.
> > >
> > >It would make even make more sense to convince the other BSD to do the same
> > >(haven't checked recently what they do) a
On Tue, 22 Aug 2000 17:25:50 +0100, Paul Richards wrote:
> Is there any current policy on what libc is?
For some reason, I seem to remember Bruce Evans once calling it "the
kitchen sink". :-)
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in
Jeroen Ruigrok van der Werven wrote:
>
> -On [2822 17:55], Ollivier Robert ([EMAIL PROTECTED]) wrote:
> >According to Jeroen Ruigrok van der Werven:
> >> Alternatively the sentiment just rose why we couldn't just collapse the
> >> crypt/hash functions of libcrypt into libc.
> >>
> >> It would
-On [2822 17:55], Ollivier Robert ([EMAIL PROTECTED]) wrote:
>According to Jeroen Ruigrok van der Werven:
>> Alternatively the sentiment just rose why we couldn't just collapse the
>> crypt/hash functions of libcrypt into libc.
>>
>> It would make sense.
>
>It would make even make more sense
According to Jeroen Ruigrok van der Werven:
> Alternatively the sentiment just rose why we couldn't just collapse the
> crypt/hash functions of libcrypt into libc.
>
> It would make sense.
It would make even make more sense to convince the other BSD to do the same
(haven't checked recently what
-On [2822 17:30], Ollivier Robert ([EMAIL PROTECTED]) wrote:
>Brian, I'm afraid you broke libutil... Every program using libutil now must
>depend on libcrypt too.
Alternatively the sentiment just rose why we couldn't just collapse the
crypt/hash functions of libcrypt into libc.
It would make
Brian, I'm afraid you broke libutil... Every program using libutil now must
depend on libcrypt too.
-=-=-
===> libexec/fingerd
cc -O -pipe -I/usr/obj/src/src/i386/usr/include -c /src/src/libexec/fingerd/fi
ngerd.c
cc -O -pipe -I/usr/obj/src/src/i386/usr/include -o fingerd fingerd.o -lutil
/
15 matches
Mail list logo
