Randy McMurchy wrote:
> (note that stuff in trunk that is going to the 6.3 branch won't
> have a changelog entry).
>
Oops...that too.
-- DJ
--
This message has been scanned for viruses and
dangerous content, and is believed to be clean.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-
Dan Nicholson wrote:
> You can either have another shallow checkout of
> svn://.../BLFS/branches/6.3, or just one huge checkout of
> svn://.../BLFS that has all the branches, tags and trunk. Applying
> individual commits in svn is sortof a PITA, but here's a little
> workflow that works for me:
>
>
Dan Nicholson wrote these words on 05/14/08 22:49 CST:
> You can either have another shallow checkout of
> svn://.../BLFS/branches/6.3, or just one huge checkout of
> svn://.../BLFS that has all the branches, tags and trunk. Applying
> individual commits in svn is sortof a PITA, but here's a littl
On Wed, May 14, 2008 at 7:54 AM, Robert Daniels
<[EMAIL PROTECTED]> wrote:
>
> Now another question: I'm not familiar with working with branches, and
> that's not something I saw covered in the editor's guide. I figure I
> go ahead and commit to trunk, but how do I go about getting this merged
>
Robert Daniels wrote these words on 05/14/08 09:54 CST:
> Now another question: I'm not familiar with working with branches, and
> that's not something I saw covered in the editor's guide. I figure I
> go ahead and commit to trunk, but how do I go about getting this merged
> to the 6.3 branch
Robert Daniels wrote:
> Now another question: I'm not familiar with working with branches, and
> that's not something I saw covered in the editor's guide. I figure I
> go ahead and commit to trunk, but how do I go about getting this merged
> to the 6.3 branch? Do I need a separate checkout an
On Wednesday 14 May 2008 08:29:36 Randy McMurchy wrote:
> Robert Daniels wrote these words on 05/14/08 02:08 CST:
> > So, do we want to make use of this patch, or do we want to disable
> > ffmpeg support by default by adding --without-ffmpeg to the
> > configure? Especially considering the feature
Robert Daniels wrote these words on 05/14/08 02:08 CST:
> So, do we want to make use of this patch, or do we want to disable
> ffmpeg support by default by adding --without-ffmpeg to the configure?
> Especially considering the feature is experimental anyway.
I think disabling FFmpeg support is
My classes for the semester are wrapping up, so I'm hoping to have some
time to devote to development for a while. It's been too long.
Anyway, doing some test building, I rediscovered that akode doesn't
build against the book's ffmpeg. The ffmpeg support is supposed to be
experimental, but is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
M.Canales.es wrote:
> Akode includes an experimental FFmpeg codec support that in akode-2.0.1 is
> not
> enabled by default, but in akode-2.0.2 it is enabled if FFmpeg is found, but
> it fail to build against the current FFmpeg version in BLFS wit
M.Canales.es wrote:
> El Miércoles, 15 de Agosto de 2007 00:18, Randy McMurchy escribió:
>
>> I thought about this today as well. And if Bruce doesn't have the time
>> to update, I've already installed and logged about 1/3 of the KDE
>> packages, so it wouldn't be hard to update. I'd like get it d
El Miércoles, 15 de Agosto de 2007 00:18, Randy McMurchy escribió:
>
> I thought about this today as well. And if Bruce doesn't have the time
> to update, I've already installed and logged about 1/3 of the KDE
> packages, so it wouldn't be hard to update. I'd like get it done one
> way or the othe
El Miércoles, 15 de Agosto de 2007 01:29, Randy McMurchy escribió:
> Dan Nicholson wrote these words on 08/14/07 18:19 CST:
> > $ readelf -s /usr/lib/libavformat.so | grep av_seek_frame
>
> [EMAIL PROTECTED]: ~ > readelf -s /usr/lib/libavformat.so | grep av_seek_frame
>112: 0001e520 1670 FUNC
Dan Nicholson wrote these words on 08/14/07 18:19 CST:
> $ readelf -s /usr/lib/libavformat.so | grep av_seek_frame
[EMAIL PROTECTED]: ~ > readelf -s /usr/lib/libavformat.so | grep av_seek_frame
112: 0001e520 1670 FUNCGLOBAL DEFAULT 10 av_seek_frame_binary
132: 0001fe30 1885 FUNC
On 8/14/07, M.Canales.es <[EMAIL PROTECTED]> wrote:
> El Miércoles, 15 de Agosto de 2007 00:43, Dan Nicholson escribió:
>
> > Well, it looks like it's trying to get the linker to not barf on
> > undefined symbols with -Wl,--allow-shlib-undefined, but maybe I don't
> > understand that option correct
El Miércoles, 15 de Agosto de 2007 00:43, Dan Nicholson escribió:
> Well, it looks like it's trying to get the linker to not barf on
> undefined symbols with -Wl,--allow-shlib-undefined, but maybe I don't
> understand that option correctly. Anyway, in my ffmpeg from 20070128,
> libavformat has av_
On 8/14/07, Randy McMurchy <[EMAIL PROTECTED]> wrote:
>
> FFmpeg is so particular as their API changes. Packages are constantly
> trying to update their required version numbers (of SVN FFmpeg) to keep
> up. It is a losing battle. Note Dan's recent comment about a GStream
> dev that said they just
On 8/14/07, M.Canales.es <[EMAIL PROTECTED]> wrote:
> /bin/sh ../../../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long
> -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align
> -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2
> -Wformat-security -Wmissing-format
M.Canales.es wrote these words on 08/14/07 16:08 CST:
> Trying to build KDE I noticed that akode-2.0.1 in not available upstream,
> current version is akode-2.0.2. And there is no akode-2.0.1 packages on
> anduin nor other mirrors.
>
> Thus we need to update akode to 2.0.2
I agree.
> (ther
Hi,
Trying to build KDE I noticed that akode-2.0.1 in not available upstream,
current version is akode-2.0.2. And there is no akode-2.0.1 packages on
anduin nor other mirrors.
Thus we need to update akode to 2.0.2 (there is also KDE-3.5.7 availble but no
open ticket yet) or change the dowload
20 matches
Mail list logo
