You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of the amiga-gcc build/install, I ran into:
% make fd2sfd
configure fd2sfd...
configure fd2sfd...done
make fd2sfd...
make fd2sfd...done
install fd2sfd...
install fd2sfd...failed
make[1]: Entering directory '/export/home/briggs/amiga-gcc/build-SunOS/fd2sfd'
/usr/gnu/bin/install -c -d /opt/amiga/bin /opt/amiga/share/fd2sfd
# Install tools
/usr/gnu/bin/install -c -s fd2sfd /opt/amiga/bin
/usr/gnu/bin/install -c cross/bin/gg-fix-includes /opt/amiga/bin
install: cannot stat 'cross/bin/gg-fix-includes': No such file or directory
make[1]: *** [Makefile:44: install] Error 1
install fd2sfd...failed
use less "log/install fd2sfd.log" to view the full log and search for ***
make: *** [Makefile:486: /opt/amiga/bin/fd2sfd] Error 2
which is from a configure failure:
creating cache ./config.cache
checking host system type... sparc-sun-solaris2.11
checking target system type... m68k-unknown-amigaos
checking build system type... sparc-sun-solaris2.11
checking whether make sets ${MAKE}... yes
checking for gcc... gcc
checking for gcc... (cached) gcc
checking whether the C compiler (gcc -Os ) works... yes
checking whether the C compiler (gcc -Os ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for a BSD compatible install... /usr/gnu/bin/install -c
updating cache ./config.cache
creating ./config.status
creating Makefile
creating fd2sfd.readme
creating gg-fd2sfd.spec
mkdir: cannot create directory 'cross/bin': No such file or directory
creating cross/bin/gg-fix-includes
./config.status: line 170: cross/bin/gg-fix-includes: cannot create [No such file or directory]
As part of the amiga-gcc build/install, I ran into:
which is from a configure failure:
which is probably from (thanks @bebbo):
which should be
(see bebbo/amiga-gcc#258)
The text was updated successfully, but these errors were encountered: