Archaic wrote:
In an attempt to get this info both archived, and presented to the
larger community, I am writing up a synopsis of ideas that have been
floating around on IRC as to how to handle the chroot/reboot phase of
the cross-lfs book. I will list them and give a brief pro/con for each
as I un
On Sat, May 14, 2005 at 02:31:22AM +0200, M.Canales.es wrote:
>
> If the target host (remote or local) is a machine running linux, wy not to do
> the full construction from the begin directly at the target machine? In that
> case HOST=TARGET due that both are the target machine.
That is what I
El Sábado, 14 de Mayo de 2005 01:42, Archaic escribió:
> Ideas? Comments? Suggestion? We need your input. Multiple perspectives
> ultimately make for a better book. The above is merely my perspective
> and likely does not cover all aspects needed to make a good decision.
There is some aspects tha
On Sat, May 14, 2005 at 01:13:31AM +0200, M.Canales.es wrote:
>
> Revising the webcvs I noticed that the historial is already loss in the
> cross-lfs branch due the big changes in the book structure.
That can be folded back in. For instance, every file that is in the same
location within the boo
In an attempt to get this info both archived, and presented to the
larger community, I am writing up a synopsis of ideas that have been
floating around on IRC as to how to handle the chroot/reboot phase of
the cross-lfs book. I will list them and give a brief pro/con for each
as I understand it.
1
El Sábado, 14 de Mayo de 2005 00:16, Archaic escribió:
> As we discussed on IRC, it can still be done without any historical
> loss, but it will require a lot of manual fiddling. However, as this is
> a one time thing, I think we'd be shooting ourselves in the foot
> researching a way to automate
On Fri, May 13, 2005 at 10:18:49AM -0400, Jeremy Huntwork wrote:
>
> But does this obscure information from the reader?
Not if properly explained in the beginning. Note that --prefix=/usr
isn't explained everytime, so the value of host, target, flags, whatever
needn't be explained everytime. And
On Fri, May 13, 2005 at 02:46:09PM +0600, Alexander E. Patrakov wrote:
>
> 2) Pass --disable-nls to binutils in Chapter 5 in order to avoid
> dependency on gettext.
Yes this has allowed me to build testing with testing with testing (3
layers deep) with no problems. I use --disable-nls on every p
On Thu, May 12, 2005 at 03:24:46PM -0700, Jim Gifford wrote:
>
> Tried that via svk, bombed everytime. I talked to the on
> irc.freenode.net #svn, they said if the structure was the same it
> wouldn't be an issue, but we made a lot of changes to lfs to multi-arch
> and multi-arch to cross-lfs.
On Fri, 13 May 2005, Jim Gifford wrote:
> Ken that's one of the things we are going to do after we get the builds
> working is go through every page and add more text or less text to give
> the reader a better understanding. We would welcome your input on this.
>
I'll be happy to contribute, but
Ken that's one of the things we are going to do after we get the builds
working is go through every page and add more text or less text to give
the reader a better understanding. We would welcome your input on this.
--
--
[EMAIL PROTECTED]
[EMAIL PROTECTED]
LFS User # 2577
Registered Linux U
On Fri, 13 May 2005, Jeremy Huntwork wrote:
> Ken Moffat wrote:
> > In my opinion, put it all in variables - the sparc page has '-m32'
> > exposed to the reader without an explanation (although it might be
> > explained on another page). Put it all in variables, and explain them
> > at the begin
On Fri, 13 May 2005, Matthew Burgess wrote:
>
> We'll be breaking the unwritten 'rule' of not bumping version numbers on
> packages during our 'slushy' RCish period, due to security issues in the
> kernel (which will be bumped to 2.6.11.9) and a bug in the bootscripts
> which caused network interf
I've been working on the integration of the BLFS patches into the
patches project. Right now I've created a script (below) that can run
on belgarath and identify patches in blfs and not in the patches project
download directory.
There are a couple of approaches I can take and one problem.
First
Ken Moffat wrote:
I see testing is moving on - did the 6.1 release get pulled ?
Nope, not pulled, just delayed whilst things went slightly manic at work
and at home. I think things are settling down now, so managed to get a
bit of work done catching up on the outstanding 6.1 items last night.
Ken Moffat wrote:
On Fri, 13 May 2005, Jeremy Huntwork wrote:
One nit-pick: you are using LFS_TARGET and LFS_HOST, why not just
TARGET and HOST ?
This one was done by me, there was a report of a distro having TARGET
and HOST set, I know we could just
override these variables. But I decided t
Ken Moffat wrote:
In my opinion, put it all in variables - the sparc page has '-m32'
exposed to the reader without an explanation (although it might be
explained on another page). Put it all in variables, and explain them
at the beginning, then just use them.
The explanatory text for the cross-lf
On Fri, 13 May 2005, Jeremy Huntwork wrote:
>
> Notice the use of $(BUILD32) in the x86_64 book that would contain (at
> least) the -m32 tag appended to the CC variable. It was thought that if
> we could have the user define the gcc tags needed to build for 32 or 64
> in the book for each arch, we
Hi all,
I wanted to hear your opinions about how we present commands in the
cross-lfs book. When we first started writing the book, we decided it
would be easier to use variables for the target triplets to be used
throughout the cross-tools and temp-system section.
Something like this:
LFS_HOST
I see testing is moving on - did the 6.1 release get pulled ?
Ken
--
das eine Mal als Tragödie, das andere Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Lets file a bug for now, I wanted to leave the lfs-bootscript tree
alone until the next LFS release.
--
Nathan Coulson (conathan)
--
nathan at linuxfromscratch org
conathan at gmail com
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscri
Glibc page in Chapter 5 contains the following paragraph:
During this stage the following warning might appear:
configure: WARNING:
*** These auxiliary programs are missing or
*** incompatible versions: msgfmt
*** some features will be disabled.
*** Check the INSTALL file for required versions.
22 matches
Mail list logo
