On Mon, Jan 23, 2012 at 03:21:11PM +0100, Chris Brody <chris.br...@gmail.com>
wrote:
> Yep maybe you should look for some volunteers to help with OSX?
> Personally I have no time right now but I can help after 1-2 months.
> Also, I wonder if the LLVM "clang" could be fixed, at least for this
> one issue?
If it even is a clang issue, the error message looked like a gcc one to
me.
the newest problem with clang is that it doesn't parse tentative
declarations correctly and throw an error. that could presumably be fixed
by leaking all private symbols to the shared object, which probbably is
harmless and only incraeses the size of the binary.
But it's apparently a new clang 3.0 problem, and I guess since apple uses
llvm-gcc and not clang, it's quite pointless, as gcc is easier to come by
than clang.
Could be wrong though, maybe apple switched to clang?
It's really a fats moving target, where static hacks depending on os x don't
really work well.
Whats worse is that there are a number of free software extensions, such as
macports and fink, and breaking it for them is imho not an option - they
should altogether be preferred over apples proprietary stuff.
--
The choice of a Deliantra, the free code+content MORPG
-----==- _GNU_ http://www.deliantra.net
----==-- _ generation
---==---(_)__ __ ____ __ Marc Lehmann
--==---/ / _ \/ // /\ \/ / schm...@schmorp.de
-=====/_/_//_/\_,_/ /_/\_\
_______________________________________________
libev mailing list
libev@lists.schmorp.de
http://lists.schmorp.de/cgi-bin/mailman/listinfo/libev
