On 2020-06-21 13:24 +0800, Xi Ruoyao via lfs-dev wrote:
> On 2020-06-20 21:24 -0500, Bruce Dubbs via lfs-dev wrote:
> > On 6/20/20 8:30 PM, Bruce Dubbs wrote:
> > > On 6/20/20 7:07 PM, Xi Ruoyao via lfs-dev wrote:
> > > > On 2020-06-20 16:58 -0500, Bruce Dubbs via lfs-dev wrote:
> > > > > On
On 2020-06-20 21:24 -0500, Bruce Dubbs via lfs-dev wrote:
> On 6/20/20 8:30 PM, Bruce Dubbs wrote:
> > On 6/20/20 7:07 PM, Xi Ruoyao via lfs-dev wrote:
> > > On 2020-06-20 16:58 -0500, Bruce Dubbs via lfs-dev wrote:
> > > > On 6/20/20 2:42 PM, Xi Ruoyao via lfs-dev wrote:
> > > > > The discussion
On 6/20/20 8:30 PM, Bruce Dubbs wrote:
On 6/20/20 7:07 PM, Xi Ruoyao via lfs-dev wrote:
On 2020-06-20 16:58 -0500, Bruce Dubbs via lfs-dev wrote:
On 6/20/20 2:42 PM, Xi Ruoyao via lfs-dev wrote:
The discussion with Frans de Boer in lfs-support shown that the
environment
variables from host
On 6/20/20 7:07 PM, Xi Ruoyao via lfs-dev wrote:
On 2020-06-20 16:58 -0500, Bruce Dubbs via lfs-dev wrote:
On 6/20/20 2:42 PM, Xi Ruoyao via lfs-dev wrote:
The discussion with Frans de Boer in lfs-support shown that the environment
variables from host can catch us completely off guard. Though
On 2020-06-20 16:58 -0500, Bruce Dubbs via lfs-dev wrote:
> On 6/20/20 2:42 PM, Xi Ruoyao via lfs-dev wrote:
> > The discussion with Frans de Boer in lfs-support shown that the environment
> > variables from host can catch us completely off guard. Though in his case
> > the
> > problem is that he
On 6/20/20 2:42 PM, Xi Ruoyao via lfs-dev wrote:
The discussion with Frans de Boer in lfs-support shown that the environment
variables from host can catch us completely off guard. Though in his case the
problem is that he forgot to create /home/lfs/.bash_profile, normally
/etc/bash.bashrc would
The discussion with Frans de Boer in lfs-support shown that the environment
variables from host can catch us completely off guard. Though in his case the
problem is that he forgot to create /home/lfs/.bash_profile, normally
/etc/bash.bashrc would be more dangerous (the book has no consideration
On Sat, Jun 20, 2020 at 07:05:24AM -0700, Joel Bion via lfs-dev wrote:
> Upgrading Perl was the trigger for me building my own package dependency
> tracker utility. With tons of manual configuration, I am able to upgrade any
> subset of packages at one time. It tells me what I need to rebuild,
Upgrading Perl was the trigger for me building my own package dependency
tracker utility. With tons of manual configuration, I am able to upgrade any
subset of packages at one time. It tells me what I need to rebuild, in what
order. Some packages trigger no or few rebuilds. Others, like
On Sat, Jun 20, 2020 at 02:42:03PM +0200, Thomas Trepl via lfs-dev wrote:
> Hi all,
>
> this is about hte configuration options of perl.
>
> Problem:
> whenever perl is upgraded to a newer version (for example 5.30.2 to
> 5.30.3), all perl modules needs to be reinstalled as the current
>
Hi all,
this is about hte configuration options of perl.
Problem:
whenever perl is upgraded to a newer version (for example 5.30.2 to
5.30.3), all perl modules needs to be reinstalled as the current
configuration of perl forces a directory structure like
/usr
/lib
/perl5
/5.30.2
There was a paragraph in sect. 7.4 "Entering the Chroot Environment", reading:
> Notice that /tools/bin is not
> in the PATH. This means that a temporary tool will no longer be
> used once its final version is installed.
It does not make sense now as the final version will overwrite the
12 matches
Mail list logo
