blfs-support Digest, Vol 1970, Issue 1

Dale Stein dstein2000 at gmail.com
Thu Feb 18 23:49:45 PST 2010


ok thanks,  I will be waiting for the update.  No hurry mind you!
I just love what you guys are doing and have always read the posts with
interest.

There are a few - more errors cropping up which I might expand on.

1) expect-5.43.0 suffers a fatal error.

2) Audacious-1.5.1 plugins have compiler error arch_raw.cxx: In constructor
'arch_Raw::arch_Raw(const std::string&)':

3) Avifile-0.7.45 Error aviplay.cpp:245: error: invalid conversion from
'const char*' to 'char*'

4) MPlayer-1.0rc1 Error!
vo_ivtv.c: In function 'ivtv_reset':
vo_ivtv.c:79: error: storage size of 'sd' isn't known
vo_ivtv.c:80: error: storage size of 'sd1' isn't known
vo_ivtv.c:85: error: 'IVTV_IOC_STOP_DECODE' undeclared (first use in this
function)
vo_ivtv.c:85: error: (Each undeclared identifier is reported only once
vo_ivtv.c:85: error: for each function it appears in.)
vo_ivtv.c:95: error: 'IVTV_IOC_START_DECODE' undeclared (first use in this
function)
make[1]: *** [vo_ivtv.o] Error 1
make[1]: Leaving directory `/sources/blfs/MPlayer-1.0rc1/libvo'
make: *** [libvo/libvo.a] Error 2

A pattern emerges, like you say, old packages.

sort of wanted to change the subject away from BLFS releases.

5)  kdelibs3-5-10  with a kioslave/ftp error.   I hope this patch will work
out (see attached)  It did, but there is another error...  Later.  too many
bears out there!
Thanks! yo all!

On Fri, Feb 19, 2010 at 1:00 AM,
<blfs-support-request at linuxfromscratch.org>wrote:

> Send blfs-support mailing list submissions to
>        blfs-support at linuxfromscratch.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>        http://linuxfromscratch.org/mailman/listinfo/blfs-support
> or, via email, send a message with subject or body 'help' to
>        blfs-support-request at linuxfromscratch.org
>
> You can reach the person managing the list at
>        blfs-support-owner at linuxfromscratch.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of blfs-support digest..."
>
>
> Today's Topics:
>
>   1. Re: BLFS-6.4RC1 or any (Simon Geard)
>   2. Re: BLFS-6.4RC1 or any (Bruce Dubbs)
>   3. help tetex-src-3.0 error (Dale Stein)
>   4. Re: help tetex-src-3.0 error (Matthew Burgess)
>   5. Re: Building LFS/BLFS through ssh session question
>      (Pol Vangheluwe)
>   6. Re: help tetex-src-3.0 error (Corstiaan Hol)
>   7. Re: help tetex-src-3.0 error (Randy McMurchy)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 18 Feb 2010 21:19:04 +1300
> From: Simon Geard <delgarde at ihug.co.nz>
> Subject: Re: BLFS-6.4RC1 or any
> To: blfs-support at linuxfromscratch.org
> Message-ID: <1266481144.1580.22.camel at aiglos.home>
> Content-Type: text/plain; charset="utf-8"
>
> On Wed, 2010-02-17 at 08:32 -0600, Randy McMurchy wrote:
> > If the community's expectations are that we have the most current
> > release of every package in the most recent BLFS book, then the
> > expectations are too high and are unreasonable.
>
> It's not a reasonable expectation that the book will *always* have the
> most recent release, at any point in time. But it's somewhat troubling
> if we can't get the latest release into the book before it ceases to be
> the latest release.
>
> I guess that to my mind, it seems reasonable that a new package release
> might be incorporated into the book within a few months of release. As
> you say, incremental Gnome releases don't tend to be all that different
> to build, and I've typically had my home system upgraded within a few
> weeks.
>
> Now, since that clearly isn't possible at the moment, can you comment on
> why, and how people might help improve the situation?
>
> Simon.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 198 bytes
> Desc: This is a digitally signed message part
> Url :
> http://linuxfromscratch.org/pipermail/blfs-support/attachments/20100218/9b674cba/attachment-0001.bin
>
> ------------------------------
>
> Message: 2
> Date: Thu, 18 Feb 2010 02:33:17 -0600
> From: Bruce Dubbs <bruce.dubbs at gmail.com>
> Subject: Re: BLFS-6.4RC1 or any
> To: BLFS Support List <blfs-support at linuxfromscratch.org>
> Message-ID: <4B7CFB4D.4030006 at gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Simon Geard wrote:
> > On Wed, 2010-02-17 at 08:32 -0600, Randy McMurchy wrote:
> >> If the community's expectations are that we have the most current
> >> release of every package in the most recent BLFS book, then the
> >> expectations are too high and are unreasonable.
> >
> > It's not a reasonable expectation that the book will *always* have the
> > most recent release, at any point in time. But it's somewhat troubling
> > if we can't get the latest release into the book before it ceases to be
> > the latest release.
> >
> > I guess that to my mind, it seems reasonable that a new package release
> > might be incorporated into the book within a few months of release. As
> > you say, incremental Gnome releases don't tend to be all that different
> > to build, and I've typically had my home system upgraded within a few
> > weeks.
>
> The problem is volume.  There are about 300 packages in the book.  Most
> are updated 2 or more times a year.  I'd estimate there are two packages
> a day on average.   Some of the packages are very large and complex,
> e.g. firefox, gcc, gnome, kde.  They also need ot be integrated -- you
> can't really update just a part of kde or gnome.  They have to be done
> pretty much all at once.
>
> > Now, since that clearly isn't possible at the moment, can you comment on
> > why, and how people might help improve the situation?
>
> Patches to the xml for sets of the complcated packages on a regular
> basis would be helpful, but editors still need to check those until the
> submitter has shown quality work.
>
>   -- Bruce
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 18 Feb 2010 13:45:44 -0600
> From: Dale Stein <dstein2000 at gmail.com>
> Subject: help tetex-src-3.0 error
> To: blfs-support at linuxfromscratch.org
> Message-ID:
>        <d04628d41002181145l3bb7f917u270c5eeac47627a8 at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> I was wondering if anyone knew how to fix this problem
> I am trying to build teTeX-3.0 and it is coming back with a ulgy error.
> This was built with LFS 6.6 and BLFS svn.
>
> make[3]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c/lib'
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -g -O2 -c tangleboot.c -o
> tangleboot.o
> In file included from tangleboot.c:94:
> tangleboot.h:34: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> tangleboot.c:2175: error: conflicting types for 'getline'
> /usr/include/stdio.h:651: note: previous declaration of 'getline' was here
> make[2]: *** [tangleboot.o] Error 1
> make[2]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c'
> make[1]: *** [all] Error 1
> make[1]: Leaving directory `/sources/blfs/tetex-src-3.0/texk'
> make: *** [all] Error 1
>
> Thanks!!!!
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://linuxfromscratch.org/pipermail/blfs-support/attachments/20100218/81132bbf/attachment-0001.html
>
> ------------------------------
>
> Message: 4
> Date: Thu, 18 Feb 2010 20:02:52 +0000
> From: Matthew Burgess <matthew at linuxfromscratch.org>
> Subject: Re: help tetex-src-3.0 error
> To: BLFS Support List <blfs-support at linuxfromscratch.org>
> Message-ID: <4B7D9CEC.6010001 at linuxfromscratch.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Dale Stein wrote:
> > I was wondering if anyone knew how to fix this problem
> > I am trying to build teTeX-3.0 and it is coming back with a ulgy error.
> > This was built with LFS 6.6 and BLFS svn.
> >
> > make[3]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c/lib'
> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -g -O2 -c tangleboot.c -o
> > tangleboot.o
> > In file included from tangleboot.c:94:
> > tangleboot.h:34: error: conflicting types for 'getline'
> > /usr/include/stdio.h:651: note: previous declaration of 'getline' was
> here
> > tangleboot.c:2175: error: conflicting types for 'getline'
> > /usr/include/stdio.h:651: note: previous declaration of 'getline' was
> here
> > make[2]: *** [tangleboot.o] Error 1
> > make[2]: Leaving directory `/sources/blfs/tetex-src-3.0/texk/web2c'
> > make[1]: *** [all] Error 1
> > make[1]: Leaving directory `/sources/blfs/tetex-src-3.0/texk'
> > make: *** [all] Error 1
>
> Yep, that's a pretty common error with older source packages and newer
> Glibc which provides its own copy of getline() now.  The easiest way
> around this is something like:
>
> sed -i -e 's/getline/get_line/g' texk/web2c/lib/tangleboot.{c,h}
>
> i.e. just rename tetex's internal copy of getline to get_line.
>
> Regards,
>
> Matt.
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 18 Feb 2010 23:04:50 +0100
> From: Pol Vangheluwe <pol.vangheluwe at belgacom.net>
> Subject: Re: Building LFS/BLFS through ssh session question
> To: BLFS Support List <blfs-support at linuxfromscratch.org>
> Message-ID: <E94CDD8A-E7CB-4790-AAA4-352953FD1BF3 at belgacom.net>
> Content-Type: text/plain; charset=us-ascii
>
> Op 17-feb-2010, om 07:01 heeft stosss het volgende geschreven:
>
> > On Wed, Feb 17, 2010 at 12:37 AM, Bruce Dubbs <bruce.dubbs at gmail.com>
> wrote:
> >>
> >>
> >> kde generally uses konsole.  Do you really mean xterm?
> >>
> >> Does PCLinuxOS have any /dev/tty* devices?
> >>
> >> On the remote system, is it vi or vim?
> >>
> >> I think you are saying PCLinuxOS is the ssh client, but what is the sshd
> >> server?
> >>
> >> Typically, I just 'ssh host' to get a bash prompt and run vi->vim from
> >> there.
> >
> > PCLOS is the client and my lfs 6.5 is the server. Yes ssh host does
> > work in the terminal.
> >
> > PCLOS is a Mandriva fork and they both use all those different drake
> > tools for a lot of the config stuff. I don't think PCLOS follows FHS
> > closely. vim behaves very strangely in PCLOS any way, not like Fedora,
> > Debian and LFS.
> > --
>
> I have built LFS 6.4 completely remotely on my home network.
> I upload the sources with FTP and used telnet until I had enough tools to
> build openssh-4.7p1 (according BLFS-6.3).
> My client is the "Terminal" program of my Apple iMac.
> I built vim-7.2 and can use it in my ssh session.  There are however some
> inconveniences:
> - the sceenwidth always reduces automatically to (about) 80 characters when
> I start vim;
> - a CR seems to be inserted in existing lines, longer then (about) 80
> characters;
> - the text appears in unexpected colors with coloured background, which
> makes it mostly difficult to read.
> I always observe a double login when I start a ssh session.  I started a
> post about it (
> http://www.mail-archive.com/lfs-support@linuxfromscratch.org/msg11394.html)
> but got no reply.
>
> So I use vim only for simple tasks.  For more complex editing, I mount the
> remote disk on my iMac and use a local editor.
> To do so, I had to build netatalk-2.0.4 (not in the BLFS book) and to write
> an appropriate bootscript for the appletalk daemon.
>
> pvg
>
> ------------------------------
>
> Message: 6
> Date: Fri, 19 Feb 2010 00:01:46 +0100
> From: "Corstiaan Hol" <corstiaan.hol at gmail.com>
> Subject: Re: help tetex-src-3.0 error
> To: "BLFS Support List" <blfs-support at linuxfromscratch.org>
> Message-ID: <BB4C27C526AC4D07B2C9BBBB7E1FF088 at corstiaan123>
> Content-Type: text/plain; format=flowed; charset="iso-8859-1";
>        reply-type=original
>
> Matthew Burgess wrote:
> > Glibc which provides its own copy of getline() now.  The easiest way
> > around this is something like:
> >
> > sed -i -e 's/getline/get_line/g' texk/web2c/lib/tangleboot.{c,h}
>
> I suggest you to use the following patch to fix all errors at once:
>
> http://svn.cross-lfs.org/svn/repos/patches/tetex-src/tetex-src-3.0-gcc_4.4-1.patch
> Just apply it with:
> patch -Np1 -i ../tetex-src-3.0-gcc_4.4-1.patch
>
> should do the trick
>
> Corstiaan
>
>
>
> ------------------------------
>
> Message: 7
> Date: Thu, 18 Feb 2010 21:28:57 -0600
> From: Randy McMurchy <randy at linuxfromscratch.org>
> Subject: Re: help tetex-src-3.0 error
> To: BLFS Support <blfs-support at linuxfromscratch.org>
> Message-ID: <4B7E0579.6040002 at linuxfromscratch.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Corstiaan Hol wrote:
>
> > I suggest you to use the following patch to fix all errors at once:
>
> Or, wait a couple of days and I will have the new TeX Live
> instructions in the book which will replace the existing TeX.
>
> --
> Randy
>
>
>
> ------------------------------
>
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>
> End of blfs-support Digest, Vol 1970, Issue 1
> *********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-support/attachments/20100219/c3916ef5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kdelibs-3.5.10-gcc_4.4-2.patch
Type: application/octet-stream
Size: 11220 bytes
Desc: not available
URL: <http://lists.linuxfromscratch.org/pipermail/blfs-support/attachments/20100219/c3916ef5/attachment.obj>


More information about the blfs-support mailing list