On Jul 12, 2013, at 12:44 PM, Branko Čibej <br...@wandisco.com> wrote:
> 
> On 12.07.2013 18:14, Daniel J. Luke wrote:
>> On Jul 12, 2013, at 11:44 AM, Branko Čibej <br...@wandisco.com>
>>  wrote:
>> 
>>> On 11.07.2013 23:11, Daniel J. Luke wrote:
>>> 
>>>> Hello, I (co-)maintain the MacPorts subversion port (and most of the 
>>>> bindings ports). I haven't yet updated to 1.8.0 since the swig bindings 
>>>> all fail to build with gnome keyring errors (e.g. 
>>>> subversion/bindings/swig/python/core.c:3851:59: error: unknown type name 
>>>> 'svn_auth_gnome_keyring_unlock_prompt_func_t' and 
>>>> subversion/bindings/swig/python/core.c:3853:32: error: use of undeclared 
>>>> identifier 'SVN_AUTH_PARAM_GNOME_KEYRING_UNLOCK_PROMPT_FUNC')
>>>> 
>>>> I see a thread on subversion-dev (
>>>> 
>>>> http://svn.haxx.se/dev/archive-2013-06/0270.shtml
>>>> ) about this, but no patches (yet?) and the latest nightly (r1502103) 
>>>> appears to have the same issue. I haven't found a patch or a bug in the 
>>>> subversion issue tracker (but maybe I'm just bad at searching).
>>>> 
>>> You can regenerate the Swig wrappers, by running autogen.sh. I find that 
>>> solves the problem for me on Mac OS.
>>> 
>> Can I ask exactly what you are doing (you can pretend I'm dumb :-) )
>> 
>> When I regen with ./autogen.sh --release, I get the same errors as before 
>> (with 1.8.0).
>> 
> 
> Don't use the --release flag. That intentionally avoids regenerating the Swig 
> wrappers. :)

If I run it without --release I don't get the spew related to running swig 
(that I get with --release). Instead, I get swig complaining about 
-no-cpp-precomp (which I can track down, it shouldn't be passed to anything on 
any recent Mac OS X anyway...)

progress (maybe)?

--
Daniel J. Luke                                                                  
 
+========================================================+                      
  
| *---------------- dl...@geeklair.net ----------------* |                      
    
| *-------------- http://www.geeklair.net -------------* |                      
    
+========================================================+                      
  
|   Opinions expressed are mine and do not necessarily   |                      
    
|          reflect the opinions of my employer.          |                      
    
+========================================================+



Reply via email to