Closed yurivict closed 4 years ago
How can I reproduce this? I have a Freebsd 12.2-RC2 VM here now. I tried both:
sh autogen.sh
because bash wasn't available) - no error message eitherI saw that the code doesn't build though, so besides configure there there are further portability issues to fix before it will build on FreeBSD.
To reproduce:
Ok, I can reproduce this, but I don't fully understand what the problem is. It seems to be all about the toplevel Makefile.am. My Makefile.am from git contains
SUBDIRS = lib tests
if COND_WITH_JACK
SUBDIRS += src
endif
if COND_WITH_LV2
SUBDIRS += lv2
endif
[...]
Now the work/liquidsfz-0.2.1 contains this Makefile.am under the name Makefile.am.orig. But the new Makefile.am is now:
SUBDIRS = lib tests
if COND_WITH_JACK
SUBDIRS += src
endif
if COND_WITH_LV2
SUBDIRS += lv2
SUBDIRS = lib src lv2
[...]
This doesn't work (note the missing endif), and this is not the Makefile.am I provided (which works if you call autogen.sh on a git checkout from my github repo). All that ports packaging via Makefile is nice, but there must be a magic step somewhere that I don't see that replaces my Makefile.am with a broken one.
Thanks for your troubleshooting. This is a patch
failure https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250511
The patch files/patch-Makefile.am needs to be removed or regenerated.
Now it fails like this:
libtool: error: CURRENT '' must be a nonnegative integer
libtool: error: ':0.2.1:0' is not valid version information
It seems that the sed
expression I used for splitting "0.2.1" into 0, 2 and 1 didn't work with FreeBSD sed. I've replaced this with cut
which works on FreeBSD and Linux. https://github.com/swesterfeld/liquidsfz/commit/18e59d6784f32e4d9c25c0f8ccbc9e7d9cd4c865
I also added the
It builds now. Thank you!
FreeBSD 12.2 autoconf-2.69_3 autoconf-wrapper-20131203 automake-1.16.2