On Sun, Aug 04, 2019 at 08:10:27PM +0100, Stuart Henderson wrote:
> On 2019/08/04 21:55, Timo Myyrä wrote:
> > Stuart Henderson <s...@spacehopper.org> writes:
> >
> > > On 2019/08/04 08:34, Timo Myyrä wrote:
> > >
> > >> Stuart Henderson <s...@spacehopper.org> writes:
> > >>
> > >> > On 2019/08/03 14:36, Timo Myyrä wrote:
> > >> >
> > >> >> Stuart Henderson <s...@spacehopper.org> writes:
> > >> >>
> > >> >> > I'm seeing gerbil build failing in "Build gerbil tags" on i386. Any
> > >> >> > ideas?
> > >> >> >
> > >> >> > $ [...] ./build.sh tags
> > >> >> > <
> > >> >> > [*] Build gerbil tags
> > >> >> > TAG gerbil/compiler/base.ss
> > >> >> > TAG gerbil/compiler/compile.ss
> > >> >> > TAG gerbil/compiler/driver.ss
> > >> >> > TAG gerbil/compiler/optimize-ann.ss
> > >> >> > TAG gerbil/compiler/optimize-base.ss
> > >> >> > TAG gerbil/compiler/optimize-call.ss
> > >> >> > TAG gerbil/compiler/optimize-top.ss
> > >> >> > TAG gerbil/compiler/optimize-xform.ss
> > >> >> > TAG gerbil/compiler/optimize.ss
> > >> >> > TAG gerbil/compiler/ssxi.ss
> > >> >> > TAG gerbil/compiler.ss
> > >> >> > *** ERROR -- (Argument 2) Out of range
> > >> >> > (vector-ref
> > >> >> > #(";;; -*- Gerbil -*-" ";;; (C) vyzo at hackzen.org" ";;; gerbil
> > >> >> > -> gambc compiler" "package: gerbil" "namespace:...
> > >> >> > 28)
> > >> >> > *** ERROR; build failed
> > >> >> >
> > >> >> >
> > >> >> > I'm building on new hardware, but other ports are all building ok.
> > >> >> >
> > >> >> > This is repeatable (either rerunning ./build.sh tags or making a
> > >> >> > whole clean
> > >> >> > build from ports).
> > >> >> >
> > >> >> > Any ideas?
> > >> >>
> > >> >> I just tested Gerbil port on new i386 vm host and it did build
> > >> >> successfully.
> > >> >> I didn't do anything special, "pkg_add git gambit libxml sqlite3 && cd
> > >> >> /usr/ports/lang/gerbil && make".
> > >> >>
> > >> >> Did you use proot / dbp or anything else which could affect the build
> > >> >> result?
> > >> >>
> > >> >> timo
> > >> >>
> > >> >
> > >> > My build setup on this machine is similar to the ones I was previously
> > >> > using which worked ok (slight differences in paths but that shouldn't
> > >> > affect
> > >> > anything in a ports build). No proot, I normally use dpb, but get the
> > >> > same
> > >> > results with a manual "make".
> > >> >
> > >> > Looks similar to (same as?) this problem which aja@ ran into, but I
> > >> > don't
> > >> > know what happened with that ..
> > >> > https://marc.info/?l=openbsd-ports-cvs&m=154340876315118&w=2
> > >>
> > >> I don't remember if there was any solution to that.
> > >> As Gerbil uses Gambit scheme as a backend, could the compilation flags
> > >> of that
> > >> affect the Gerbil build?
> > >> Did you build the Gambit package yourself or did you use package?
> > >
> > > This is on the machine that builds snapshot packages. So I suppose
> > > the answer is 'both' :-)
> > >
> > > It is a clean build with no non-default flags that would affect
> > > compilation.
> > >
> > >> Reading Gambit's INSTALL.txt:
> > >> "Note that some C compilers generate incorrect code when
> > >> compiling Gambit with --enable-c-opt, notably GCC 4.6.0 . So the
> > >> --enable-c-opt option should be used with great care."
> > >>
> > >> Most of the Gambit documentation seems to recommend to use GCC when
> > >> compiling
> > >> it so I don't know if LLVM gives some issue with it.
> > >>
> > >> Could you test what your gxi is gives when executing:
> > >> $ cat <<EOF > /tmp/test.ss
> > >>
> > >> > (import :std/misc/ports)
> > >> > (for-each (lambda (l)
> > >> > (display l) (newline))
> > >> > (read-file-lines
> > >> > "/usr/ports/pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss"))
> > >> > EOF
> > >>
> > >> /usr/ports/pobj/gerbil-0.15.1/gerbil-0.15.1/bin/gxi /tmp/test.ss
> > >>
> > >> Timo
> > >>
> > >>
> > >
> > > sthen@i386-2[/tmp] cat test.ss
> > > (import :std/misc/ports)
> > > (for-each (lambda (l)
> > > (display l) (newline))
> > > (read-file-lines
> > > "/pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss"))
> > > sthen@i386-2[/tmp] /pobj/gerbil-0.15.1/gerbil-0.15.1/bin/gxi test.ss
> > > ;;; -*- Gerbil -*-
> > > ;;; (C) vyzo at hackzen.org
> > > ;;; gerbil -> gambc compiler
> > > package: gerbil
> > > namespace: gxc
> > >
> > > (import :gerbil/compiler/driver)
> > > (export (import: :gerbil/compiler/driver))
> >
> > Seems ok that one, what does running the gxtags manually give:
> > /pobj/gerbil-0.15.1/gerbil-0.15.1/bin/gxtags -o /tmp/TEST-TAG
> > /pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss
> >
> > if the problem is limited into gxtags for some reason?
> >
> > timo
> >
>
> $ doas -u _pbuild /pobj/gerbil-0.15.1/gerbil-0.15.1/bin/gxtags -o
> /tmp/TEST-TAG /pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss
> *** ERROR IN _gx#load-runtime! -- Cannot determine GERBIL_HOME
>
> $ doas -u _pbuild env GERBIL_HOME=/pobj/gerbil-0.15.1/gerbil-0.15.1
> /pobj/gerbil-0.15.1/gerbil-0.15.1/bin/gxtags -o /tmp/TEST-TAG
> /pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss
> TAG /pobj/gerbil-0.15.1/gerbil-0.15.1/src/gerbil/compiler.ss
> *** ERROR -- (Argument 2) Out of range
> (vector-ref #(";;; -*- Gerbil -*-" ";;; (C) vyzo at hackzen.org" ";;; gerbil
> -> gambc compiler" "package: gerbil" "namespace: gxc" "" "(import
> :gerbil/compiler/driver)" "(export (import: :gerbil/compiler/driver))") 28)
I don't want to hijack this thread, but I just wanted to say that there are many
wolves hiding.
That gerbil port has *never* built successfully for me on exopi (amd64) since
its first import.
cc -O2 -pipe -Wno-unused -Wno-write-strings -Wdisabled-optimization
-fwrapv -fno-strict-aliasing -fno-math-errno -fomit-frame-pointer -fPIC
-fno-common -rdynamic -I"/usr/local/include/gambit" -o "gxpkg" gxpkg_.o
gxpkg.o "/usr/local/lib/gambit/libgambit.a" -lutil -lm
-L/usr/local/opt/openssl/lib -lssl -lcrypto
[*] Build gerbil tags
*** ERROR; build failed
And thank you gerbil for the useless output...
--
Antoine
