Dan Nicholson wrote:
> On 2/10/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>>> * in xorg-server, but there's no way to enable it through configure.
>>>You'd have to manually define "-DUSE_PAM". But, then you
>>>could have /etc/pam.d/xserver. I'm not sure why there
On 2/10/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote these words on 02/10/07 15:02 CST:
>
> > Yeah, we'll move to the new series of libXfont when Xorg-7.2 comes out
> > (any time now, but no official announcement yet). We can also drop the
> > security patch then, too. You co
Dan Nicholson wrote these words on 02/10/07 15:02 CST:
> Yeah, we'll move to the new series of libXfont when Xorg-7.2 comes out
> (any time now, but no official announcement yet). We can also drop the
> security patch then, too. You could probably use it with Xorg-7.1, but
> I haven't looked into
On 2/10/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Randy McMurchy wrote these words on 02/10/07 14:49 CST:
>
> > This mail being sent as just an FYI for the archives.
>
> I forgot to add that there is much more information about this at:
> http://wiki.linuxfromscratch.org/blfs/ticket/1988
Yea
On 2/10/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
> Dan Nicholson wrote:
> >
> > * in xorg-server, but there's no way to enable it through configure.
> >You'd have to manually define "-DUSE_PAM". But, then you
> >could have /etc/pam.d/xserver. I'm not sure why there's not an
> >eas
Randy McMurchy wrote these words on 02/10/07 14:49 CST:
> This mail being sent as just an FYI for the archives.
I forgot to add that there is much more information about this at:
http://wiki.linuxfromscratch.org/blfs/ticket/1988
--
Randy
rmlscsi: [bogomips 1003.26] [GNU ld version 2.16.1] [gcc
Hi all,
Apparently, the libXfont package we use in BLFS has not been updated
to use FreeType >=2.2.0. They are still using Internal API calls which
are now deprecated, and the build fails. I'm sure we can find a patch.
This mail being sent as just an FYI for the archives.
--
Randy
rmlscsi: [bo
[Moving this to blfs-dev, as the discussion is now moving towards
book development]
Dan Nicholson wrote:
> I just grepped all the sources for instances of pam or PAM. There are
> only two places it's used.
>
> * xdm, where it will try to use PAM if it find's it and you can
>create an /etc/pa
On Σαβ, Φεβ 10, at 10:46 Dan Nicholson wrote:
> On 2/10/07, Ag. Hatzimanikas <[EMAIL PROTECTED]> wrote:
> >
> > All I know (from another source but me,A.J.Mechelynck),is that some
> > warnings are
> > common and unavoidable,such as those that coming when you enable the various
> > interfaces e.g p
On 2/10/07, Bruce Dubbs <[EMAIL PROTECTED]> wrote:
>
> My question is: Why does the package try to install something *from* a
> location that is outside its own files. Its own files reside on, in
> this case,
>
> {/mnt/lfs}/tools/glibc-build/ and
> {/mnt/lfs}/tools/glibc-$glibc-version
>
> but it
Chris Staub wrote:
> Yes, but in general it doesn't matter *where* you build stuff, it will
> still work fine.
>
> However, this does seem to be an exception in the case of Glibc
> 2.5...I've been testing it myself, and I get a build failure due to the
> same problem, as it keeps complaining t
On 2/10/07, Chris Staub <[EMAIL PROTECTED]> wrote:
>
> Apparently, if there is an "include" dir one level up from the Glibc
> build dir, it automatically copies headers from there into the default
> include dir. Obviously, this means that if you build Glibc in /tools, it
> tries to copy from "glibc
Alexander E. Patrakov wrote these words on 02/09/07 23:59 CST:
> The issue is that sometimes Electric Fence is used not for testsuite, but
> for some other purpose (e.g.: in order to allow the person who develops the
> application to do better debugging). I wouldn't like it if one puts
> debugg
Matthew Burgess wrote:
> On Saturday 10 February 2007 06:23, Dan Winkler wrote:
>
>> i unpack the package in /mnt/lfs/tools then follow the instructions.
>
> Why? It's recommended that all packages should live in /sources and be
> unpacked there. See 3.1: Introduction
>
> "Downloaded packages
Gilles Espinasse kirjoitti:
> - Original Message -
> From: "Robert Connolly" <[EMAIL PROTECTED]>
> To: "Hardened LFS Development List"
> Sent: Saturday, February 10, 2007 9:10 AM
> Subject: Re: Install Vim to /bin?
>
>> I copied vim, symlinked vi to it, in a chroot with just bash and
> l
On Saturday 10 February 2007 06:23, Dan Winkler wrote:
> i unpack the package in /mnt/lfs/tools then follow the instructions.
Why? It's recommended that all packages should live in /sources and be
unpacked there. See 3.1: Introduction
"Downloaded packages and patches will need to be stored so
16 matches
Mail list logo
