Re: [lfs-dev] e2fsprogs

2014-02-04 Thread Bruce Dubbs
Armin K. wrote: > On 02/05/2014 06:12 AM, Bruce Dubbs wrote: >> Armin K. wrote: >>> On 02/04/2014 11:19 PM, Bruce Dubbs wrote: Armin K. wrote: >> The disable- prevents e2fsprogs from building/installing libuuid and libblkid, but it still needs them and with the change and at this poi

Re: [lfs-dev] e2fsprogs

2014-02-04 Thread Armin K.
On 02/05/2014 06:12 AM, Bruce Dubbs wrote: > Armin K. wrote: >> On 02/04/2014 11:19 PM, Bruce Dubbs wrote: >>> Armin K. wrote: > >>> The disable- prevents e2fsprogs from building/installing libuuid and >>> libblkid, but it still needs them and with the change and at this point >>> in building pack

Re: [lfs-dev] e2fsprogs

2014-02-04 Thread Bruce Dubbs
Armin K. wrote: > On 02/04/2014 11:19 PM, Bruce Dubbs wrote: >> Armin K. wrote: >> The disable- prevents e2fsprogs from building/installing libuuid and >> libblkid, but it still needs them and with the change and at this point >> in building packages in Chapter 6, it needs the PKG_CONFIG_PATH to f

Re: [blfs-dev] Why/Why not systemd

2014-02-04 Thread Aleksandar Kuktin
>On Tue, 04 Feb 2014 18:26:35 +0100 >Igor Živković wrote: > http://wizardofbits.tumblr.com/post/45232318557/systemd-more-like-shit-stemd Nevermind the systemd flammage going on in here, the single most important contribution of this article is that he *proposed an alternative* in the form of run

Re: [lfs-dev] e2fsprogs

2014-02-04 Thread Armin K.
On 02/04/2014 11:19 PM, Bruce Dubbs wrote: > Armin K. wrote: >> I've built e2fsprogs and it seems broken in a way with the util-linux >> chapter 5 move. >> >> I still don't understand why PKG_CONFIG_PATH has to be exported >> seperately. > > The disable- prevents e2fsprogs from building/installing

Re: [lfs-dev] e2fsprogs

2014-02-04 Thread Bruce Dubbs
Armin K. wrote: > I've built e2fsprogs and it seems broken in a way with the util-linux > chapter 5 move. > > I still don't understand why PKG_CONFIG_PATH has to be exported > seperately. The disable- prevents e2fsprogs from building/installing libuuid and libblkid, but it still needs them and wi

Re: [lfs-dev] Unnecessarry command in Groff instructions

2014-02-04 Thread Bruce Dubbs
Armin K. wrote: > In the install command, > > mkdir -pv /usr/share/doc/groff-1.22/pdf > make install > > The mkdir is not necessarry. make install output has: > > > > test -d /usr/share/doc/groff-1.22.2/pdf \ >|| /bin/sh /sources/groff-1.22.2/mkinstalldirs > /usr/share/doc/groff-1.22.2/pdf > mk

Re: [blfs-dev] Why/Why not systemd

2014-02-04 Thread Armin K.
On 02/04/2014 10:59 PM, Aleksandar Kuktin wrote: >> On Tue, 04 Feb 2014 21:35:03 +0100 >> "Armin K." wrote: > >> If an user logs via SSH or VNC or whatever that's not a "real >> console", logind won't grant such users permissions to use video >> card, audio device, cdrom, usb sticks, etc. I, for

Re: [blfs-dev] Why/Why not systemd

2014-02-04 Thread Aleksandar Kuktin
>On Tue, 04 Feb 2014 21:35:03 +0100 >"Armin K." wrote: > If an user logs via SSH or VNC or whatever that's not a "real > console", logind won't grant such users permissions to use video > card, audio device, cdrom, usb sticks, etc. I, for one, wouldn't want > someone to access my cdrom device whe

[lfs-dev] Unnecessarry command in Groff instructions

2014-02-04 Thread Armin K.
In the install command, mkdir -pv /usr/share/doc/groff-1.22/pdf make install The mkdir is not necessarry. make install output has: test -d /usr/share/doc/groff-1.22.2/pdf \ || /bin/sh /sources/groff-1.22.2/mkinstalldirs /usr/share/doc/groff-1.22.2/pdf mkdir -p -- /usr/share/doc/groff-1.22.2/

[blfs-dev] Tex (#4647)

2014-02-04 Thread Ken Moffat
This ticket lists a whole lot of changes to how we build Tex from source. I took it, because I don't (in general) like packages which use their own static versions of system libs. But I now see that the following are external references: GD, t1lib, ZZIPlib, TECkit, Graphite, and also CLISP (not

[lfs-dev] e2fsprogs

2014-02-04 Thread Armin K.
I've built e2fsprogs and it seems broken in a way with the util-linux chapter 5 move. I still don't understand why PKG_CONFIG_PATH has to be exported seperately. It works here when used inline, ie LIBS=-L/tools/lib \ CFLAGS=-I/tools/include\ ../configure --prefix=/usr

Re: [lfs-dev] Chapter 5 Check and Util-Linux commands consistency

2014-02-04 Thread Armin K.
On 02/04/2014 08:59 PM, Bruce Dubbs wrote: > Armin K. wrote: >> Check package has: >> >> PKG_CONFIG= ./configure --prefix=/tools >> >> While Util-Linux has: >> >> ./configure --prefix=/tools\ >> --disable-makeinstall-chown\ >> --without-systemdsystemuni

Re: [lfs-dev] Chapter 5 Check and Util-Linux commands consistency

2014-02-04 Thread Bruce Dubbs
Armin K. wrote: > Check package has: > > PKG_CONFIG= ./configure --prefix=/tools > > While Util-Linux has: > > ./configure --prefix=/tools\ > --disable-makeinstall-chown\ > --without-systemdsystemunitdir \ > PKG_CONFIG="" > > PKG_CONFIG in

[lfs-dev] Chapter 5 Check and Util-Linux commands consistency

2014-02-04 Thread Armin K.
Check package has: PKG_CONFIG= ./configure --prefix=/tools While Util-Linux has: ./configure --prefix=/tools\ --disable-makeinstall-chown\ --without-systemdsystemunitdir \ PKG_CONFIG="" PKG_CONFIG in both cases do the same, yet they're use