Hi Dimitri,

> Am 29.11.2014 um 14:44 schrieb Dimitri van Heesch <[email protected]>:
>> On 28 Nov 2014, at 12:16 , Dagobert Michelsen <[email protected]> wrote:
>> 
>> Hi Dimitri,
>> 
>> I noticed the current „configure“ of doxygen is broken on my Solaris 
>> continuous integration:
>>> 
>>> Autodetected platform solaris-g++... 
>>> Checking for GNU make tool... using /opt/csw/bin/gmake
>>> Checking for GNU install tool... using /usr/bin/install
>>> Checking for dot (part of GraphViz)... using /opt/csw/bin/dot
>>> 
>>> ./configure: syntax error at line 558: `libclang_hdr_dir=$' unexpected
>>> 
>>> program finished with exit code 2
>>> elapsedTime=0.264766
>> 
>> Can you please have a look?
> 
> I think a bash specific construct has crept in. Can you check if changing 
> lines 558 and 559 by
> 
>    libclang_hdr_dir=`llvm-config --includedir`
>    libclang_lib_dir=`llvm-config --libdir`
> 
> helps?

Yes, that looks much better. You can check the doxygen build status on Solaris 
at
  
https://buildfarm.opencsw.org/buildbot/waterfall?builder=doxygen-solaris10-i386&builder=doxygen-solaris10-sparc&reload=none
If you want I can set up email notification when something breaks.


Best regards

  — Dago

-- 
"You don't become great by trying to be great, you become great by wanting to 
do something,
and then doing it so hard that you become great in the process." - xkcd #896

Attachment: smime.p7s
Description: S/MIME cryptographic signature

------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Doxygen-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doxygen-develop

Reply via email to