On Tue, Sep 16, 2008 at 9:34 AM, Stefan Sperling <stsp_at_elego.de> wrote:
> On Tue, Sep 16, 2008 at 08:41:11AM -0700, David James wrote:
>> On Tue, Sep 16, 2008 at 6:40 AM, Stefan Sperling <stsp_at_elego.de> wrote:
>> > On Wed, Aug 20, 2008 at 09:50:14PM +0200, Stefan Sperling wrote:
>> >> Hi,
>> >>
>> >> I am in the process of putting together a proper Subversion-1.5.1
>> >> port for OpenBSD. Their current port is still at 1.4.4.
>> >>
>> >> I got most things working, except for the binding regression tests.
>> >> I haven't tried javahl yet (planning to tackle that at some later time),
>> >> but for all the swig-based bindings, the regression tests just flat
>> >> out fail.
>> >
>> > For the record, Brad Walker managed to fix the problems by
>> > regenerating all SWIG-generated files with swig-1.3.36:
>> > http://marc.info/?l=openbsd-ports&m=122157221716865&w=2
>> >
>> > Why do we ship generated files in releases that don't work
>> > on all platforms? Are files generated by SWIG even supposed
>> > to work on all platforms?
>> >
>> > Stefan
>>
>> Hi Stefan,
>>
>> The pregenerated SWIG files shipped with Subversion are supposed to
>> work on all platforms, but there may of course be bugs. Can you post a
>> log of what commands you typed during your build? Start with the tar
>> command that extracts from the tarball, and let me know whether or not
>> you ran "autogen.sh".
>
> Well, the commands are all issued by OpenBSD's ports system.
> There might be some way of getting it to display the commands
> it's running, but either way I don't expect this would help
> us much. It seems to be a deeper problem in swig -- e.g. earlier
> versions than 1.3.36 also results in regression test failures
> in the bindings, even when regenerating everything.
> See Brad's post: http://marc.info/?l=openbsd-ports&m=122157221716865&w=2
Ah, thanks. In that case, I think we should use Swig 1.3.36 for future
releases of Subversion (say, Subversion 1.6) so that the build will
work on OpenBSD. Before we do this, we should test on all platforms,
of course.
Once we're sure that SWIG 1.3.36 works great on all platforms, we
might add a check to dist.sh to make sure the packager has the right
version of SWIG. This will ensure that the packager does not forget to
upgrade SWIG.
(As for your patches, I haven't looked at them in detail -- but if
they build on all platforms including OpenBSD, then I think they
should be committed.)
Cheers,
David
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-09-16 21:02:39 CEST