Le 23/02/2020 à 00:33, Tadeus Prastowo via lfs-dev a écrit :
> On Sat, Feb 22, 2020 at 11:10 PM Pierre Labastie via lfs-dev
> wrote:
>>
>> Le 22/02/2020 à 18:33, Tadeus Prastowo via lfs-dev a écrit :
>>> On Sat, Feb 22, 2020 at 6:17 PM Douglas R. Reno via lfs-dev
>
Le 22/02/2020 à 18:33, Tadeus Prastowo via lfs-dev a écrit :
> On Sat, Feb 22, 2020 at 6:17 PM Douglas R. Reno via lfs-dev
> wrote:
>>
>>
>> On 2/22/20 11:14 AM, Tadeus Prastowo via lfs-dev wrote:
>>> On Fri, Feb 21, 2020 at 9:54 PM Pierre Labastie via lfs-dev
>
Le 21/02/2020 à 21:50, Pierre Labastie via lfs-dev a écrit :
> Le 21/02/2020 à 18:15, Tadeus Prastowo a écrit :
>> Some corrections below, keeping in mind that the binutils build is a
>> native build, not a cross build.
>>
>> On Fri, Feb 21, 2020 at 6:05 PM Tadeus Pra
Le 21/02/2020 à 18:29, Tadeus Prastowo via lfs-dev a écrit :
> Hello,
>
> To quote
> http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-libstdc++.html:
>
> --disable-libstdcxx-threads
>
> Since we have not yet built the C threads library, the C++ one cannot
> be built either.
>
>> On Fri, Feb 21, 2020 at 11:01 AM Pierre Labastie via lfs-dev
>> wrote:
>>>
>>> Le 21/02/2020 à 05:33, Bruce Dubbs via lfs-dev a écrit :
>>>> On 2/20/20 10:09 PM, Xi Ruoyao via lfs-dev wrote:
>>>>> No. The linker (/usr/bin/ld) looks
Le 21/02/2020 à 05:33, Bruce Dubbs via lfs-dev a écrit :
> On 2/20/20 10:09 PM, Xi Ruoyao via lfs-dev wrote:
>> On 2020-02-20 22:05 -0600, Bruce Dubbs via lfs-dev wrote:
>>> On 2/20/20 6:57 PM, Xi Ruoyao via lfs-dev wrote:
On 2020-02-21 01:54 +0100, Tadeus Prastowo via lfs-dev wrote:
> Hel
Le 17/02/2020 à 17:14, Bruce Dubbs via lfs-dev a écrit :
> On 2/17/20 4:49 AM, Roger via lfs-dev wrote:
>> On Fri, 14 Feb 2020 14:27:23 -0600, Bruce Dubbs
>> wrote:
>>
>>> The Linux From Scratch community announces the release of LFS Version
>>> 9.1-rc1. It is a preliminary release of LFS-9.1.
>>>
Le 14/02/2020 à 14:05, Tadeus Prastowo via lfs-dev a écrit :
> Hi,
>
> I found that at
> http://www.linuxfromscratch.org/lfs/view/development/chapter05/perl.html,
> I needed to add `-Dnoextensions=Time/HiRes' because otherwise, the
> compilation failed with the following message due to the extensi
Le 09/02/2020 à 18:33, Pierre Labastie via lfs-dev a écrit :
> Le 09/02/2020 à 17:46, Bruce Dubbs via lfs-dev a écrit :
>> On 2/9/20 10:36 AM, Pierre Labastie via lfs-dev wrote:
>>> Le 09/02/2020 à 09:02, Kevin Buckley via lfs-dev a écrit :
>>>> I'll spare you
Le 09/02/2020 à 17:46, Bruce Dubbs via lfs-dev a écrit :
> On 2/9/20 10:36 AM, Pierre Labastie via lfs-dev wrote:
>> Le 09/02/2020 à 09:02, Kevin Buckley via lfs-dev a écrit :
>>> I'll spare you the details of how I cam to notice this but i was just
>>> applyin
Le 09/02/2020 à 09:02, Kevin Buckley via lfs-dev a écrit :
> I'll spare you the details of how I cam to notice this but i was just
> applying some local patches to the most recent trunk Rev 11745
> and realised that
>
> Chapter 5 still has these two XML files in the source directory
>
> gmp.xml
>
Le 04/02/2020 à 07:47, Walter P. Little via lfs-dev a écrit :
> Hi All -
>
> I recently volunteered to give a talk next month about LFS/BLFS to the San
> Fernando Valley Linux User Group (Los Angeles) that one of my employees
> organizes.
>
> The main purpose of my talk will be to inspire peop
Le 01/02/2020 à 07:44, Gavin Howard via lfs-dev a écrit :
> This may be self-serving as I am the author of the software in
> question, but I think that the Makefile generated by the configure.sh
> script of the bc package to be a good example. To get it, the user can
> run the first command in the
Le 13/01/2020 à 04:23, Bruce Dubbs via lfs-dev a écrit :
> On 1/12/20 8:31 PM, Douglas R. Reno via lfs-dev wrote:
>>
>> On 1/12/20 12:08 PM, Bruce Dubbs via lfs-dev wrote:
>>> I have added zstd to Chapter 6 of the book. It provides a new compression
>>> algorithm but is not yet used in LFS. I add
Le 08/01/2020 à 15:33, Saul Tigh via lfs-dev a écrit :
>
> On Wed, 8 Jan 2020 at 03:12 Pierre Labastie via lfs-dev
> <mailto:lfs-dev@lists.linuxfromscratch.org>> wrote:
>
>
> Actually, the static libraries libc.a and libpthread.a should be in
> /usr/lib.
&
Le 07/01/2020 à 13:02, Αγαθοκλής via lfs-dev a écrit :
> Hi Pierre,
>
> On Tue, Jan 07, at 09:19 Pierre Labastie via lfs-dev wrote:
>> Le 06/01/2020 à 23:54, Αγαθοκλής via lfs-dev a écrit :
>>> Hi Saul,
>>>
>>> On Tue, Jan 07, at 01:35
Le 07/01/2020 à 12:17, Saul Tigh via lfs-dev a écrit :
> You are right. Libc.a and libpthread.a are missing for some reason. One quick
> and dirty trick is to just copy them from /tools/lib to /lib and now I can
> compile libcap without problem but is this an ideal solution? Why libcap
> relies on
Le 06/01/2020 à 23:54, Αγαθοκλής via lfs-dev a écrit :
> Hi Saul,
>
> On Tue, Jan 07, at 01:35 Saul Tigh via lfs-dev wrote:
>> gcc -O2 -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Dlinux -Wall
>> -Wwrite-strings -Wpointer-arith -Wcast-qual -Wcast-align
>> -Wstrict-prototypes -Wmissing-prototypes
Le 06/01/2020 à 19:35, Saul Tigh via lfs-dev a écrit :
> Dear LFS dev,
> First time poster here so please be gentle. I've compiled LFS dev several
> times before but this time libcap (section 6.28) is giving me a headache. I'm
> following the latest version of LFS-systemd SVN-20200106 with ubuntu 1
Le 03/01/2020 à 22:07, Pierre Labastie via lfs-dev a écrit :
> Le 03/01/2020 à 17:16, Douglas R. Reno via lfs-dev a écrit :
>>
>> On 1/3/20 3:48 AM, Pierre Labastie via lfs-dev wrote:
>>> Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
>>>> On 1/2/20
Le 03/01/2020 à 17:16, Douglas R. Reno via lfs-dev a écrit :
>
> On 1/3/20 3:48 AM, Pierre Labastie via lfs-dev wrote:
>> Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
>>> On 1/2/20 3:26 PM, Pierre Labastie via lfs-dev wrote:
>>>> Hi,
>>>>
&
Le 03/01/2020 à 18:42, Joel Bion via lfs-dev a écrit :
> On 2020-01-03 07:40, Bruce Dubbs via lfs-dev wrote:
>> On 1/3/20 3:48 AM, Pierre Labastie via lfs-dev wrote:
>>> Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
>>>> On 1/2/20 3:26 PM, Pierre Labastie v
Le 02/01/2020 à 23:53, Bruce Dubbs via lfs-dev a écrit :
> On 1/2/20 3:26 PM, Pierre Labastie via lfs-dev wrote:
>> Hi,
>>
>> First, the variable for naming the static library has changed, and now there
>> are two of them: They can be removed with:
>> sed -i &
Hi,
First, the variable for naming the static library has changed, and now there
are two of them: They can be removed with:
sed -i '/install.*STA...LIBNAME/d' libcap/Makefile
Second, we use prefix=/usr for Make install, then move the shared library to
/lib. But actually, if we do not pass prefix,
Here is the error I get:
CCLD libmagic.la
/mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../../../x86_64-pc-li
nux-gnu/bin/ld: /mnt/lfs/tools/bin/../lib/gcc/x86_64-pc-linux-gnu/9.2.0/../../..
/../lib/libbz2.a(bzlib.o): relocation R_X86_64_32S against symbol
`BZ2_crc32Table' can no
Le 09/12/2019 à 00:43, Akira Urushibata via lfs-dev a écrit :
> Recently I installed Debian 10.2 on a computer with both LFS and older
> Debian versions. The installer automatically produced a new grub.cfg
> in which LFS is listed as "unknown Linux distribution." To my great
> surprise the listed
On 23/09/2019 18:56, Ken Moffat via lfs-dev wrote:
> On Mon, Sep 23, 2019 at 06:10:01PM +0200, Pierre Labastie via lfs-dev wrote:
>> On 23/09/2019 17:37, Xi Ruoyao via lfs-dev wrote:
>>> On 2019-09-23 10:30 -0500, Bruce Dubbs via lfs-dev wrote:
>>>> On 9/23/19 9:2
On 23/09/2019 17:37, Xi Ruoyao via lfs-dev wrote:
On 2019-09-23 10:30 -0500, Bruce Dubbs via lfs-dev wrote:
On 9/23/19 9:24 AM, John Burrell via lfs-dev wrote:
I haven't noticed this before but linux-5.3.1 uses rsync to transfer
the files in the command
make INSTALL_HDR_PATH=dest headers_insta
On 14/09/2019 18:34, Pierre Labastie via lfs-dev wrote:
> On 14/09/2019 18:28, Bruce Hill via lfs-dev wrote:
>> This link http://www.cotse.com/tools/wordlists.htm is no longer good, as
>> Cotse has rebuilt the site and it resolves to
>> https://www.identicloak.com/mailtools
On 14/09/2019 18:28, Bruce Hill via lfs-dev wrote:
> This link http://www.cotse.com/tools/wordlists.htm is no longer good, as
> Cotse has rebuilt the site and it resolves to
> https://www.identicloak.com/mailtools/wordlists.htm, which requires a login,
> if the list is even available anymore. I hav
On 03/09/2019 11:52, Kevin Buckley via lfs-dev wrote:
> On Tue, 3 Sep 2019 at 14:03, Bruce Dubbs via lfs-dev
> wrote:
>
>>> Couple of small "tidy-ups"
>>>
>>> On the download page of the website, there's the text
>>>
Other versions of the source may be similarly downloaded by changing the
>
On 28/08/2019 12:01, Xi Ruoyao via lfs-dev wrote:
> On 2019-08-28 11:39 +0200， Julien Lepiller via lfs-dev wrote:
>> Hi,
>>
>> In meson from chapter 6, I see: … via an environment variable,
>> NINJAJOBS. For example, setting …
>>
>> But that's not a command, is it? :)
>
> There is a comment sayin
On 16/08/2019 16:25, Riccardo Corsi via lfs-dev wrote:
> Hello, I have a question about GCC 9.2.0
> Is there a new option for ISL ?
> I have in my configure (build of LFS 9.0-rc1) of GCC:
>> ../configure --prefix=/usr \
>> --enable-languages=c,c++ \
>> --disable
On 02/07/2019 15:10, Wayne Blaszczyk via lfs-dev wrote:
> Hi All,
>
> Since yesterday, building the LFS book has been cause some issues for me.
> I've been using git rather than svn to keep up to date with the LFS
> repository.
> But recently I've been getting a 'update-index --refresh: command r
On 10/06/2019 08:28, Akira Urushibata via lfs-dev wrote:
> While constructing LFS v.8.4 I encountered a segmentation fault in
> Chapter 5 Section 35 "Stripping."
>
> I understand why this happened. I built up to Section 34, logged out
> and logged in as lfs again. PATH found the newly compiled a
;m taking in detail, I have a work-in-progress
> repo that contains a Docker container and scripts that perform all steps
> I'm taking here:
>
> https://gitlab.com/golddranks/lfs_docker
>
Please do not top post...
Pierre
>
>
> 2019年5月14日(火) 0:54 Bruce Dubbs via lfs-d
On 20/05/2019 14:42, emiliocabrera via lfs-dev wrote:
Hi. I´m at 5.5.1 Installation of Cross GCC, I´m building the LFS V8.4
on a VirtualBox machine with Debian x86_x64 installed. I get this error:
Configuring stage 2 in ./intl
You should be using lfs-support for this kind of question. If you
On 13/05/2019 15:50, Pyry Kontio via lfs-dev wrote:
Hi, and thanks for the wonderful book.
I'm trying to follow the standard LFS track, but I ran problems with
the GCC test suite in Chapter 6
(http://www.linuxfromscratch.org/lfs/view/stable/chapter06/gcc.html)
-- I get a massive amount of failed
On 12/05/2019 06:24, Ken Moffat via lfs-dev wrote:
> As people probably know, I usually set my own CFLAGS when building
> LFS (at a minimum, -O2 to get rid of most debug symbols). But I'm
> now trying to compare the build times and the size of the
> executables for "I did it my way" against using
On 10/05/2019 22:52, Bruce Dubbs via lfs-dev wrote:
> On 5/10/19 3:12 PM, Pierre Labastie via lfs-dev wrote:
>> On 10/05/2019 14:33, Douglas R. Reno via lfs-dev wrote:
>>>
>>> On 5/10/19 2:21 AM, Pierre Labastie via lfs-dev wrote:
>>>> Hi,
>>>>
&g
On 10/05/2019 14:33, Douglas R. Reno via lfs-dev wrote:
>
> On 5/10/19 2:21 AM, Pierre Labastie via lfs-dev wrote:
>> Hi,
>>
>> I now build the systemd book. I may come back to SysV later, but ATM, I want
>> to test the BLFS book, and the systemd revision has more
Hi,
I now build the systemd book. I may come back to SysV later, but ATM, I want
to test the BLFS book, and the systemd revision has more thorough coverage
than SysV.
Since i'm new to systemd, I try various commands. That's how I realized there
was a unit (man-db.timer) for running a daily update
On 09/05/2019 20:34, Ken Moffat via lfs-dev wrote:
> On Thu, May 09, 2019 at 09:32:48AM -0500, Bruce Dubbs via lfs-dev wrote:
>> On 5/9/19 1:11 AM, Ken Moffat via lfs-dev wrote:
>>> My fresh build (current svn) has just installed gcc in chroot and
>>> tried to check the SEARCH directories, where it
On 08/05/2019 19:05, spiky0011 via lfs-dev wrote:
> Hi
>
> I have just used the new jhalfs from git
>
> and have found that setting parallel make to 4 they are not being passed to
> the make in the scripts.
>
> gcc pass 1 setting via the menu it takes 25mins
>
> if I edit gcc pass1 script make
Le 26 avr. 2019 2:23 PM, William Harrington via lfs-dev a écrit :On 2019-04-23 19:10, Ken Moffat via lfs-dev wrote:
> In
> https://lore.kernel.org/lkml/CAHk-=wiv2glqkp6jfqyewl1uzgwnwek9fkwp3afzbcu2lv_...@mail.gmail.com/
> Linus Torvalds said:
>
> | I absolutely abhor even the concept of building
On 25/04/2019 11:54, Richard Melville via lfs-dev wrote:
On Thu, 25 Apr 2019 at 07:49, Pierre Labastie via lfs-dev
<mailto:lfs-dev@lists.linuxfromscratch.org>> wrote:
On 25/04/2019 00:34, Richard Melville via lfs-dev wrote:
> On Wed, 24 Apr 2019 at 18:19, Pierre Labastie
On 25/04/2019 00:34, Richard Melville via lfs-dev wrote:
> On Wed, 24 Apr 2019 at 18:19, Pierre Labastie via lfs-dev
> <mailto:lfs-dev@lists.linuxfromscratch.org>> wrote:
>
> I've again modified jhalfs, in order to get rid of the GPLv2 license.
> This li
I've again modified jhalfs, in order to get rid of the GPLv2 license.
This license prevents anybody to use anything that is in this project,
in projects with more permissive licenses. I've obtained the agreement
of the other contributors to jhalfs, except Manuel Canales Esparcia,
who is unreachabl
On 22/04/2019 05:55, Jeremy Huntwork via lfs-dev wrote:
> On Sun, Apr 21, 2019 at 8:37 PM Bruce Dubbs wrote:
>>
>>> I wasn't asking because of any personal preference. I just noticed
>>> that out of the box Ubuntu fails this test because /bin/sh is a
>>> symlink to /bin/dash, and I was wondering i
On 22/04/2019 02:28, Jeremy Huntwork via lfs-dev wrote:
> On Sun, Apr 21, 2019 at 8:17 PM Bruce Dubbs via lfs-dev
> wrote:
>>
>> On 4/21/19 7:04 PM, Jeremy Huntwork via lfs-dev wrote:
>>> Hi,
>>>
>>> What's the thinking behind the line in section 2.2 that requires
>>> /bin/sh to be a symlink or a
On 22/04/2019 05:55, Jeremy Huntwork via lfs-dev wrote:
> On Sun, Apr 21, 2019 at 8:37 PM Bruce Dubbs wrote:
>>
>>> I wasn't asking because of any personal preference. I just noticed
>>> that out of the box Ubuntu fails this test because /bin/sh is a
>>> symlink to /bin/dash, and I was wondering i
On 16/04/2019 04:18, Bruce Dubbs via lfs-dev wrote:
> On 4/15/19 9:03 PM, Douglas R. Reno via lfs-dev wrote:
>>
>> On 4/15/19 8:57 PM, Kevin Buckley via lfs-dev wrote:
>>> I am sure that there are reasons for not doing this but I've noticed,
>>> as a result of Xen no longer needing Python 2, that t
On 12/04/2019 20:24, Jeremy Huntwork via lfs-dev wrote:
> On Fri, Apr 12, 2019 at 2:13 PM Pierre Labastie via lfs-dev
> wrote:
>>
>> I'm certainly interested. You can make it as a patch set, I have a private
>> git
>> repo where I can run "git am"
On 12/04/2019 19:06, Jeremy Huntwork via lfs-dev wrote:
> On Fri, Apr 12, 2019 at 8:48 AM Pierre Labastie via lfs-dev
> wrote:
>>
>> It is certainly worth trying, but who will be able to find the time for
>> doing this? I'm working steadily towards a complete jhalf
On 12/04/2019 05:49, Jeremy Huntwork via lfs-dev wrote:
> Hi Folks,
>
> I'm just dropping a line to say I've released some actual documentation around
> a system I've been tinkering with for a long time: https://merelinux.org
>
> I thought some of you might find some ideas and features interestin
On 12/04/2019 12:37, DJ Lucas via lfs-dev wrote:
On March 28, 2019 7:00:29 PM CDT, Ken Moffat via lfs-dev
wrote:
It is disappointing that glibc links to static libgcc. What we
really need is a new generation of experimenters to replace Greg and
Ryan.
I like the sound of the "very clean met
Hi,
To address ticket http://wiki.linuxfromscratch.org/alfs/ticket/1713, I made
several changes to jhalfs:
- now it is the job of scriptlets to unpack the tarballs, and print disk usage.
- the Makefile therefore does less.
- some changes in pkgmngt/packageManager.xml.xxx (add sect1info sections, an
On 10/04/2019 12:30, thomas via lfs-dev wrote:
Am 2019-04-10 12:03, schrieb Pierre Labastie via lfs-dev:
On 10/04/2019 11:09, Julien Lepiller via lfs-dev wrote:
Hi!
I've helped a few lfs newcomers on the French IRC channel who all
made the same mistake: because there are two python arc
On 10/04/2019 11:09, Julien Lepiller via lfs-dev wrote:
Hi!
I've helped a few lfs newcomers on the French IRC channel who all made the same mistake:
because there are two python archives, they decompressed the wrong one and got stuck.
It's not hard to imagine them doing tar xf python. The tarb
Hi,
I'd like to know whether somebody around there uses the information in the
tags of LFS book, because I'd like to change that information
slightly. There are three tags inside the one:
- : this is where I'd like to make a change. Presently, the three
passes of gcc, and gcc-libstdc++, all have
Running configure as per the book, I get:
-
[...]
checking for swig... none
configure: Configuring python swig binding
checking for Python includes... -I/usr/include/python3.7m
checking for compiling Python extensions... gcc -pthread -fPIC
checking for linking Python extensions... gcc -pthread
Is there a reason why the instruction:
"install -vdm755 /usr/lib/pkgconfig"
is on the "6.6. Creating Essential Files and Symlinks" page,
and not in "6.5. Creating Directories"?
This lead to another question: should we use "install" or "mkdir -pv" in
"Creating Directories"? Actually, for pedagogica
On 05/04/2019 09:00, Xi Ruoyao via lfs-dev wrote:
> On 2019-04-04 16:43 -0500, Bruce Dubbs via lfs-dev wrote:
>> On 4/4/19 4:11 PM, Pierre Labastie via lfs-dev wrote:
>>> I've been testing several things for glibc in chapter 6 recently:
>>>
>>> - glibc
On 04/04/2019 23:43, Bruce Dubbs via lfs-dev wrote:
> On 4/4/19 4:11 PM, Pierre Labastie via lfs-dev wrote:
>> I've been testing several things for glibc in chapter 6 recently:
>>
>> - glibc-2.29 has introduced a hard dependency on Python 3. Previous versions
>> w
I've been testing several things for glibc in chapter 6 recently:
- glibc-2.29 has introduced a hard dependency on Python 3. Previous versions
were only dependent on perl. So I wondered whether perl was still a
dependency. It turns out that glibc can be built without perl, but that some
(24 exactl
On 04/04/2019 20:54, Bruce Dubbs via lfs-dev wrote:
> On 4/4/19 1:18 PM, Pierre Labastie via lfs-dev wrote:
>> On 03/04/2019 22:49, Pierre Labastie via lfs-dev wrote:
>>> On 02/04/2019 22:21, Pierre Labastie via lfs-dev wrote:
>>>> On 29/03/2019 11:16, Kevin Buckley v
On 03/04/2019 22:49, Pierre Labastie via lfs-dev wrote:
> On 02/04/2019 22:21, Pierre Labastie via lfs-dev wrote:
>> On 29/03/2019 11:16, Kevin Buckley via lfs-dev wrote:
>>> On Thu, 28 Mar 2019 at 14:35, James B via lfs-dev
>>> wrote:
>>>>
>>>
On 02/04/2019 22:21, Pierre Labastie via lfs-dev wrote:
> On 29/03/2019 11:16, Kevin Buckley via lfs-dev wrote:
>> On Thu, 28 Mar 2019 at 14:35, James B via lfs-dev
>> wrote:
>>>
>>> And then Python (which meson depends on) isn't exactly straightforward to
Hi,
I just found that bzip2 is now hosted on sourceware [1]. Should we still
host it on anduin?
Note: IIRC, the original site bzip.org got squatted, and bzip2 became
unavailable around the end of August last year. Now, both home and
downloads are on sourceware.
Pierre
[1] https://www.source
On 29/03/2019 11:16, Kevin Buckley via lfs-dev wrote:
> On Thu, 28 Mar 2019 at 14:35, James B via lfs-dev
> wrote:
>>
>> And then Python (which meson depends on) isn't exactly straightforward to
>> bootstrap,
>> and doubly so for multilib environments.
>
> Well, don't forget that someone in GLib
On 29/03/2019 11:09, Bruce Dubbs via lfs-dev wrote:
> On 3/29/19 4:42 AM, Pierre Labastie via lfs-dev wrote:
>> On 29/03/2019 08:37, Pierre Labastie via lfs-dev wrote:
>>> On 29/03/2019 00:19, Bruce Dubbs via lfs-dev wrote:
>>>> On 3/28/19 5:42 PM, Pierre Labastie via
On 29/03/2019 08:37, Pierre Labastie via lfs-dev wrote:
> On 29/03/2019 00:19, Bruce Dubbs via lfs-dev wrote:
>> On 3/28/19 5:42 PM, Pierre Labastie via lfs-dev wrote:
>>> On 28/03/2019 11:44, Pierre Labastie via lfs-dev wrote:
>>>> On 28/03/2019 10:42, thomas via l
On 29/03/2019 00:19, Bruce Dubbs via lfs-dev wrote:
> On 3/28/19 5:42 PM, Pierre Labastie via lfs-dev wrote:
>> On 28/03/2019 11:44, Pierre Labastie via lfs-dev wrote:
>>> On 28/03/2019 10:42, thomas via lfs-dev wrote:
>>>> Am 2019-03-28 09:57, schrieb Pierre Labast
On 28/03/2019 11:44, Pierre Labastie via lfs-dev wrote:
> On 28/03/2019 10:42, thomas via lfs-dev wrote:
>> Am 2019-03-28 09:57, schrieb Pierre Labastie via lfs-dev:
>>> On 27/03/2019 17:55, Pierre Labastie via lfs-dev wrote:
>>>> On 27/03/2019 16:43, Bruce Dubbs vi
On 28/03/2019 10:42, thomas via lfs-dev wrote:
Am 2019-03-28 09:57, schrieb Pierre Labastie via lfs-dev:
On 27/03/2019 17:55, Pierre Labastie via lfs-dev wrote:
On 27/03/2019 16:43, Bruce Dubbs via lfs-dev wrote:
On 3/26/19 11:51 PM, DJ Lucas via lfs-dev wrote:
For future reference, the
On 27/03/2019 17:55, Pierre Labastie via lfs-dev wrote:
> On 27/03/2019 16:43, Bruce Dubbs via lfs-dev wrote:
>> On 3/26/19 11:51 PM, DJ Lucas via lfs-dev wrote:
>>
>>> For future reference, the 'strings' utility might be better suited for this
>>> t
On 27/03/2019 16:43, Bruce Dubbs via lfs-dev wrote:
On 3/26/19 11:51 PM, DJ Lucas via lfs-dev wrote:
For future reference, the 'strings' utility might be better suited
for this task, rather than opening a binary in a text editor.
$ strings /lib/libc.so.6 | grep "tools"
Good idea.
$ strings
On 25/03/2019 19:11, Bruce Dubbs via lfs-dev wrote:
> On 3/25/19 12:12 PM, Pierre Labastie via lfs-dev wrote:
>> On 25/03/2019 16:05, Bruce Dubbs via lfs-dev wrote:
>>> On 3/25/19 8:12 AM, Pierre Labastie via lfs-dev wrote:
>>>> On 25/03/2019 10:34, Xi Ruoyao via lfs-
On 25/03/2019 16:05, Bruce Dubbs via lfs-dev wrote:
On 3/25/19 8:12 AM, Pierre Labastie via lfs-dev wrote:
On 25/03/2019 10:34, Xi Ruoyao via lfs-dev wrote:
On 2019-03-24 12:49 -0500, Bruce Dubbs via lfs-dev wrote:
On 3/24/19 12:20 PM, Xi Ruoyao via lfs-dev wrote:
In r11250 DJ introduced
On 25/03/2019 10:34, Xi Ruoyao via lfs-dev wrote:
On 2019-03-24 12:49 -0500, Bruce Dubbs via lfs-dev wrote:
On 3/24/19 12:20 PM, Xi Ruoyao via lfs-dev wrote:
In r11250 DJ introduced several symlinks and GCC -isystem options for Glibc
so
it will use the final system location of system headers.
On 14/03/2019 14:37, Mark Wigzell via lfs-dev wrote:
Hi, this is very minor point but the discussion on /usr/local debate
says "All of the BLFS instructions install programs in /usr with
optional instructions to install into /opt for some specific packages"
However, the libxcb-util-wm package is
On 14/03/2019 14:06, Mark Wigzell via lfs-dev wrote:
xkbvleds is missing from the md5sum file that is generated by manually
from the doc page. However the applications listed include xkbvleds.
When I built them, that app wasn't created so I'm thinking the list is
not up to date in the doc.
Th
On 14/03/2019 11:47, Julien Lepiller via lfs-dev wrote:
Hi, I found a few typos while translating:
In python, the description of pip3 says "pacakges"
In systemd, the description of resolvconf has a parenthesis.
Thanks!
Fixed at revision 11559. Thanks to you!
Pierre
--
http://lists.linuxfrom
On 11/03/2019 10:25, Pierre Labastie via lfs-dev wrote:
> On 09/03/2019 09:50, Pierre Labastie via lfs-dev wrote:
>> [...]
>> - copy host's /etc/resolve.conf to /run/systemd/resolve for systemd
>
> This part is buggy: it is only done when running "make -C /mnt/lfs/
On 11/03/2019 16:17, Bruce Dubbs via lfs-dev wrote:
On 3/11/19 9:18 AM, Pierre Labastie via lfs-dev wrote:
Hi,
In Gcc-7, a new compile time option has been introduced:
--with-gcc-major-version-only
with the effect of having only the major version in directory names.
But it has also the effect
Hi,
In Gcc-7, a new compile time option has been introduced:
--with-gcc-major-version-only
with the effect of having only the major version in directory names.
But it has also the effect that "gcc -dumpversion" only shows
the major version. For example, on Debian unstable:
$ gcc -dumpversion
On 09/03/2019 09:50, Pierre Labastie via lfs-dev wrote:
> [...]
> - copy host's /etc/resolve.conf to /run/systemd/resolve for systemd
This part is buggy: it is only done when running "make -C /mnt/lfs/jhalfs
devices", but not when entering chapter06. So blfs-tools still can
On 09/03/2019 23:29, Bruce Dubbs via lfs-dev wrote:
> On 3/9/19 3:47 PM, Pierre Labastie via lfs-dev wrote:
>> On 09/03/2019 21:24, Bruce Dubbs via lfs-dev wrote:
>>> On 3/9/19 12:57 PM, DJ Lucas via lfs-dev wrote:
>>>> On 3/9/2019 10:38 AM, Pierre Labastie via lfs-
On 09/03/2019 21:24, Bruce Dubbs via lfs-dev wrote:
> On 3/9/19 12:57 PM, DJ Lucas via lfs-dev wrote:
>> On 3/9/2019 10:38 AM, Pierre Labastie via lfs-dev wrote:
>>> On 09/03/2019 17:09, DJ Lucas via lfs-dev wrote:
>>>> This reminds me, I'm getting /etc/sysco
Hi, Thanks for feedback,
On 09/03/2019 17:09, DJ Lucas via lfs-dev wrote:
> On 3/9/2019 2:50 AM, Pierre Labastie via lfs-dev wrote:
>> [...]
>> Note that a new variable LOG_LEVEL is introduced in
>> System configuration-->Console configuration, and is added to the
>&g
Sent to lfs-dev, since I am not sure everybody using jhalfs
monitors alfs-discuss. I've made several updates to jhalfs lately:
- generate an /etc/adjtime file for systemd. This involves a new variable
named LOCAL, which is set in System configuration-->Console configuration.
LOCAL is taken into ac
On 28/02/2019 20:46, Daniel Schepler via lfs-dev wrote:
> On Thu, Feb 28, 2019 at 10:09 AM DJ Lucas (LFS) via lfs-dev
> wrote:
>> I'd like to just go ahead and add it to the book then. No guarantee that
>> previous host was systemd. Something to the effect of the following would be
>> appropriat
On 28/02/2019 19:08, DJ Lucas (LFS) via lfs-dev wrote:
> On February 28, 2019 2:22:46 AM CST, Pierre Labastie via lfs-dev
> wrote:
>
>>
>> To Bruce, Doug and DJ: I may take an intermediate approach: add the two
>> lines
>> above only to jhalfs (in Makefile, un
On 28/02/2019 01:33, DJ Lucas (LFS) via lfs-dev wrote:
> On February 27, 2019 3:27:02 PM CST, Pierre Labastie via lfs-dev
> wrote:
>> On 27/02/2019 18:05, Bruce Dubbs via lfs-dev wrote:
>>> On 2/27/19 10:45 AM, Pierre Labastie via lfs-dev wrote:
>>>> On 27/02/20
On 27/02/2019 18:05, Bruce Dubbs via lfs-dev wrote:
> On 2/27/19 10:45 AM, Pierre Labastie via lfs-dev wrote:
>> On 27/02/2019 04:47, Bruce Dubbs via lfs-dev wrote:
>>> We now have all tickets for 8.4 closed and all packages tagged.
>>>
>>> Please review what is
On 27/02/2019 04:47, Bruce Dubbs via lfs-dev wrote:
> We now have all tickets for 8.4 closed and all packages tagged.
>
> Please review what is in the development books and let us know if there are
> any changes that need to be made. Small issues are as important at this stage
> as big ones.
>
On 22/02/2019 09:26, Pierre Labastie via lfs-dev wrote:
> On 22/02/2019 02:25, Ken Moffat via lfs-dev wrote:
>> Summary - another 22 tests were run, and passed. I think this is
>> worth adding to the minimal locales:
>>
>> localedef -c -i ja_JP -f UTF-8 ja_JP.UTF-8
&g
On 22/02/2019 02:25, Ken Moffat via lfs-dev wrote:
> On Fri, Feb 15, 2019 at 09:06:34PM +, Ken Moffat via lfs-dev wrote:
>>
>> · gawk had no failures, but reported
>>
>> %% Inadequate locale support: skipping charset tests.
>> %% At least en_US.UTF-8, fr_FR.UTF-8, ru_RU.UTF-8 an
On 2/16/19 6:19 PM, Bruce Dubbs via lfs-dev wrote:
On 2/16/19 9:08 AM, Thomas Trepl via blfs-support wrote:
Am Samstag, den 16.02.2019, 15:18 +0100 schrieb Gerhard Gedigk via
blfs-support:
Hello,
please correct the example for the German console fonts. (7.6.5)
KEYMAP="de-latin1" # is corre
On 16/02/2019 08:55, Brandon Murry via lfs-dev wrote:
> Thanks for everyone's help getting through some of the problems I encountered.
> Finally got LFS complete and booted and thought I could share a few things
> extra issues I came across using git repositories for GCC and the Linux
> kernel.
>
101 - 200 of 224 matches
Mail list logo
