even the combinations of some of them... same result
--build should not be set to PPC but to whatever system you are building on.
But you see that ./configure works out build for itself in the first couple of lines.
Quote:
checking build system type... x86_64-pc-linux-gnu checking host system type... powerpc-unknown-amigaos
Make sure you know ehere the ppc-amigaos-* tools are and that you can execute them and build simple helloworld (transfer that to an amigaos machine to very it works).
As broadblues said, your configure script isn't finding the cross-compiler. Did you add the following to your ~/.bashrc: export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools/bin
(You probably want to use "nano ~/.bashrc" to add that export command to the end of your bashrc file so every boot/new shell will keep the path for you.)
If you don't do that, then you'll have to update the PATH to find your cross-compiler every time you restart your machine.
Well that rather long and nasty pathname is in your PATH so not sure why configure can't see it.
Have you verified that you can compile a simple helloworld.c ? It could be that some dependency of ppc-amigaos-gcc is missing (ld as etc) and so it's failing rather than not being found.
"Oh come on, please try a little harder on your own behalf, can you not see this near the top?"
"hat obviously doesn't include the cross compiler elements. I'm not sure why that should be though. "
Well, thank you.
The first installation worked. I even captured screenshots of all the steps, carefully observing all the procedure. Of course this is not related to SDL2, to --host, --build or --target.
Could you try what broadblues suggests? Or, at least execute echo $PATH Something's clearly weird about your setup, because you can execute ppc-amigaos-gcc, but the configure script clearly isn't finding it.
The configure script isn't even listing the directory ppc-amigaos-gcc is in as part of the path. It should be listing /usr/local/amiga/adtools/bin as part of the PATH, but it's not.
EDIT: Thinking a bit further, did you add "export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools/bin" to /etc/profile? Or to ~/.bashrc?
Eg I have both 'bash' and 'dash' installed on my looonix laptop with 'bash' being the one in use by the console and 'dash' being what 'sh' is linked to. Never having run cross compiler on that machine I don't know if that might make any difference
Try doing a
ls -l /bin/*sh
to see what shells might be present and which linked
See if
sh -c "echo $PATH"
differe from plain
echo $PATH
aslo
echo $0
will tell you which shell is running in your console (or if added to script which ran the script)
you could also try
sh ./configure
Quote:
This is my 16th or more installation.
What do you mean by that? 16th run of configure? You don't need to reinstall the SDL2 stuff just run
No, 16th time reinstalled the entire UWin, repeating all the steps of the instructions to ensure that i've followed carefully the instruction. I even captured the images during the installation (39 images) and created an install script (posted in the previous post), script that i don't use cause i want to follow step by step the installation.
Only one shell is installed.
Edited by AmigaBlitter on 2017/11/20 14:13:23 Edited by AmigaBlitter on 2017/11/20 14:14:25
Note the spaces in the middle. It's highly likely that the configure script gets confused by that. A space in my home path caused trouble when I was building the cross-compiler...
Try moving the Skype entry in your ENV/PATH to the end, so your cross-compiler's paths appear first. Or, try removing the Skype phone entry altogether.
Slightly different thoughts....try any or all of them.
1) It may be that you've got a dead/missing symlink in your /usr/local/amiga directory. As in, you might be missing the "/usr/local/amiga/adtools" symlink that some things rely upon in the build instructions. Start with confirming/creating the symlink. If it's not there, "sudo ln -s /usr/local/amiga/adtools-ppc-uwin64-20170623-404 /usr/local/amiga/adtools"
2) I've still not tried to do the compilation of the SDL toolkit, but I wonder aloud what might happen if you replace just the UWin gcc executable in its normal /usr/bin/gcc location with a symlink from:
I created the symlink after creating the two directories:
/usr/local/amiga /usr/local/amiga/adtools
and after "chowning" both for my user. Only after this i can create the symlink without an error. Then i set the export path, by executing it and by inserting it into bashrc file.
You should only have to create /usr/local/amiga, and not any adtools directory inside that. Then, a directory symlink called "adtools" can be made there pointing to the original location.