This is fixed upstream and will be part of 4.10.3. You might want to use
the official patch. (almost the same as this one).
https://projects.kde.org/projects/kde/kdepim/repository/revisions/2573a6678d3415d7de8024a417d8f2e92b8c7611
On 04/03/2013 07:46 AM, rthom...@higgs.linuxfromscratch.org wrote
Le 03/04/2013 00:26, Bruce Dubbs a écrit :
> Pierre Labastie wrote:
>> Le 02/04/2013 19:39, Bruce Dubbs a écrit :
>>
>>> I think the pmap tests issues have something to do with jhalfs as I
>>> can't get it to fail outside of the full jhalfs build.
>> Problem is: the tests passed three times on 64 b
Le 03/04/2013 08:03, Bruce Dubbs a écrit :
> I'm pretty sure I tracked down this problem. In pmap.exp there is:
>
> spawn $pmap -X 1
> expect_pass $test "$pmap_initname\$"
>
> and spawn is doing some things with stty and the pmap program's newline
> characters are being converted to \r\n. The exp
Le 03/04/2013 08:03, Bruce Dubbs a écrit :
> Bruce Dubbs wrote:
> To make that pass, we need to do: sed -i -r
> 's/(pmap_initname)\\\$/\1/' ./testsuite/pmap.test/pmap.exp
Actually, a similar sed was in the previous version of the page. It got
suppressed when updating to the new version of procps
Pierre Labastie wrote:
> Le 03/04/2013 08:03, Bruce Dubbs a écrit :
>> Bruce Dubbs wrote:
>> To make that pass, we need to do: sed -i -r
>> 's/(pmap_initname)\\\$/\1/' ./testsuite/pmap.test/pmap.exp
> Actually, a similar sed was in the previous version of the page. It got
> suppressed when updatin
When switching to gcc 4.8.0, the test of g++ was added to
version-check.sh, but not to the list of requirements. Only GCC appears,
which could be anything from the gcc executable to the whole compiler
collection. Maybe this should be made clearer that g++ is needed.
I'll commit a change to jhalf
On Wed, 2013-04-03 at 22:22 +0200, Pierre Labastie wrote:
> When switching to gcc 4.8.0, the test of g++ was added to
> version-check.sh, but not to the list of requirements. Only GCC appears,
> which could be anything from the gcc executable to the whole compiler
> collection. Maybe this should
Pierre Labastie wrote:
> When switching to gcc 4.8.0, the test of g++ was added to
> version-check.sh, but not to the list of requirements. Only GCC appears,
> which could be anything from the gcc executable to the whole compiler
> collection. Maybe this should be made clearer that g++ is needed.
>
Le 03/04/2013 22:33, Matt Burgess a écrit :
> On Wed, 2013-04-03 at 22:22 +0200, Pierre Labastie wrote:
>> When switching to gcc 4.8.0, the test of g++ was added to
>> version-check.sh, but not to the list of requirements. Only GCC appears,
>> which could be anything from the gcc executable to the
Bruce Dubbs wrote:
> Pierre Labastie wrote:
>> When switching to gcc 4.8.0, the test of g++ was added to
>> version-check.sh, but not to the list of requirements. Only GCC appears,
>> which could be anything from the gcc executable to the whole compiler
>> collection. Maybe this should be made clea
On Wed, 2013-04-03 at 15:52 -0500, Bruce Dubbs wrote:
> Bruce Dubbs wrote:
> > Pierre Labastie wrote:
> >> When switching to gcc 4.8.0, the test of g++ was added to
> >> version-check.sh, but not to the list of requirements. Only GCC appears,
> >> which could be anything from the gcc executable to
Le 03/04/2013 22:41, Bruce Dubbs a écrit :
> Pierre Labastie wrote:
>> When switching to gcc 4.8.0, the test of g++ was added to
>> version-check.sh, but not to the list of requirements. Only GCC appears,
>> which could be anything from the gcc executable to the whole compiler
>> collection. Maybe
On Wed, 2013-04-03 at 22:03 +0100, Matt Burgess wrote:
> Whether or not one can, following the 'rewrite in a subset of C++' in
> 4.8.0, now do --enable-languages=c++ on GCC's configure line and get a
> working C++ compiler sans C support 'baggage' is an interesting
> question. I might give it a t
13 matches
Mail list logo
