On 2012-12-11 10:20:29 +0100, Sylvestre Ledru wrote:
> On 11/12/2012 10:18, Vincent Lefevre wrote:
> > Unfortunately I don't know how to do that. What I mean is that
> > if dragonegg-4.6 is built with gcc-4.6 4.6.3-14, then it should
> > have in its dependency:
> >
> > Depends: ..., gcc-4.6 (= 4.6
On 11/12/2012 10:18, Vincent Lefevre wrote:
> On 2012-12-11 09:36:20 +0100, Sylvestre Ledru wrote:
>> Could you provide a patch ? I am not sure to see what you mean.
>
> Unfortunately I don't know how to do that. What I mean is that
> if dragonegg-4.6 is built with gcc-4.6 4.6.3-14, then it should
On 2012-12-11 09:36:20 +0100, Sylvestre Ledru wrote:
> Could you provide a patch ? I am not sure to see what you mean.
Unfortunately I don't know how to do that. What I mean is that
if dragonegg-4.6 is built with gcc-4.6 4.6.3-14, then it should
have in its dependency:
Depends: ..., gcc-4.6 (= 4.
On 11/12/2012 09:21, Vincent Lefevre wrote:
> On 2012-12-11 07:38:47 +0100, Sylvestre Ledru wrote:
>> On 11/12/2012 00:23, Vincent Lefevre wrote:
>>> On 2012-12-10 20:44:08 +0100, Sylvestre Ledru wrote:
Gcc plugin system sucks from a distribution point of view...
The best solution would b
On 2012-12-11 07:38:47 +0100, Sylvestre Ledru wrote:
> On 11/12/2012 00:23, Vincent Lefevre wrote:
> > On 2012-12-10 20:44:08 +0100, Sylvestre Ledru wrote:
> >> Gcc plugin system sucks from a distribution point of view...
> >> The best solution would be to rebuild dragonegg at installation time.
>
On 11/12/2012 00:23, Vincent Lefevre wrote:
> On 2012-12-10 20:44:08 +0100, Sylvestre Ledru wrote:
>> Gcc plugin system sucks from a distribution point of view...
>> The best solution would be to rebuild dragonegg at installation time.
>
> How about adding dependencies?
>
> For instance, dragoneg
On 2012-12-10 20:44:08 +0100, Sylvestre Ledru wrote:
> Gcc plugin system sucks from a distribution point of view...
> The best solution would be to rebuild dragonegg at installation time.
How about adding dependencies?
For instance, dragonegg-4.6 could depend on some fixed version
of gcc-4.6. Or
On 10/12/2012 20:22, Vincent Legout wrote:> Hi,
>
> Vincent Lefevre writes:
>
>> The crash still occurs on the same testcase, with llvm-gcc
>> (provided by llvm-gcc-4.6).
>
> I also have this crash with the test.i file. However, rebuilding the
> source package or using the x86 version seem to fix
Hi,
Vincent Lefevre writes:
> The crash still occurs on the same testcase, with llvm-gcc
> (provided by llvm-gcc-4.6).
I also have this crash with the test.i file. However, rebuilding the
source package or using the x86 version seem to fix this bug. I guess
the amd64 package wasn't built correc
reopen 686231
found 686231 3.1-3
thanks
On 2012-09-28 14:51:08 +, Debian Bug Tracking System wrote:
> Changes:
> dragonegg (3.1-3) unstable; urgency=low
> .
>* Rebuild against the lastest version of gcc
>(Closes: #686231, #676499)
The crash still occurs on the same testcase, with l
10 matches
Mail list logo
