On 10/02/2021 02:49, Ken Moffat wrote:
On Tue, Feb 09, 2021 at 05:14:09PM -0500, Jean-Marc Pigeon wrote:
Hello,
On Tue, 2021-02-09 at 18:27 +, Ken Moffat wrote:
On Tue, Feb 09, 2021 at 12:29:14AM +, Ken Moffat wrote:
On Mon, Feb 08, 2021 at 03:52:35AM +, Ken Moffat wrote:
On 08/02/2021 05:05, Bruce Dubbs wrote:
On 2/7/21 9:52 PM, Ken Moffat wrote:
On Mon, Feb 08, 2021 at 11:14:22AM +0800, xry...@mengyan1223.wang wrote:
Please help me to test my glibc workaround in this thread. If it
works,
crt1.o should have no "needed" ISA markers (even x86-64-baseline
On 07/02/2021 18:19, Bruce Dubbs wrote:
On 2/7/21 8:11 AM, Pierre Labastie wrote:
On Sun, 2021-02-07 at 14:15 +0100, Pierre Labastie wrote:
On Sun, 2021-02-07 at 13:38 +0100, Frans de Boer wrote:
LS,
Finally had a change to finish the LFS build. Alas, the grub-
install
reported the old error
On 07/02/2021 15:26, Jim Martin wrote:
On 2/7/21 6:38 AM, Frans de Boer wrote:
LS,
Finally had a change to finish the LFS build. Alas, the grub-install
reported the old error "Decompression is too big".
Here is the solution to add to the section to compile grub:
# Patch gentpl.p
LS,
Finally had a change to finish the LFS build. Alas, the grub-install
reported the old error "Decompression is too big".
Here is the solution to add to the section to compile grub:
# Patch gentpl.py to avoid an error from grub-mkinstall "Decompressor is
too big"
# Source:
On 06/02/2021 15:46, Xi Ruoyao wrote:
On 2021-02-06 14:56 +0100, Frans de Boer wrote:
On 06/02/2021 14:34, Pierre Labastie wrote:
On Sat, 2021-02-06 at 13:43 +0100, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05
On 06/02/2021 14:34, Pierre Labastie wrote:
On Sat, 2021-02-06 at 13:43 +0100, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223
On 06/02/2021 14:34, Pierre Labastie wrote:
On Sat, 2021-02-06 at 13:43 +0100, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223
On 06/02/2021 14:34, Pierre Labastie wrote:
On Sat, 2021-02-06 at 13:43 +0100, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT-readelf -a $LFS/lib/libc.so.6 | grep
On 05/02/2021 22:23, Frans de Boer wrote:
On 05/02/2021 21:54, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans
On 05/02/2021 21:54, Frans de Boer wrote:
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT
On 05/02/2021 21:35, Pierre Labastie wrote:
On Fri, 2021-02-05 at 20:54 +0100, Frans de Boer wrote:
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT-readelf -a $LFS/lib/libc.so.6 | grep
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT-readelf -a $LFS/lib/libc.so.6 | grep ISA
(in host distro)
and config.log of glibc (both ch6 and ch8)?
Sorry for bad formating (using my phone
On 05/02/2021 20:16, Frans de Boer wrote:
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT-readelf -a $LFS/lib/libc.so.6 | grep ISA
(in host distro)
and config.log of glibc (both ch6 and ch8)?
Sorry for bad formating (using my phone
On 05/02/2021 16:25, xry...@mengyan1223.wang wrote:
Hi Frans,
Could you send the result of
$LFS_TGT-readelf -a $LFS/lib/libc.so.6 | grep ISA
(in host distro)
and config.log of glibc (both ch6 and ch8)?
Sorry for bad formating (using my phone to reply)
Just started recompiling glibc 2.33
On 05/02/2021 13:42, Ken Moffat wrote:
On Fri, Feb 05, 2021 at 12:31:56PM +0100, Frans de Boer wrote:
On 05/02/2021 12:29, Frans de Boer wrote:
After the 'file' issue, I started rebuilding LFS. Just to find out that
it stops with the message
'/lib/libc.so.6: CPU ISA level is lower than
On 05/02/2021 12:29, Frans de Boer wrote:
After the 'file' issue, I started rebuilding LFS. Just to find out
that it stops with the message
'/lib/libc.so.6: CPU ISA level is lower than required'
I use a Phenom II X4 365, but that seems now outdated?
--- Frans
Sorry, have to add
After the 'file' issue, I started rebuilding LFS. Just to find out that
it stops with the message
'/lib/libc.so.6: CPU ISA level is lower than required'
I use a Phenom II X4 365, but that seems now outdated?
--- Frans
--
A: Yes, just like thatA: Ja, net zo
Q: Oh,
On 04/02/2021 22:19, Bruce Dubbs wrote:
On 2/4/21 2:50 PM, Frans de Boer wrote:
On 04/02/2021 21:21, Pierre Labastie wrote:
On Thu, 2021-02-04 at 20:03 +0100, Frans de Boer wrote:
On 04/02/2021 16:22, Scott Andrews wrote:
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new instructions
On 04/02/2021 21:21, Pierre Labastie wrote:
On Thu, 2021-02-04 at 20:03 +0100, Frans de Boer wrote:
On 04/02/2021 16:22, Scott Andrews wrote:
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new instructions for compiling file-5.39 in the first phase,
are
incomplete. As it turns out, you can only
On 04/02/2021 16:22, Scott Andrews wrote:
On 2/4/21 9:14 AM, Frans de Boer wrote:
The new instructions for compiling file-5.39 in the first phase, are
incomplete. As it turns out, you can only compile file when the
configure command is augmented with '--disable-libseccomp'. The file
$LFS/usr
The new instructions for compiling file-5.39 in the first phase, are
incomplete. As it turns out, you can only compile file when the
configure command is augmented with '--disable-libseccomp'. The file
$LFS/usr/include/libseccomp/seccomp.h does not exist yet, cause to halt
compilation with the
On 25/01/2021 15:30, Frans de Boer wrote:
LS,
If have a problem with systemd and network. journalctl reports
"systemd-networkd.service: Failed to determine user credentials: No
such process"
I have searched internet but found only older references to this
message, however, this i
LS,
If have a problem with systemd and network. journalctl reports
"systemd-networkd.service: Failed to determine user credentials: No such
process"
I have searched internet but found only older references to this
message, however, this in relation to other units.
I use the settings as
On 06-07-2020 17:18, Bruce Dubbs wrote:
On 7/6/20 8:57 AM, Frans de Boer wrote:
I have found messages from some years ago asking about the
possibility of giving examples how to configure LFS for use on IPv4
and IPv6. Now, LFS is still using the ifconfig utility including the
ipconfig.xxx file
I have found messages from some years ago asking about the possibility
of giving examples how to configure LFS for use on IPv4 and IPv6. Now,
LFS is still using the ifconfig utility including the ipconfig.xxx file.
I found references to this utility way back in 1983, so it looks very
much
On 2020-06-28 22:24, Scott Andrews wrote:
On Sun, 28 Jun 2020 19:41:20 +0200
Frans de Boer wrote:
On 28-06-2020 14:07, Scott Andrews wrote:
On Sun, 28 Jun 2020 13:42:10 +0200
Frans de Boer wrote:
LS,
Currently, the previous chapter 5 has been split into 3 separate
chapters
On 28-06-2020 16:36, Pierre Labastie wrote:
On Sun, 2020-06-28 at 15:43 +0200, Frans de Boer wrote:
On 28-06-2020 15:16, Pierre Labastie wrote:
On Sun, 2020-06-28 at 13:42 +0200, Frans de Boer wrote:
LS,
Currently, the previous chapter 5 has been split into 3 separate
chapters. It is obvious
On 28-06-2020 14:07, Scott Andrews wrote:
On Sun, 28 Jun 2020 13:42:10 +0200
Frans de Boer wrote:
LS,
Currently, the previous chapter 5 has been split into 3 separate
chapters. It is obvious why the new chapter 7 exists.
However, chapter 5 and 6 are a bit puzzling. There are no extra
actions
On 28-06-2020 15:16, Pierre Labastie wrote:
On Sun, 2020-06-28 at 13:42 +0200, Frans de Boer wrote:
LS,
Currently, the previous chapter 5 has been split into 3 separate
chapters. It is obvious why the new chapter 7 exists.
However, chapter 5 and 6 are a bit puzzling. There are no extra
actions
LS,
Currently, the previous chapter 5 has been split into 3 separate
chapters. It is obvious why the new chapter 7 exists.
However, chapter 5 and 6 are a bit puzzling. There are no extra actions
between chapter 6 and 5, in fact one could argue that 5 and 6 can be
fussed together.
The only
On 2020-06-22 20:02, Frans de Boer wrote:
On 2020-06-22 14:54, Xi Ruoyao wrote:
echo "#include | x86_64-cross-linux-gnu-g++ -E -x c++ -
Result:
# 1 ""
# 1 ""
# 1 ""
# 1 "/mnt/lfs/usr/include/stdc-predef.h" 1 3 4
# 1 "" 2
# 1 &qu
On 2020-06-22 14:54, Xi Ruoyao wrote:
echo "#include | x86_64-cross-linux-gnu-g++ -E -x c++ -
Result:
# 1 ""
# 1 ""
# 1 ""
# 1 "/mnt/lfs/usr/include/stdc-predef.h" 1 3 4
# 1 "" 2
# 1 ""
:1:10: fatal error: iostream: No such file or directory
compilation terminated.
--- Frans
--
A: Yes,
LS,
Next issue, while compiling ncurses-6.2 i get the next message:
x86_64-cross-linux-gnu-g++ -DHAVE_CONFIG_H -I../c++ -I. -I../include
-D_DEFAULT_SOURCE -D_XOPEN_SOURCE=600 -DNDEBUG -O2 -fPIC -c
../c++/cursesf.cc -o ../obj_s/cursesf.o
In file included from ../c++/cursesw.h:41,
On 20-06-2020 20:50, Frans de Boer wrote:
On 20-06-2020 20:43, Xi Ruoyao wrote:
On 2020-06-20 20:10 +0200, Frans de Boer wrote:
Looking at the config.log, I see that libc_cv_slibdir is set to /lib.
However, libdir is automatically set to /lib64. I did specified in the
past this --libdir, so
On 20-06-2020 20:43, Xi Ruoyao wrote:
On 2020-06-20 20:10 +0200, Frans de Boer wrote:
Looking at the config.log, I see that libc_cv_slibdir is set to /lib.
However, libdir is automatically set to /lib64. I did specified in the
past this --libdir, so there was no problem - most likely because
On 20-06-2020 14:36, Pierre Labastie wrote:
On Sat, 2020-06-20 at 14:20 +0200, Frans de Boer wrote:
On 20-06-2020 13:12, Xi Ruoyao wrote:
On 2020-06-20 13:02 +0200, Frans de Boer wrote:
On 19-06-2020 22:33, Frans de Boer wrote:
On 19-06-2020 22:15, Pierre Labastie wrote:
On Fri, 2020-06-19
On 20-06-2020 13:12, Xi Ruoyao wrote:
On 2020-06-20 13:02 +0200, Frans de Boer wrote:
On 19-06-2020 22:33, Frans de Boer wrote:
On 19-06-2020 22:15, Pierre Labastie wrote:
On Fri, 2020-06-19 at 21:13 +0200, Frans de Boer wrote:
Dear all,
I follow every step but always stumble
On 19-06-2020 22:33, Frans de Boer wrote:
On 19-06-2020 22:15, Pierre Labastie wrote:
On Fri, 2020-06-19 at 21:13 +0200, Frans de Boer wrote:
Dear all,
I follow every step but always stumble on the '$LFS_TGT-gcc dummy.c'
-
in the first glibc.c section - in that crti.o can't be located by ld
On 19-06-2020 22:15, Pierre Labastie wrote:
On Fri, 2020-06-19 at 21:13 +0200, Frans de Boer wrote:
Dear all,
I follow every step but always stumble on the '$LFS_TGT-gcc dummy.c'
-
in the first glibc.c section - in that crti.o can't be located by ld.
Looking for crti.o, I find it residing
Dear all,
I follow every step but always stumble on the '$LFS_TGT-gcc dummy.c' -
in the first glibc.c section - in that crti.o can't be located by ld.
Looking for crti.o, I find it residing in the $LFS/usr/lib64 directory.
So, why can't ld find it?
--- Frans.
--
A: Yes, just like that
On 29-05-2020 22:39, Flareon Zulu wrote:
On Fri, May 29, 2020, 14:37 Frans de Boer <mailto:fr...@fransdb.nl>> wrote:
On 29-05-2020 21:09, Flareon Zulu wrote:
On Fri, May 29, 2020, 13:03 Frans de Boer mailto:fr...@fransdb.nl>> wrote:
On 29-05-2020 16:34,
On 29-05-2020 21:09, Flareon Zulu wrote:
On Fri, May 29, 2020, 13:03 Frans de Boer <mailto:fr...@fransdb.nl>> wrote:
On 29-05-2020 16:34, Xi Ruoyao wrote:
On 2020-05-29 16:20 +0200, Pierre Labastie wrote:
On Fri, 2020-05-29 at 15:45 +0200, Frans de Boer wrote:
On 29-05-2020 16:34, Xi Ruoyao wrote:
On 2020-05-29 16:20 +0200, Pierre Labastie wrote:
On Fri, 2020-05-29 at 15:45 +0200, Frans de Boer wrote:
On 29-05-2020 14:33, Pierre Labastie wrote:
On Fri, 2020-05-29 at 13:34 +0200, Frans de Boer wrote:
On 28-05-2020 15:08, Pierre Labastie wrote
On 29-05-2020 14:33, Pierre Labastie wrote:
On Fri, 2020-05-29 at 13:34 +0200, Frans de Boer wrote:
On 28-05-2020 15:08, Pierre Labastie wrote:
On Thu, 2020-05-28 at 14:16 +0200, Frans de Boer wrote:
LS,
Pierre has described a change "Add a symlink from
/tools/share/locale
to
/usr/
On 28-05-2020 15:08, Pierre Labastie wrote:
On Thu, 2020-05-28 at 14:16 +0200, Frans de Boer wrote:
LS,
Pierre has described a change "Add a symlink from /tools/share/locale
to
/usr/share/locale/locale-archive, ..."
The code refers to .../lib/locale and /usr/lib/locale is not crea
LS,
Pierre has described a change "Add a symlink from /tools/share/locale to
/usr/share/locale/locale-archive, ..."
The code refers to .../lib/locale and /usr/lib/locale is not created in 6.5.
Frans.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ:
On 19-03-19 10:19, Michael Shell wrote:
On Tue, 19 Mar 2019 09:15:25 +0100
thomas wrote:
Renaming /tools to another name will be appropriate to come over this
issue.
Perhaps a more functionally descriptive name would also help in other
ways. After all, the stuff in /tools is for a
On 9/28/18 5:50 PM, Bruce Dubbs wrote:
On 09/28/2018 02:16 AM, Pierre Labastie wrote:
On 9/28/18 6:48 AM, Bruce Dubbs wrote:
On 09/27/2018 05:07 PM, Ken Moffat wrote:
On Thu, Sep 27, 2018 at 10:37:09PM +0200, Frans de Boer wrote:
On 9/27/18 10:01 PM, Bruce Dubbs wrote:
Ken and Bruce,
I
On 9/28/18 9:16 AM, Pierre Labastie wrote:
On 9/28/18 6:48 AM, Bruce Dubbs wrote:
On 09/27/2018 05:07 PM, Ken Moffat wrote:
On Thu, Sep 27, 2018 at 10:37:09PM +0200, Frans de Boer wrote:
On 9/27/18 10:01 PM, Bruce Dubbs wrote:
Ken and Bruce,
I suspected it has to do something with entropy
On 9/27/18 10:01 PM, Bruce Dubbs wrote:
On 09/27/2018 02:21 PM, Frans de Boer wrote:
LS,
I have a problem which I don't seem to be able to solve without
further help.
Using the development version for LFS, I get stuck every time during
boot time. It happens either after the message
"
LS,
I have a problem which I don't seem to be able to solve without further
help.
Using the development version for LFS, I get stuck every time during
boot time. It happens either after the message
"Fast init done" or right thereafter - with a delay of aprox 12 seconds
- at the message
On 07/24/2018 01:01 AM, Ken Moffat wrote:
On Mon, Jul 23, 2018 at 05:20:41PM -0500, Douglas R. Reno wrote:
On Thu, Jul 19, 2018 at 8:47 AM Frans de Boer wrote:
This quite frustrating. After recompiling, following the book to the
letter, I still get a frozen LFS system.
One thing I do note
On 07/19/2018 09:34 PM, Michael Shell wrote:
On Thu, 19 Jul 2018 13:54:19 +0200
Frans de Boer wrote:
But I can't compile 4.13. anymore because I now have gcc 8.1 instead
of the former 7 series.
Frans,
What goes wrong when you try to build a 4.13 kernel with gcc 8.1?
It should work
On 06-07-18 16:44, Bruce Dubbs wrote:
On 07/06/2018 01:20 AM, Frans de Boer wrote:
On 07/05/2018 11:56 PM, Bruce Dubbs wrote:
On 07/05/2018 02:48 PM, Frans de Boer wrote:
On 06/30/2018 01:29 PM, Hazel Russman wrote:
On Fri, 29 Jun 2018 01:25:29 -0400
Michael Shell wrote:
On Thu, 28 Jun
On 19-07-18 14:57, Hazel Russman wrote:
On Thu, 19 Jul 2018 13:54:19 +0200
Frans de Boer wrote:
However a git bisection showed that this is actually a memory management issue.
The kernel commit that caused the problem is :
[33c2b803edd13487518a2c7d5002d84d7e9c878f] x86/mm: Remove
phys_to_virt
On 07/17/2018 03:15 PM, Hazel Russman wrote:
On Tue, 17 Jul 2018 14:06:09 +0200
Frans de Boer wrote:
On 07/14/2018 06:56 PM, Hazel Russman wrote:
Gentlemen,
I was given your contact details by Michael Shell, who has been helping me to
troubleshoot this problem via the Linux From Scratch
On 07/14/2018 06:56 PM, Hazel Russman wrote:
Gentlemen,
I was given your contact details by Michael Shell, who has been helping me to
troubleshoot this problem via the Linux From Scratch support list.
For some time now I have been unable to boot recent kernels (4.14 or later) on my rather
On 07/15/2018 11:26 PM, Armin K. wrote:
On 15.7.2018. 21:19, Frans de Boer wrote:
LS,
Below is a repeated piece of information, now being brought as a
separate issue from systemd.
I get the following error when i try to compile glibc in chapter 6:
...
bison --yacc --name-prefix=__gettext
On 07/15/2018 10:39 PM, Frans de Boer wrote:
On 07/15/2018 10:09 PM, Ken Moffat wrote:
On Sun, Jul 15, 2018 at 09:19:22PM +0200, Frans de Boer wrote:
LS,
Below is a repeated piece of information, now being brought as a
separate
issue from systemd.
I get the following error when i try
On 07/15/2018 10:09 PM, Ken Moffat wrote:
On Sun, Jul 15, 2018 at 09:19:22PM +0200, Frans de Boer wrote:
LS,
Below is a repeated piece of information, now being brought as a separate
issue from systemd.
I get the following error when i try to compile glibc in chapter 6:
...
bison --yacc
LS,
Below is a repeated piece of information, now being brought as a
separate issue from systemd.
I get the following error when i try to compile glibc in chapter 6:
...
bison --yacc --name-prefix=__gettext --output
/sources-lfs/glibc-2.27/glibc-build/intl/plural.c plural.y
bison: m4
On 07/14/2018 06:56 PM, Hazel Russman wrote:
Gentlemen,
I was given your contact details by Michael Shell, who has been helping me to
troubleshoot this problem via the Linux From Scratch support list.
For some time now I have been unable to boot recent kernels (4.14 or later) on my rather
On 13-07-18 16:24, Michael Shell wrote:
On Fri, 13 Jul 2018 09:35:24 -0400
Michael Shell wrote:
what exactly did gdb say about systemd's crash?
And FWIW, command output can be logged to a file as well as displayed
on the screen at the same time via the use of tee:
gdb /bin/program | tee
On 06-07-18 08:23, Frans de Boer wrote:
On 07/06/2018 05:32 AM, Michael Shell wrote:
On Thu, 5 Jul 2018 21:48:16 +0200
Frans de Boer wrote:
I had even rebuild everything with systemd-232, and that worked as
before. But after 232, things started to behave strange. Now way to
debug systemd
On 07/06/2018 05:32 AM, Michael Shell wrote:
On Thu, 5 Jul 2018 21:48:16 +0200
Frans de Boer wrote:
I had even rebuild everything with systemd-232, and that worked as
before. But after 232, things started to behave strange. Now way to
debug systemd, whatever I do
Frans,
That's
On 07/05/2018 11:56 PM, Bruce Dubbs wrote:
On 07/05/2018 02:48 PM, Frans de Boer wrote:
On 06/30/2018 01:29 PM, Hazel Russman wrote:
On Fri, 29 Jun 2018 01:25:29 -0400
Michael Shell wrote:
On Thu, 28 Jun 2018 16:06:00 +0800
Xi Ruoyao wrote:
Now I only use "initrd" directive to
On 06/30/2018 01:29 PM, Hazel Russman wrote:
On Fri, 29 Jun 2018 01:25:29 -0400
Michael Shell wrote:
On Thu, 28 Jun 2018 16:06:00 +0800
Xi Ruoyao wrote:
Now I only use "initrd" directive to update CPU microcode and fix the
buggy ACPI DSDT of my laptop (another sad story).
.
And
On 06/28/2018 09:54 PM, Thanos Baloukas wrote:
On 28/06/2018 10:44 μμ, Frans de Boer wrote:
On 06/28/2018 04:21 PM, Hazel Russman wrote:
On Thu, 28 Jun 2018 16:06:00 +0800
Xi Ruoyao wrote:
On 2018-06-28 01:08 -0400, Michael Shell wrote:
On Wed, 27 Jun 2018 14:42:47 -0700
Paul Rogers wrote
On 06/28/2018 04:21 PM, Hazel Russman wrote:
On Thu, 28 Jun 2018 16:06:00 +0800
Xi Ruoyao wrote:
On 2018-06-28 01:08 -0400, Michael Shell wrote:
On Wed, 27 Jun 2018 14:42:47 -0700
Paul Rogers wrote:
If that's true, even with systemd, why is there any need to build an
initramfs for a
On 06/26/2018 07:16 AM, Michael Shell wrote:
On Mon, 25 Jun 2018 09:19:35 +0200
Frans de Boer wrote:
I have a strong reason to believe that it is systemd, since up-to
version 237 all worked well, but with version 237 and 238 - and nothing
else changed - it does not boot anymore.
Frans
On 06/25/2018 03:51 AM, Michael Shell wrote:
On Sun, 24 Jun 2018 10:01:48 +0200
Frans de Boer wrote:
Same story, nothing happens.
I do notice, however, that on the listing by systemd capabilities the
text -ELFUTILS is used. I do compile the elfutils, but somehow systemd
does not use them
On 06/22/2018 07:30 AM, Michael Shell wrote:
On Thu, 21 Jun 2018 20:44:57 +0200
Frans de Boer wrote:
Alas, tried everything from the site including the init statement to no
avail. The shell does not start due to an unapropriate ioctl.
According to this:
https://www.raspberrypi.org/forums
On 18-06-18 06:53, Michael Shell wrote:
On Sun, 17 Jun 2018 11:22:23 +0200
Frans de Boer wrote:
Alas, keeping debugging symbols did not work. I still get the message
"no debug symbols found" and as a reaction to the bt command "no stack".
Frans,
You will have to
Can't reach the LFS site. There is no report, so I assume that the site
is down. How long will that last?
Regards,
Frans.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on
On 16-06-18 22:13, Frans de Boer wrote:
On 29-05-18 08:39, Frans de Boer wrote:
First of all I apologize for the initial flood of messages. They where
the result of multiple tries to get the message to the list in the
first place. Only yesterday I found that LFS is - still - not handling
TLS
On 29-05-18 08:39, Frans de Boer wrote:
First of all I apologize for the initial flood of messages. They where
the result of multiple tries to get the message to the list in the first
place. Only yesterday I found that LFS is - still - not handling TLS
while my server had the line that is must
2018 16:21:53 +0200
Frans de Boer wrote:
Attached is a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
Frans,
A few lines before the crash, your systemd errored with:
"failed to insert module 'autofs4': No such
Dear all,
Attached was a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
This is already like the introduction of systemd-238.
Regards, Frans.
Since pictures are not allowed:
The output ends with:
systemd[1]: Detected
Dear all,
Attached was a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
This is already like the introduction of systemd-238.
Regards, Frans.
Since pictures are not allowed:
The output ends with:
systemd[1]: Detected
Dear all,
Attached is a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
This is already like the introduction of systemd-238.
Regards, Frans.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ:
Dear all,
Attached was a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
This is already like the introduction of systemd-238.
Regards, Frans.
Since pictures are not allowed:
The output ends with:
systemd[1]: Detected
Dear all,
Attached was a picture with a repeatably failing boot when I build LFS
with systemd support. Any suggestion where I screwed-up?
This is already like the introduction of systemd-238.
Regards, Frans.
Since pictures are not allowed:
The output ends with:
systemd[1]: Detected
LS,
Now that the issue of the undocumented two dots in the meson command
line are clear, I encountered the next error:
Meson encountered an error in file src/resolve/meson.build, line 178,
column 10:
Expecting rbracket got eof.
tests += [
^^
Any suggestion?
Regards,
Frans.
--
LS,
I just had to downgrade my email security in order to be able to send
messages to the list. Just because the email server used for the list
does not support TLS. It's 2018, and no TLS support?
Hope that linuxfromscratch gets an security upgrade soon.
Regards,
Frans.
--
Chapter 6.53 contains the following instruction:
LANG=en_US.UTF-8 \
meson --prefix=/usr\
--sysconfdir=/etc\
--localstatedir=/var \
-Dblkid=true \
-Dbuildtype=release \
-Ddefault-dnssec=no
Chapter 6.53 contains the following instruction:
LANG=en_US.UTF-8 \
meson --prefix=/usr\
--sysconfdir=/etc\
--localstatedir=/var \
-Dblkid=true \
-Dbuildtype=release \
-Ddefault-dnssec=no
On 22-04-17 22:30, Ken Moffat wrote:
On Sat, Apr 22, 2017 at 09:49:25PM +0200, Frans de Boer wrote:
Ok, my mistake: lib64 contains some links, I found out how to eliminate the
use of lib64 at all.
From your next paragraph, you eliminated the use of lib.
The case of using lib64 instead
On 22-04-17 17:54, Bruce Dubbs wrote:
Frans de Boer wrote:
Dear Reader,
The current instance of LFS-dev still requires the use of /lib64 (as a
link to /lib).
No it does not. /lib64 is a directory, not a symlink. It contains
exactly two files, both symbolic links:
$ ls -l /lib64
total 0
On 16-02-17 23:18, Bruce Dubbs wrote:
Frans de Boer wrote:
Building flex-2.6.3 does not work because configure is not yet generated.
Running autogen.sh usually solves this, but there are no autotools
installed yet.
Any one else?
When I look at the tarball, configure is there.
md5sum
On 16-02-17 23:18, Bruce Dubbs wrote:
Frans de Boer wrote:
Building flex-2.6.3 does not work because configure is not yet generated.
Running autogen.sh usually solves this, but there are no autotools
installed yet.
Any one else?
When I look at the tarball, configure is there.
md5sum
Building flex-2.6.3 does not work because configure is not yet
generated. Running autogen.sh usually solves this, but there are no
autotools installed yet.
Any one else?
Regards, Frans.
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ:
On 29-12-16 07:59, Hazel Russman wrote:
On Wed, 28 Dec 2016 23:47:45 +0100
Frans de Boer <fr...@fransdb.nl> wrote:
I have said that I will forward some patches to get rid of the
[...]/lib64 notions after I have tested my older patches against the
newest sources.
I have created several
On 21-12-16 17:48, Bruce Dubbs wrote:
Frans de Boer wrote:
On 20-12-16 23:02, Bruce Dubbs wrote:
Frans de Boer wrote:
On 20-12-16 21:56, Bruce Dubbs wrote:
Frans de Boer wrote:
Hi all,
I just noticed that there are changes in the development version of
LFS,
related to x86_64 architecture
On 20-12-16 23:02, Bruce Dubbs wrote:
Frans de Boer wrote:
On 20-12-16 21:56, Bruce Dubbs wrote:
Frans de Boer wrote:
Hi all,
I just noticed that there are changes in the development version of
LFS,
related to x86_64 architecture. But i do miss the rationale and/or more
explanation
On 20-12-16 21:56, Bruce Dubbs wrote:
Frans de Boer wrote:
Hi all,
I just noticed that there are changes in the development version of LFS,
related to x86_64 architecture. But i do miss the rationale and/or more
explanation. The latter is important because I see several changes which
make
Hi all,
I just noticed that there are changes in the development version of LFS,
related to x86_64 architecture. But i do miss the rationale and/or more
explanation. The latter is important because I see several changes which
make sense, but misses other related changes in various other
On 07-12-16 09:07, Frans de Boer wrote:
On 06-12-16 23:21, Douglas R. Reno wrote:
Frans de Boer wrote:
While building systemd-232, I encounter the next errors during
installing:
mv: cannot stat '/usr/lib/libnss_myhostname.so.2': No such file or
directory
mv: cannot stat '/usr/lib
On 06-12-16 23:21, Douglas R. Reno wrote:
Frans de Boer wrote:
While building systemd-232, I encounter the next errors during
installing:
mv: cannot stat '/usr/lib/libnss_myhostname.so.2': No such file or
directory
mv: cannot stat '/usr/lib/libnss_mymachines.so.2': No such file or
directory
mv
1 - 100 of 130 matches
Mail list logo
