Re: Specifying a C++11 compatible pre-dependency
Depend on gcc-4.8 and override CC=cc-4.8 on powerpc in debian/rules. Ondřej Surý On 16. 5. 2013, at 5:20, Shachar Shemesh shac...@debian.org wrote: Hi all, I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? Shachar P.S. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. 1 - http://packages.qa.debian.org/f/fakeroot-ng.html
Specifying a C++11 compatible pre-dependency
Hi all, I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? Shachar P.S. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. 1 - http://packages.qa.debian.org/f/fakeroot-ng.html
Re: Specifying a C++11 compatible pre-dependency
Hi! On Wed, 2013-05-15 at 18:15:37 +0300, Shachar Shemesh wrote: I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? You should usually (depending on the upstream build system) be able to force a different compiler with something like «make CXX=g++-4.8», or at configure time for example. You'll need to depend explicitly on g++-4.8 though. Regards, Guillem -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130515160131.ga14...@gaara.hadrons.org
Re: Specifying a C++11 compatible pre-dependency
On 2013-05-15 17:15, Shachar Shemesh wrote: I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. What about Build-Depends: g++-4.7 and ./configure ... CC=gcc-4.7 CXX=g++-4.7 ? Andreas -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5193ad98.2090...@debian.org
Re: Specifying a C++11 compatible pre-dependency
On Wed, May 15, 2013 at 06:15:37PM +0300, Shachar Shemesh wrote: package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Just specify the compiler you want: Build-Depends: gcc-4.7 CC=gcc-4.7 ./configure Bothering with alternatives is a waste of time as gcc-defaults will be updated to either 4.8 or a mixture of 4.7/4.8 soon; I kind of remember doko saying something about the beginning of June. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. You want qemu-system for that. Too bad, current qemu is incapable of running wheezy d-i, and upgrading from squeeze took me a crapload of effort. I heard that qemu's trunk (scheduled to release in a week) has this fixed, and our qemu team will wrangle it into shape soon, but if you want my upgraded image, say a word. -- ᛊᚨᚾᛁᛏᚣ᛫ᛁᛊ᛫ᚠᛟᚱ᛫ᚦᛖ᛫ᚹᛖᚨᚲ -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130515160600.ga8...@angband.pl
Specifying a C++11 compatible pre-dependency
Hi all, I have a package[1] that will not transition to testing due to failed compilation on powerpc. The problem is that the actual package requires a fairly complete C++11 support in order to compile. I have tried to signify this by adding Build-Depends: gcc (= 4:4.7) to the dependencies. On PowerPC, despite gcc version 4.7 (and, indeed, 4.8) being available, the gcc package is for version 4.6.4. This means that without some platform specific tricks in the package (as I don't have a PowerPC platform, these tricks are hard to know), the package fails dependencies. Even if that were not the case, the package would fail to build, as gcc points to gcc-4.6.4. Is there some better way to cause the system to use a C++11 capable compiler? Shachar P.S. I no longer have a PowerPC platform to test with, and qemu-user isn't emulating deep enough for fakeroot-ng to work under (and is extremely buggy for PowerPC emulation anyways). As such, the best I can tell at the moment is that under ppc, when specifying gcc-4.8 compiler, the code compiles. 1 - http://packages.qa.debian.org/f/fakeroot-ng.html
