Bug 139352 - sys-devel/icecream-0.7.14 (version bump)
|
Bug#:
139352
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: hp-cluster@gentoo.org
|
Reported By: furlongm@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: sys-devel/icecream-0.7.14 (version bump)
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2006-07-05 11:52 0000
|
ebuild for new version of sys-devel/icecream
(In reply to comment #5)
> ftp://ftp.suse.com/pub/projects/icecream/ contains version 0.7.5
> 0.7.3a is no longer available
>
> It would be great if you could provide an updated ebuild.
>
No problem, I'm waiting for 0.7.6 to be released, svn contains a lot of little
fixes over 0.7.5
Created an attachment (id=94059) [details]
files/icecream-config
icecream-config (similar to distcc-config or ccache-config for adding/removing
symlinks). just updated to use ICECC/icecc instead of ICEC/icec, it was meant
to be like this in first place, and is a purely cosmetic update.
Works great here. Thanks!
icecc-create-env has a bug, the checks "if file "$path" | grep" should be
"if file -L "$path" | grep", note -L parameter. On my installation /usr/bin/as
is a symlink:
$ file /usr/bin/as
/usr/bin/as: symbolic link to `i686-pc-linux-gnu-as'
$ file -L /usr/bin/as
/usr/bin/as: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for
GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux 2.6.9,
stripped
BTW, current release of icecc is 0.7.12, "cp icecream-0.7.6.ebuild
icecream-0.7.12.ebuild" works fine.
Created an attachment (id=96729) [details]
./icecc-create-env.patch
Confirmed bug described by Sergey Okhapkin in Comment #14.
This is a patch to make the change he describes.
After applying this patch and clearing out /var/cache/icecream,
0.7.12 works as expected.
*** Bug 141899 has been marked as a duplicate of this bug. ***
Are the latest files good to bump and go for 0.7.14? I'd like to commit these
updates tomorrow or so.
(In reply to comment #20)
> Are the latest files good to bump and go for 0.7.14? I'd like to commit these
> updates tomorrow or so.
>
Yep, they're ready.
(In reply to comment #21)
> (In reply to comment #20)
> > Are the latest files good to bump and go for 0.7.14? I'd like to commit these
> > updates tomorrow or so.
> >
>
> Yep, they're ready.
>
Any chance of getting this ebuild into portage? 0.7.14 is the stable upstream
release and was successfully used in a cluster of around 200 recently without
any problems.
Fixed, finally! Thanks for your patience.