[Kde-pim] Akonadi-1.2.1 build error

[Sagara Wijetunga]

Ingo Klöcker wrote:
> On Thursday 22 October 2009, Sagara Wijetunga wrote:
>   
>> Ingo Klöcker wrote:
>>     
>>> On Wednesday 21 October 2009, Sagara Wijetunga wrote:
>>>       
>>>> Ingo Klöcker wrote:
>>>>         
>>>>>> I tried following manually:
>>>>>> cd /usr/pkg/akonadi/build/libs/tests
>>>>>>
>>>>>> /usr/bin/automoc4
>>>>>> /usr/pkg/akonadi/build/libs/tests/notificationmessagetest_automo
>>>>>> c. cpp /usr/pkg/akonadi/akonadi-1.2.1/libs/tests
>>>>>> /usr/pkg/akonadi/build/libs/tests /usr/bin/moc /usr/bin/cmake
>>>>>>
>>>>>> Exit status ($?) is 1. No error message.
>>>>>>
>>>>>> Is there a way to run  automoc4 command with a verbose output?
>>>>>>             
>>>>> I don't think so. I suggest trying to compile automoc4 yourself.
>>>>> Maybe there's something wrong with the installed automoc4.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Ingo
>>>>>           
>>>> Ok, automoc4 removed and recompiled and reinstalled.
>>>> Removed Soprano (ver. 2.3.1) and recompiled and reinstalled.
>>>>
>>>> Reran the above /usr/bin/automoc4 statement in the
>>>> build/libs/tests. Result is still the same, exit status is 1.
>>>>
>>>> Does Soprano play any role in the above /usr/bin/automoc4
>>>> statement?
>>>>         
>>> No.
>>>
>>>       
>>>> Does Java availability or not availability play any role in the
>>>> above /usr/bin/automoc4 statement to fail?
>>>>         
>>> No.
>>>
>>>       
>>>> What else could I check to find the cause?
>>>>         
>>> You could compile automoc4 in debug mode (if you didn't do so
>>> already) and debug it.
>>>
>>> BTW, running the above automoc4 command on my system results in the
>>> output of
>>>   Generating notificationmessagetest.moc
>>> and in the generation of the files
>>>   notificationmessagetest_automoc.cpp
>>>   notificationmessagetest.moc
>>>
>>> Just so that you know what should happen.
>>>
>>>
>>> Out of curiosity: Can you build kdelibs?
>>>       
>> Did not try to build kdelibs.
>>
>> What I have installed so far related KDE4 are:
>> 1. automoc4-0.9.88
>> 2. soprano-2.3.1
>>
>> Akonadi cannot build.
>>
>> Tried to buid Phonon-4.3.0, its also the same issue as Akonadi,
>> /usr/bin/automoc4 fails.
>>
>> I'll try to debug Akonadi and see whether I can identify what causes
>> this error.
>>     
>
> Maybe somebody over at kde-freebsd 
> (https://mail.kde.org/mailman/listinfo/kde-freebsd) has some ideas.
>
>
> Regards,
> Ingo
>   
Ok, I have debugged the /usr/bin/automoc4. What happens is, 
AutoMoc::dotFilesCheck(bool x) exists with EXIT_FAILURE.

Breakpoint 1, AutoMoc::dotFilesCheck (this=0xbfbfe988, x=false)
    at /tmp/automoc4-0.9.88/kde4automoc.cpp:105
105         if (!x) {


(gdb) backtrace
#0  AutoMoc::dotFilesCheck (this=0xbfbfe988, x=false)
    at /tmp/automoc4-0.9.88/kde4automoc.cpp:105
#1  0x0804debe in AutoMoc::run (this=0xbfbfe988)
    at /tmp/automoc4-0.9.88/kde4automoc.cpp:259
#2  0x0805382c in main (argc=0, argv=0x0)
    at /tmp/automoc4-0.9.88/kde4automoc.cpp:114


The backtrace shows AutoMoc::dotFilesCheck() is called at line 259.

dotFiles.setFileName(args[1] + QLatin1String(".files"));
dotFiles.open(QIODevice::ReadOnly | QIODevice::Text);

const QByteArray &line = dotFiles.readLine();
Line 259 => dotFilesCheck(line == "SOURCES:\n");

Regards
Sagara

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/