> That's the case of recent macOS versions. 
> 
> 
> Judging from the code, 10.3 returns libruby.a as $librubyarg while it doesn't 
> have such a static library, but does have a shared library.  As a result,  
> RUBY_LIBS is set to something like "libruby.a -L/.../" which causes link 
> error.  Therefore, libruby.a must be replaced with -lruby if 
> $librubydir/libruby.a doesn't exist and if $librubyarg is equal to libruby.a
> 

I couldn’t find any reference neither to this nor to such problem with 
LIBRUBYARG in RbConfig on OS X 10.3. Can you please substantiate this by some 
links to discussions?

> The correct variable is $librubya. 
> 
> 
> No.  Our goal is to set RUBY_LIBS to canonical "-L$rubylibdir $librubyarg", 
> which would look like, e.g., "-L/usr/local/lib -lruby".  Only for 10.3 (or 
> systems having the same RbConfig bug), $librubyarg must be replaced with 
> -lruby to avoid link error.  We don't need to care about 
> libruby-X.Y..Z-static.a at all from the outset.
> 

Our goal is never that, since vim attempts to use static library on other 
unixes. The specific case for macOS is exactly due to inexistence of a static 
library there. 

What we need to care are two things: (1) the in-existence of the static library 
and (2) the sanity of the ruby configuration. When both are met, we decide that 
there simply is no static library at all. 

> 
> Besides that, as I already wrote above, your current patch makes the code 
> about macOS completely useless. And I’m trying to ask you what is the point 
> of it.
> 
> 
> 
> You argued on the basis of a wrong assumption (See above). Rather, your patch 
> breaks 10.3 build.
> 

Unfortunately, I don’t have OS X 10.3. I would wonder if this is truly the only 
thing that breaks it and if the current version even builds there. As well, as 
I would wonder if there is anyone left wishing to build latest vim on OS X 
10.3. 

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui