gcc-4.1.1

[Samuel Verstraete]

On Tue, 30 Jan 2007 17:53:39 -0800
Auke Kok <sofar at foo-projects.org> wrote:

> samuel verstraete wrote:
> > i felt like rebuilding everything after the gcc update... (i know
> > totally not needed and things like that but it was still fun ;) )
> > 
> > FYI:
> > Failed updated modules:
> 
> something is wrong with your setup. several of the modules below here
> compile just fine with gcc-4.1.1. Notably:
> 
>  > xfprint
>  > xfdesktop
>  > Terminal
>  > xfmedia
>  > verve-plugin
>  > thunar-volman
>  > thunar-media-tags-plugin

All of those work indeed... they just borked because w3c-libwww
wouldn't compile and somehow those modules compiled against libmd5.la
which is installed by it... i basically suspect libtool just borking
around ...

> 
> really work just right
> 
>  > xdelta
> 
> that was reported to the author and a new version is in alpha now.
> fix expected soon.
> 
> > db
> 
> # lvu compiler db
> /usr/bin/db_archive GCC: (GNU) 4.1.1
> /usr/bin/db_checkpoint GCC: (GNU) 4.1.1
> /usr/bin/db_deadlock GCC: (GNU) 4.1.1
> etc... compiles just fine.

had CONFLICTS on the java modules that were not solved :)

> 
> 
> > gpm
> > lcms
> > avifile
> > w3c-libwww
> > xmms
> > ffmpeg
> > mjpegtools
> > gst-ffmpeg
> > mailx
> > ZopeInterface
> > libofa

> > R
Borked because in PRE_BUILD it was checking for f77 while these days it
is replaced by gfortran... so that was an easy fix :^)


> > Murrine-Engine
> > testdisk
> > qtiplot
> > kino
> > gliv
> > djvulibre
> > cdrkit
> > pigment
> > 
> > Still gonna have to look into them in more details but this is just
> > to inform you ;)
> 
> I suspect that you have another breakage. is this i386 or x86_64 ?
> optimizations?

No optimizations and just plain i686 . But indeed i had other stuff
that was b0rked :)

> 
> Auke
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev