Go or Rust Packages?

Achim Gratz Stromeko@nexgo.de
Sun Feb 6 11:09:12 GMT 2022

Achim Gratz writes:
> Pulling out this and another stop successfully configures and actually
> builds a gccgo executable sometime later.  If any of this actually works
> remains to be seen.

The compiler itself seems to be working (for some definition of
working), but the compilation of libgo fails at some point:

--8<---------------cut here---------------start------------->8---
make[4]: Entering directory '/mnt/share/packages/gcc/gcc.x86_64/build/x86_64-pc-cygwin/libgo'
/usr/bin/mkdir -p os/signal/internal; files=`echo  | sed -e 's/[^ ]*\.gox//g' -e 's/[^ ]*\.dep//'`; /bin/sh ./libtool --tag GO --mode=compile /mnt/share/packages/gcc/gcc.x86_64/build/./gcc/gccgo -B/mnt/share/packages/gcc/gcc.x86_64/build/./gcc/ -B/usr/x86_64-pc-cygwin/bin/ -B/usr/x86_64-pc-cygwin/lib/ -isystem /usr/x86_64-pc-cygwin/include -isystem /usr/x86_64-pc-cygwin/sys-include   -fchecking=1  -minline-all-stringops  -O2 -g -I . -c -fgo-pkgpath=`echo os/signal/internal/pty.lo | sed -e 's/.lo$//'`  -o os/signal/internal/pty.lo $files
libtool: compile:  /mnt/share/packages/gcc/gcc.x86_64/build/./gcc/gccgo -B/mnt/share/packages/gcc/gcc.x86_64/build/./gcc/ -B/usr/x86_64-pc-cygwin/bin/ -B/usr/x86_64-pc-cygwin/lib/ -isystem /usr/x86_64-pc-cygwin/include -isystem /usr/x86_64-pc-cygwin/sys-include -fchecking=1 -minline-all-stringops -O2 -g -I . -c -fgo-pkgpath=os/signal/internal/pty  -DDLL_EXPORT -o os/signal/internal/.libs/pty.o
gccgo: fatal error: no input files
compilation terminated.
make[4]: *** [Makefile:3001: os/signal/internal/pty.lo] Error 1
--8<---------------cut here---------------end--------------->8---

Since this is in the os subtree my guess is that this happens due to the
non-recognition of Cygwin somewhere else.

+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Blofeld:

More information about the Cygwin-apps mailing list