[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] reenable libtool options

From: Stefan Sperling <stsp_at_elego.de>
Date: Fri, 17 Jun 2011 13:08:52 +0200

On Sun, Mar 01, 2009 at 05:01:48PM +0000, Philip Martin wrote:
> Justin Erenkrantz <justin_at_erenkrantz.com> writes:
> > On Sun, Mar 1, 2009 at 4:41 AM, Philip Martin <philip_at_codematters.co.uk> wrote:
> >> Justin feels that is not acceptable, I'm not really sure why but I
> >> think it's because it creates libtool dropping in the build dir.
> >
> > I repeatedly said why - I looked at all of the other broken code that
> > was removed with it. Almost all of the autogen.sh logic was bad and
> > would need to be reworked substantially to be 'proper'.
> That bad logic didn't seem to affect me.
> > Rather than
> > continue to apply more and more band-aids on top of broken band-aids,
> > I do not feel that Subversion should be in the business of determining
> > how to build libraries. IMO, that should be APR's job. Our build
> > system gets tremendously simplified in the process and I feel that's a
> > *huge* win. -- justin
> A win for you, but you don't use libtool. It's a loss for me.

[resending, this time to the current dev@ address instead of tigris]

This change has caused an issue that I've marked as a 1.7.0 blocker:
"build system assumes that APR libtool supports C++"

Any ideas on how to resolve this?
I think this is quite release critical because it means we don't
compile on some platforms anymore where 1.6.x used to compile fine.

I am currently testing if a backout of r876227 will help.
Received on 2011-06-17 13:09:25 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.