Apologies, all, for being silent for a few weeks. This is an insanely busy time for me in all my businesses. None are retail/X-mas affected, per-se!

I'll readily / happily edit my instructions if an inadvertent/unnecessary "sudo" needs to be corrected somewhere.

Can someone let me know if/what changes I may need to make to the original post?

@stonecracker


post #1 from stonecracker:

export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools/bin

DStastny @ post #6

export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools-ppc-uwin-20170623-404/bin
(which in my case should be: export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools-ppc-uwin64-20170623-404/bin)


In my now working installation i have only this in bashrc:

export PATH=$PATH:~/adtools/bin:/usr/local/amiga/adtools-ppc-uwin64-20170623-404/bin

@AmigaBlitter

With the symlink in place, export PATH=$PATH:~/adtools/bin is probably all you need. Although there's that rare occasion when a configure script can't find something in /SDK/local/newlib/bin even when you use --prefix, so that can be added too.

I _think_ the culprit was an unnecessary "sudo" or maybe a missing chown/chgrp command somewhere that caused some of the simple but irritating permissions problems?

This problem doesn't show up on Cygwin, as Cygwin doesn't have sudo or root users.

But UWin, it would/could be a problem. Can someone point me to where the problem might be in my originating post? I'm quickly reviewing that post, and just don't see where the problem might be...

@stonecracker

Thank you for your tutorial. installed on Cygwin64, all seems fine !

Glad to hear. I _think_ all is working fine with my instructions, as seen in the originating/but heavily edited, original post. UWin, and Cygwin. Unless someone tells me otherwise?

@stonecracker

Hello,

i bring up again this thread cause i had a severe Windows 10 failure and lost my uwin installation.

i tried already to reinstall everything as before, having all the steps done previously written in a document and proceeded carefully with copy and paste to ensure no errors occoured during the setup phase.

Unfortunately, the make commands fails with some errors and i can't complete the installation of the uwin environment.

At first i tought that something changed in Windows fall creator update and i figured out that only the lxss environment path has been modified as default. I think that this should not have any impact in the cross compiler setup procedure.

I would like to address this problem definitively, so i ask you (again) for help.

Thank you.

@AmigaBlitter

Stonecracker hasn't logged in in a while. So, you might want to explain where you're getting stuck here. Maybe others can help.

Hans

It looks like the instructions in post #1 jump straight into building gcc before building binutils. AmigaBlitter's screenshots he sent to me show it failed when looking for ppc-amigaos-ar in native-build/root-cross/bin/. I had a look at the Makefile in native-build and the gcc-cross target, and I don't see where binutils is made for that target.

So I suggest going into native-build, and running "make binutils-install". Then building gcc should work afterwards. Not tested, but this is my best guess.

Edit: The Makefile from when this thread was first made, used to build binutils for the gcc-cross target, but no longer does. 18 days ago a change was made (893c02b) that meant binutils would no longer be built automatically if using the gcc-cross target. Previously, gcc-cross would call clib2-cross which would call xgcc-done which called binutils-cross.

Edit 2: That wasn't right either. See salass00's post below.

@MickJT

Changing the following two lines in native-build/makefile fixed the problem with wrong path being used for ppc-amigaos-ar for me:



Eventually it failed again because it wasn't able to find clib2 files in $(CROSS_PREFIX)/ppc-amigaos/SDK/clib2 so I copied them there manually from native-build/downloads/clib2/ and ran make again, and it finished without errors building the gcc 6.4.0 cross compiler.

I missed that CLIB2_CROSS_DONE_DEPENDENCY line.

So, the makefile still builds it but doesn't always take into account modified variables.

Thank you all for the informations.

Will try to apply asap.

Making a few more changes to the makefile I was able to build a gcc 8.0.1 cross compiler without any errors.

Ok. I just went through the steps myself. I'm naming the CROSS_PREFIX directory as adtools-ppc-uwin64-20180416-480 (I used make print-dist-version to find the date/revision). After doing all the gild stuff, I went into native-build and ran:

make gcc-cross CROSS_PREFIX=/usr/local/amiga/adtools-ppc-uwin64-20180416-480

When I got to the error, I simply did:

ln -s /usr/local/amiga/adtools-ppc-uwin64-20180416-480 root-cross

So that makes a root-cross symlink inside of native-build that points to /usr/local/amiga/adtools-ppc-uwin64-20180416-480

Then I ran the "make" line again, and it continued on fine. Sorry to say salass00, your method is the hard way, even if it is more "proper" :) I'm sure Sebastian Bauer will fix CROSS_PREFIX to work properly again soon anyway (basically the same as what you did).