Re: Bigloo 4.2a build problems

Jerry James <[email protected]>
Newsgroups gmane.lisp.scheme.bigloo
Message-ID <CAHCOHQmOOx=yw-htZ4v8OkQ5wHfm1FX4Tjji7yDRA4=eD5KdJg@mail.gmail.com>
Sorry, Manuel, got very busy at work....

On Wed, Oct 7, 2015 at 3:21 AM,  <[email protected]> wrote:
> I have fixed (I hope) the linking problem you are mentioning. I'm not
> able to reproduce the failures you have observed with multi-threading.
> I'm strongly suspect an installation problem. My guess is that the GC
> library is incorrectly linked.
>
> I will upload a new version by the end of the day (or tomorrow morning,
> Paris time). Would you be kind to check that forthcoming version? Thanks
> in advance.

The new version looks good, thank you.  The test failure I mentioned
was, in fact, due to a mistake I made in the RPM spec file, now fixed.

The build now looks good for inclusion in Fedora.  However, I have to
rebuild any dependent packages, and the hop 2.5.1 build doesn't work
with bigloo 4.2a.  For one thing, the hop Makefile invokes
shared-link-lib, which was commented out in bigloo 4.2a.  After
working around that, the build runs for awhile but ultimately fails:

File "read.scm", line 260, character 8295:
# (input-port-name input-port)
#                 ^
*** ERROR:<anonymous:5676>
Unbound variable -- input-port

File "read.scm", line 261, character 8331:
# (input-port-position input-port))))))))
#                     ^
*** ERROR:<anonymous:5676>
Unbound variable -- input-port

File "read.scm", line 248, character 7982:
# (read-multi-line-comment input-port)
#                         ^
*** ERROR:<anonymous:5676>
Unbound variable -- input-port
3 errors occured, ending ...
../etc/Makefile.library:35: recipe for target 'o/read.o' failed
make[1]: Leaving directory '/builddir/build/BUILD/hop-2.5.1/runtime'
make[1]: *** [o/read.o] Error 255
make: *** [lib] Error 2
Makefile:63: recipe for target 'lib' failed

Is a version of hop that can be built with bigloo 4.2a in the works?  Thank you,
-- 
Jerry James
http://www.jamezone.org/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.