This bug you linked is reported for llvm-gcc, not clang, but I guess they
share the same issue.
You can close the bug report.
Thanks,
Marko
On Feb 1, 2012 10:41 PM, "Juan Jose Garcia-Ripoll" <
juanjose.garciarip...@googlemail.com> wrote:
>
>
> On Tue, Jan 31, 2012 at 11:58 PM, Marko Kocić <marko.ko...@gmail.com>wrote:
>
>> Hi Juan,
>>
>> In order to try windows build without installing older gcc, I tried to
>> build it using clang.
>> It built C code fine, but failed in linking phase.
>>
>> I opened a bug at
>> https://sourceforge.net/tracker/?func=detail&aid=3482358&group_id=30035&atid=398053
>>
>>
>> It seems that gcc and clang on windows use different naming convention
>> for exported symbols (leading underscores or not) on windows. I don't have
>> an idea if fixing clang/windows build would be simple enough to take it
>> into the release?
>>
>
> Apparently the problem is LLVM's. It is a bug in their compiler, which
> does not produce the right link flags for symbols with declspec(dllexport)
>
> See http://permalink.gmane.org/gmane.comp.compilers.llvm.bugs/4614
>
> Can I close the bug report?
>
> Juanjo
>
> --
> Instituto de Física Fundamental, CSIC
> c/ Serrano, 113b, Madrid 28006 (Spain)
> http://juanjose.garciaripoll.googlepages.com
>
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Ecls-list mailing list
Ecls-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ecls-list
