On 09/03/14 19:16, William Harrington wrote:


Okay I have had a successful build with the x86_64-64 book regarding the changes required to using libblkid from tools for e2fsprogs and systemd and moving util-linux after systemd and dbus. And added test suite commands for systemd.

Of course we'll need to adjust some commands for the multilib books.

For e2fsprogs:

sed -i -e 's|^LD_LIBRARY_PATH.*|&:/tools/lib|' tests/test_config
LIBS=-L/tools/lib CFLAGS="-I/tools/include" PKG_CONFIG_PATH=/tools/lib/pkgconfig ../configure.........

For systemd:

cat > config.cache << "EOF"
KILL=/bin/kill
HAVE_BLKID=1
BLKID_LIBS="-L/tools/lib -lblkid"
BLKID_CFLAGS="-I/tools/include/blkid"
EOF

sed -i "s:blkid/::" src/udev/udev-builtin-blkid.c   (before configure)

sed -i s:test/udev-test.pl::g Makefile (for a test suite failure before make -k check)
make -k check

And then for util-linux after systemd and dbus:

Same commands except this time it'll link against libudev and will include addition information for UUID and other output for findmnt and lsblk.
why not just rebuild and install the two relevant programs after systemd, seems much cleaner to me or am I missing something

You can refer to the LFS systemd branch book and look at ch6 e2fsprogs and systemd builds to see what I am talking about for changes utilizing /tools/lib/liblkid. I did also adjust Systemd commands to not use LIBRARAY_PATH=/tools/lib make and instead set BLKID_LIBS="-L/tools/lib -lblkid"

For Dbus: I may replace that this package does not have a test suite text to state that there is a test suite but requires additional packages from cblfs or so. But since cblfs is quite old, I don't know if our current version of dbus is the same or needs updated for required packages supporting the dbus test suite. I can refer to BLFS for that at the moment.
Seems a sane choice, with wording along the lines as you said

Any suggestions are requested. I plan to make the changes sometime today or tomorrow after I test a multilib build.

Sincerely,

William Harrington
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org

regards

Martin
_______________________________________________
Clfs-dev mailing list
[email protected]
http://lists.cross-lfs.org/listinfo.cgi/clfs-dev-cross-lfs.org

Reply via email to