Re: [blfs-dev] Systemd-238 in BLFS-dev doesn't compile
On 04/05/2018 05:26 μμ, John Burrell wrote: Using the commands for systemd-238 in the sysutils section of the systemd version of the Book gives the following error: [316/1488] Compiling C object 'src/core/core@sta/dbus-mount.c.o'. FAILED: src/core/core@sta/dbus-mount.c.o ccache cc -Isrc/core/core@sta -Isrc/core -I../src/core -I. -I../ -Isrc/libsystemd-network -I../src/libsy stemd-network -I../src/libsystemd/sd-network -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device -I../src/libsystemd/sd-bus -Isrc/libudev -I../s rc/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login -Isrc/timesync -I../src/timesync -Isrc/res olve -I../src/resolve -Isrc/journal -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src /shared -Isrc/basic -I../src/basic -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -fdia gnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror= undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaratio n-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit- function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshad ow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffas t-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector - fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initiali zers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -MD -MQ 'src/core/core@sta/dbus-mount.c.o' -MF 'src/core/core@sta/dbus-mount.c.o.d' -o 'src/core /core@sta/dbus-mount.c.o' -c ../src/core/dbus-mount.c In file included from ../src/basic/util.h:47:0, from ../src/basic/hashmap.h:30, from ../src/shared/bus-util.h:31, from ../src/core/dbus-mount.c:21: ../src/basic/missing.h:528:17: error: expected identifier before numeric constant #define MS_MOVE 8192 This appears to be the same error identified in the LFS version of systemd-238. Should the commands that are in the LFS version: sed -i '527,565 d' src/basic/missing.h sed -i '24 d' src/core/load-fragment.c sed -i '53 a#include ' src/shared/bus-unit-util.c also be in the BLFS version? jb. It's been reported in the following thread too: http://lists.linuxfromscratch.org/pipermail/blfs-support/2018-April/080065.html Either the patch in the book must be replaced by the revised one or the sed commands by the LFS book must be used. -- Thanos -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] Systemd-238 in BLFS-dev doesn't compile
Using the commands for systemd-238 in the sysutils section of the systemd version of the Book gives the following error: [316/1488] Compiling C object 'src/core/core@sta/dbus-mount.c.o'. FAILED: src/core/core@sta/dbus-mount.c.o ccache cc -Isrc/core/core@sta -Isrc/core -I../src/core -I. -I../ -Isrc/libsystemd-network -I../src/libsy stemd-network -I../src/libsystemd/sd-network -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device -I../src/libsystemd/sd-bus -Isrc/libudev -I../s rc/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login -Isrc/timesync -I../src/timesync -Isrc/res olve -I../src/resolve -Isrc/journal -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src /shared -Isrc/basic -I../src/basic -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/uuid -fdia gnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -std=gnu99 -O0 -g -Wextra -Werror= undef -Wlogical-op -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaratio n-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn -Werror=missing-prototypes -Werror=implicit- function-declaration -Werror=missing-declarations -Werror=return-type -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshad ow -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time -Wnested-externs -ffas t-math -fno-common -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden -fstack-protector - fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter -Wno-missing-field-initiali zers -Wno-unused-result -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -include config.h -fPIC -pthread -MD -MQ 'src/core/core@sta/dbus-mount.c.o' -MF 'src/core/core@sta/dbus-mount.c.o.d' -o 'src/core /core@sta/dbus-mount.c.o' -c ../src/core/dbus-mount.c In file included from ../src/basic/util.h:47:0, from ../src/basic/hashmap.h:30, from ../src/shared/bus-util.h:31, from ../src/core/dbus-mount.c:21: ../src/basic/missing.h:528:17: error: expected identifier before numeric constant #define MS_MOVE 8192 This appears to be the same error identified in the LFS version of systemd-238. Should the commands that are in the LFS version: sed -i '527,565 d' src/basic/missing.h sed -i '24 d' src/core/load-fragment.c sed -i '53 a#include ' src/shared/bus-unit-util.c also be in the BLFS version? jb. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] Use optimize while building Vim
On 05/03/2018 09:00 PM, Xi Ruoyao wrote: On 2018-05-03 11:50 -0500, Bruce Dubbs wrote: I've never had a problem with vim using the standard build. Our general approach is that upstream knows best, so that we rarely change optimization flags. I am not familiar with the operation "using netrw to view directory content". Can you give some more detail on that? If we do change the optimization flags, we will need to do it in both LFS and BLFS. For example "vim ~". OK. I did know about that as well as vim pkg.tar.xz. Your term netrw was new to me. Is it possible the problem you mention is language/font specific? It's possible I mistyped something in the previous Vim installation, so after a new installation it seems to be solved. I can't reproduce the problem now. Sorry for the noise :(. No problem. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
