Summary: | libdvdnav-0.1.2-r2 won't build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rigo <rigo> |
Component: | Current packages | Assignee: | Brandon Low (RETIRED) <lostlogic> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | tester |
Priority: | High | ||
Version: | 1.3 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Fix for a proposed libdvdnav-0.1.2-r3 |
Description
Rigo
2002-08-01 17:15:08 UTC
Ditto here. GCC3.2 all yours, lolo The same for me with gcc pre_3.2 (fresh install : untarred 1.3b stage 1 tarball, unmasked gcc pre_3.2 and emerged it, then bootstrap, system... I had no problem doing this and it seems to work just fine except for this ebuild.) But it built fine on gcc 3.1. (1.3b stage 1). From what I read in the ebuild it is quite normal : # This nice little patch that makes compilation work on gcc2 # breaks compilation on gcc-3.1 so, don't use it if we are # going to be running gcc-3.1 [ -z "${CC}" ] && export CC=gcc [[ "`${CC} -dumpversion`" != "3.1" ]] && \ ( patch < ${FILESDIR}/${P}-gentoo.patch || die ) so the patch got applied with pre_3.2, but not with 3.1. (the same problem applies to gcc 3.1.1, the patch should only be applied with 2.9???) Of course I commented out the offending section and it built just fine on pre_3.2. Don't quite understand why it did occur for the reporter, that should have been using gcc 3.1, if I understand correctly the first line. ea. is a lot (incl. 3.2pre ;) ...Sorry 4 that...Changed 3.2 worked for me too :-D Thanx a lot, Rigo Created attachment 2916 [details, diff]
Fix for a proposed libdvdnav-0.1.2-r3
The test only applies a patch to GCC 2. As GCC 2.95.3 is the only GCC 2 version
in portage, it makes much more sense to test for it this way.
This is fixed in libdvdnav-0.1.3, right? so we can just forget about this and move on with our lives? I can confirm that this is fixed thanks |