Re: Patches in RedHat 8.0 package

[cm...@collab.net]

Brandon Ehle <be...@pipedreaminteractive.com> writes:

> Rather than accumulating tons of patches in the RedHat 8.0 packages, I
> am posting them here for inclusion in the main tree or finding another
> suitable fix.

Brandon, can you explain what problems you were seeing that inspired
these patches?  I've been building (and using) the swig bindings with
no problems.

Well, except those problems that trow keeps committing... :-)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: Patches in RedHat 8.0 package

[Brandon Ehle <az...@yahoo.com>]

cmpilato@collab.net wrote:

>Brandon Ehle <be...@pipedreaminteractive.com> writes:
>
>  
>
>>Rather than accumulating tons of patches in the RedHat 8.0 packages, I
>>am posting them here for inclusion in the main tree or finding another
>>suitable fix.
>>    
>>
>
>Brandon, can you explain what problems you were seeing that inspired
>these patches?  I've been building (and using) the swig bindings with
>no problems.
>  
>
The top patch is a fix for breakage from yesterday.  The swig compiler 
doesn't seem to be able to handle that line.  This could just be swig 
breakage if its not happening for you.  (Although this file did change 
in revision 3387 when my build stopped working.)

I am not sure how you can run without the second patch.  Never anywhere 
does a libsvn_swig_py-1.a get built.  I don't even see a rule anywhere 
that could build one.  Are you sure that you don't have an old library 
laying around that no longer has a rule to build it?

The third patch is probably swig breakage, I will ask on the swig 
mailing list about that one if its working for you.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org