Am Donnerstag, den 02.05.2019, 21:23 +0100 schrieb Ken Moffat via lfs-
dev:
> On Thu, May 02, 2019 at 09:39:44PM +0200, Thomas Trepl via lfs-dev wrote:
> > Regarding pkgmngt, i started a project for my own to see how
> > pkgmngt may work. There is no heavy development on
> > https://www.belfs.org
On Thu, May 02, 2019 at 09:39:44PM +0200, Thomas Trepl via lfs-dev wrote:
>
> Regarding pkgmngt, i started a project for my own to see how
> pkgmngt may work. There is no heavy development on
> https://www.belfs.org since its a one-man- and spare-time show but it
> works for me so far and a new
Am Freitag, den 03.05.2019, 01:58 +1000 schrieb James B via lfs-dev:
> Hi guys,
>
> I've been lurking in this mailing list for quite a while now and seen some
> developments going on.
>
> Specifically, I have seen Thomas' multilib work being discussed and I think
> Thomas recently put his work
On 2019-05-02 12:48 -0500, Bruce Dubbs via lfs-dev wrote:
> On 5/2/19 12:15 PM, Xi Ruoyao via lfs-dev wrote:
> > The test suite log says:
> >
> > *** Obsolete types detected:
> > /usr/include/linux/sysctl.h:KERN_PANIC_PRINT=78, /* ulong: bitmask to
> > print
> > system info on panic */
> >
>
On 5/2/19 12:15 PM, Xi Ruoyao via lfs-dev wrote:
The test suite log says:
*** Obsolete types detected:
/usr/include/linux/sysctl.h:KERN_PANIC_PRINT=78, /* ulong: bitmask to print
system info on panic */
So this test failure seems because of changes in Linux API headers.
Should we note
The test suite log says:
*** Obsolete types detected:
/usr/include/linux/sysctl.h:KERN_PANIC_PRINT=78, /* ulong: bitmask to print
system info on panic */
So this test failure seems because of changes in Linux API headers.
Should we note this in the book?
--
Xi Ruoyao
School of Aerospace
Hi guys,
I've been lurking in this mailing list for quite a while now and seen some
developments going on.
Specifically, I have seen Thomas' multilib work being discussed and I think
Thomas recently put his work into somewhere in LFS website. I've also seen
comments about "LFS with package
