I'm feeling embaressed posting this however I'm in a bind.

when I try to build gcc using the Pat's build script I get:
configure: error: in `/usr/ports/tmp/build/gcc-build':
configure: error: C compiler cannot create executables

I have all disksets installed of current except e, f, kde, t, xap and xfce. Current is is recent as Tue Oct 19 01:10:06 UTC 2021

I did build and install some 3rd party software: gnucash, vlc, trinity amongst others, so gcc works!

I then tried to build ffmpeg and failed. Got error:
'g++: no such file'.

I reinstalled the gcc-g++ package which fixed this error.

Then on a whim i decided to build gcc package using Pat's SlackBuild script. This fails with the above error. I'm sure nothing wrong with Slackware or Pat's script but what may I have screwed up? Where should I start looking to solve this?

BTW: I have reinstalled all of 'd' diskset as I thought binutils may have been hosed somehow by my custom build scripts for 3rd party software.
TIA

This indicates to me that your system is not clean. Did you ever install multilib? Unfortunately there's no telling what all is wrong with your system.

You may need the 't' set or something from it. I've argued about reducing packages before, but utilities you trake for granted are often packaged as part of a package you "obviously don't want." Nslookup being part of bind is one example that springs to mind.

Try it again,and trap the error. I presume it's in the configure stage, processing the Makefile. IIRC, it tries to make a tiny a.out program with a few lines of the Makefile; just run it line by line in a console until you find the issue.

Yes I did install multilib, but then removed it. This is a test machine so I have made my own build scripts for trinity. My latest changes to these scripts hosed the filesystem...just saw where it happens. I have ended up with /usr/bin/lib64, and /opt/lib64 and then even /usr/lib64/lib64

Some trinity variables to blame.
Thank you so much for your help though.
I can't see how to mark this as solved / is there a button somewhere?

1 members found this post helpful.

okI saw how to close this