Right now there are a few of tickets outstanding with regard to updated
packages
or patches to packages that we need to address before a package freeze. We
need
to either agree to update or reset the target milestone to either 7.0 or future.
2226Vim mandir patch ( really just an optimizat
Bruce Dubbs wrote:
> Right now there are a few of tickets outstanding with regard to updated
> packages
> or patches to packages that we need to address before a package freeze. We
> need
> to either agree to update or reset the target milestone to either 7.0 or
> future.
>
> 2226 Vim mandir
DJ Lucas wrote:
> Bruce Dubbs wrote:
>> Right now there are a few of tickets outstanding with regard to updated
>> packages
>> or patches to packages that we need to address before a package freeze. We
>> need
>> to either agree to update or reset the target milestone to either 7.0 or
>> futu
[EMAIL PROTECTED] wrote:
> Author: randy
> Date: 2008-10-12 09:09:40 -0600 (Sun, 12 Oct 2008)
> New Revision: 8649
>
> Modified:
>trunk/BOOK/appendices/dependencies.xml
>trunk/BOOK/chapter01/changelog.xml
>trunk/BOOK/chapter05/chapter05.xml
> Log:
> Moved the Chapter 5 M4 installation
Jeremy Huntwork wrote:
> Whichever way I look at it, it feels dirty. :/
Just as a followup, what I would suggest is:
* move m4 to a location similar to other packages in chapter 5 so that
it is linked against our temporary libs in /tools and will work
independently with /tools. (Let's not forge
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Bruce Dubbs wrote:
> Right now there are a few of tickets outstanding with regard to updated
> packages
> or patches to packages that we need to address before a package freeze. We
> need
> to either agree to update or reset the target milest
I didn't bump into this problem until installing arts-1.5.9 from BLFS
6.3. Making m4 part of the temporarily toolchain and installing it
after autoconf makes a tool of autoconf called autom4te link to the m4
in /tools instead of a m4 that would be part of a finished system.
Also bison does the same
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Rick Houkes wrote:
> Making m4 part of the temporarily toolchain and installing it after
> autoconf makes a tool of autoconf called autom4te link to the m4 in
> /tools instead of a m4 that would be part of a finished system.
Um, m4 doesn't provid
Bruce Dubbs wrote:
> Right now there are a few of tickets outstanding with regard to updated
> packages
> or patches to packages that we need to address before a package freeze. We
> need
> to either agree to update or reset the target milestone to either 7.0 or
> future.
>
> 2226 Vim mandir
Bryan Kadzban wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
> Rick Houkes wrote:
>> Making m4 part of the temporarily toolchain and installing it after
>> autoconf makes a tool of autoconf called autom4te link to the m4 in
>> /tools instead of a m4 that would be part of a finishe
Chris Staub wrote:
> Another problem (not really related to this, but it does also involve
> m4) is that, as the book is now, m4 in /tools is not linked to /tools.
> Either m4 needs to be built again in /tools sometime after the toolchain
> adjustment, or the host system's m4 can be used for GCC
Jeremy Huntwork wrote:
> Chris Staub wrote:
>> Another problem (not really related to this, but it does also involve
>> m4) is that, as the book is now, m4 in /tools is not linked to /tools.
>> Either m4 needs to be built again in /tools sometime after the toolchain
>> adjustment, or the host sys
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jeremy Huntwork wrote:
> So, to sum up, we have two problems:
>
> 1. m4 in chapter five doesn't link against /tools
> 2. m4 in chapter six is built to late to avoid hard-coded paths to
> /tools/bin/m4 showing up in autotools scripts.
>
> I pers
Bryan Kadzban wrote:
>
>
> I'd prefer to get rid of it. It wasn't there at all (since 2007 or so)
> until gcc's extra bits added it as a requirement...
You mean, don't put m4 in /tools at all, and just build it right before
GMP in Chapter 6? Sounds like that could work...
--
http://linuxfroms
Bryan Kadzban wrote:
> I'd prefer to get rid of it. It wasn't there at all (since 2007 or so)
> until gcc's extra bits added it as a requirement...
I'd tend to agree, but, if it's not built at all in chapter 5, what do
you do in chapter 6 for final gcc?
--
JH
--
http://linuxfromscratch.org/ma
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
OK, some useful info this time (instead of a state dump...):
DJ Lucas wrote:
> Bruce Dubbs wrote:
>> Right now there are a few of tickets outstanding with regard to updated
>> packages
>> or patches to packages that we need to address before a
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Jeremy Huntwork wrote:
> Bryan Kadzban wrote:
>
>> I'd prefer to get rid of it. It wasn't there at all (since 2007 or
>> so) until gcc's extra bits added it as a requirement...
>
> I'd tend to agree, but, if it's not built at all in chapter 5,
Chris Staub wrote:
> Bryan Kadzban wrote:
>>
>> I'd prefer to get rid of it. It wasn't there at all (since 2007 or so)
>> until gcc's extra bits added it as a requirement...
>
> You mean, don't put m4 in /tools at all, and just build it right before
> GMP in Chapter 6? Sounds like that could wor
Jeremy Huntwork wrote:
> Chris Staub wrote:
>> Another problem (not really related to this, but it does also involve
>> m4) is that, as the book is now, m4 in /tools is not linked to /tools.
>> Either m4 needs to be built again in /tools sometime after the toolchain
>> adjustment, or the host sys
Bruce Dubbs wrote:
> The oldest version on ftp.gnu.org is 1.4.1 dated June 2004.
The m4 on my RH 6.2 box says it's 1.4 and it seems to do fine.
--
JH
--
http://linuxfromscratch.org/mailman/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
On Saturday October 18 2008 10:10:57 pm Bryan Kadzban wrote:
> >> 2247 Texinfo 4.13a ( repackage due to maintainer error )
>
> I just pulled down texinfo-4.13a.tar.gz and texinfo-4.13.tar.gz -- and
> their md5sums are *identical*. Extracting each into its own directory
> also shows no differ
Bruce Dubbs wrote:
> BTW, there was a new version released 11 Oct 2008 - 1.4.12.
>
> It builds with configure && make && make check && make install.
> Three tests were skipped:
>
> cannot tell stack overflow from crash; consider installing libsigsegv
> SKIP: test-c-stack2.sh
> Skipping test: mul
On Saturday October 18 2008 10:54:01 pm Robert Connolly wrote:
> On Saturday October 18 2008 10:10:57 pm Bryan Kadzban wrote:
> > >> 2247 Texinfo 4.13a ( repackage due to maintainer error )
> >
> > I just pulled down texinfo-4.13a.tar.gz and texinfo-4.13.tar.gz -- and
> > their md5sums are *ide
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Robert Connolly wrote:
> On Saturday October 18 2008 10:10:57 pm Bryan Kadzban wrote:
2247 Texinfo 4.13a ( repackage due to maintainer error )
>> I just pulled down texinfo-4.13a.tar.gz and texinfo-4.13.tar.gz --
>> and their md5sums ar
24 matches
Mail list logo
