RE: 1.10.0-alpha1 is up for signing

If you compare this problem to 1.7 or something it wouldn’t be a regression.

MSBuild by default builds all targets in the makefile, if you don’t pass a target via the optional -t argument. In those older versions we always generated targets that depended hard on optional dependencies, so building everything didn’t work… You really had to specify a target like __ALL_TESTS__, to avoid things like the swig code, bdb or cxxhl failing.

Since that problem was fixed some time ago, we now fail on systems that just build everything… while those that still specify a target like our buildbots that were setup to be compatible with those old setups don’t see this problem.

Note that I don’t think the unix makefiles build everything either… so they may have similar problems somewhere.

But +1 on rerolling anyway.

Bert

Sent from Mail for Windows 10

From: Stefan Sperling
Sent: dinsdag 21 februari 2017 11:28
To: Evgeny Kotkov
Cc: Stefan Hett; Subversion Development
Subject: Re: 1.10.0-alpha1 is up for signing

On Tue, Feb 21, 2017 at 01:18:01PM +0300, Evgeny Kotkov wrote:
> Stefan Hett <luke1410_at_posteo.de> writes:
>
> > Trying to build this release triggers the following build error when
> > compiling the svn-mergeinfo-normalizer tool for me:
> >
> > ..\..\..\tools\client-side\svn-mergeinfo-normalizer\wc_mergeinfo.c(376):
> > error C4013: 'svn_hash__sets' undefined; assuming extern returning int
>
> I can confirm that 1.10.0-alpha1 doesn't build on Windows in my environment
> (the svn-mergeinfo-normalizer tool is built by default).
>
> I committed r1783859 and r1783862 in order to fix this issue. Perhaps, we
> should roll alpha2 with these fixes?
>
>
> Regards,
> Evgeny Kotkov

Thanks for fixing this Evgeny!

I agree we should prepare another release and toss alpha1, given that
alpha1 does not compile everywhere. I'll do that today.
Received on 2017-02-21 17:29:54 CET