Aurélien Gâteau wrote:
Having been bit with the gcc 4.1 bugs again, I figured it would be better to
prevent users from building with gcc 4.1 unless they explicitly ask for it.
Attached patch does this. It prevents the user from building with gcc 4.1
unless he calls cmake with
Hi,
Nikolay Mitev wrote:
I thought the problem was not GCC 4.1 but a boost version 1.33.2
compiled with GCC 4.1. Maybe it is best to check for that combination
and not only for GCC 4.1.
Actually, it's programs using boost which are compiled with gcc 4.1.
Cheers,
Dave.
--
Dave Neary
On Friday 05 October 2007 09:43:45 Nikolay Mitev wrote:
Aurélien Gâteau wrote:
Having been bit with the gcc 4.1 bugs again, I figured it would be better
to prevent users from building with gcc 4.1 unless they explicitly ask
for it.
Attached patch does this. It prevents the user from
Much better for me. GCC 4.2 is just not an option for Fedora
at the moment :-)
--alec
Ursprungligt meddelande
Från: [EMAIL PROTECTED]
Datum: 05-10-2007 15:10
Till: wengophone-devel@lists.openwengo.com
Ärende: Re: [Wengophone-devel] [PATCH] Stronger warn against
gcc 4.1
On Friday 05
I'm observing phapi-test crash.
Is it because of this issue?
I'm using GCC-4.1.0 and boost_1_34_0 on Suse 10.1
Thanks
Mangesh
On Fri, 2007-10-05 at 15:31 +0200, Alec leamas wrote:
Much better for me. GCC 4.2 is just not an option for Fedora
at the moment :-)
--alec
Ursprungligt
On Friday 05 October 2007 16:00:56 Mangesh Kulkarni wrote:
I'm observing phapi-test crash.
Is it because of this issue?
I'm using GCC-4.1.0 and boost_1_34_0 on Suse 10.1
Probably not, since phapi does not use Boost.
Aurélien
___
Wengophone-devel
Hi all,
I'm pleased to announce the addition of a new committer to the OpenWengo
repository, Alec Leamas. In the past month or so, he has done great work
on the ALSA driver for phmedia, and has shown a great ability to
identify problems and exercise good judgement.
Alec, welcome to the team!
Aurélien,
Indeed:
#1 the crash file attempts to write the binary directiory, which does
not happen on my system
#2 indeed, the FTP fails, appears the server is indeed down.
mystery solved, I'll try 2.2
I agree with your suggestion, or perhaps just create the report, and
allow the user to
