octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: failed build after rev b646413c3d0e


From: Jordi Gutiérrez Hermoso
Subject: Re: failed build after rev b646413c3d0e
Date: Wed, 31 Aug 2011 17:30:16 -0500

2011/8/31 Ben Abbott <address@hidden>:
> On Aug 31, 2011, at 6:17 PM, Jordi Gutiérrez Hermoso wrote:
>
>> On 31 August 2011 16:05, Andreas Weber <address@hidden> wrote:
>>> Am 31.08.2011 21:42, schrieb Ben Abbott:
>>>> On Aug 31, 2011, at 3:36 PM, Andreas Weber wrote:
>>>>
>>>>> Am 31.08.2011 21:15, schrieb Ben Abbott:
>>>>>> After the changeset below ...
>>>>>> http://hg.savannah.gnu.org/hgweb/octave/rev/b646413c3d0e
>>>>>> My build is failing.
>>>>>
>>>>> Hi Ben, I have build b646413c3d0e at 31. Aug 18:27 CEST without
>>>>> problems on Debian wheezy, gcc version 4.6.1 x86_64-linux-gnu.
>>>>> Likely a Mac specific problem? Andy
>>>>
>>>> I do expect that MacOS will be alone in complaining. If I
>>>> understand the error correctly, the problem is that
>>>>
>>>> .libs/liboctave_la-Sparse-b.o and .libs/liboctave_la-Sparse-C.o
>>>> each contain the symbol Sparse<bool>::Sparse(PermMatrix const&)
>>>>
>>
>> Yes, this seem to be what ld is complaining aboutn
>>
>>>> Is this not the case for your build? ... or is it that your gcc
>>>> doesn't consider that an error? Ben
>>>
>>> I forgot to mention that I'm using ccache as Jordi does as far as I
>>> know.
>>
>> I'm using ccache too, so it's conceivable that ccache is somehow
>> preventing both of us from seeing the problem and that I did indeed
>> break something.
>>
>> As far as I can tell, I only instantiate that symbol once from the
>> source file Sparse.cc... what could happen is that this file is
>> getting compiled twice, for some odd reason.
>>
>> Could I get a full compilation log? Zip it.

>
> Are you asking for a log from me?

Yep.

     make clean && make > compile.log 2>&1

Or some other "make" command if that's what you use. That should put
it into compile.log, just zip it after that.

TIA,
- Jordi G. H.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]