It works for me now but I do remember it used to use the the wrong libs.

Round up your *.la files in /usr/lib on the host and move them to /usr/lib/la.files say, in case you regret it.
You shouldn't, since they no longer need to be installed.

Yikes! Is that really necessary?

NeddySeagoon wrote:

Read one or two ... notice the last line. Its an absolute path to a location on the host.
Thats a very bad thing since the cross environment can't fix it.

You talking about the make[1] and make[2] lines?

NeddySeagoon wrote:

On the Pi you should have an option in make.conf to not install *.la files.

I haven't even gotten that far yet, I'm trying to compile the GCC binary for the Pi, it just requires gettext for the build._________________"It's ok, they might have guns but we have flowers." - Perpetual Victim

# Should we warn about portability when linking against -modules?
shouldnotlink=no

# Files to dlopen/dlpreopen
dlopen=''
dlpreopen=''

# Directory that this library needs to be installed in:
libdir='/usr/lib64'

Notice the pathname. I've moved all my *.la files out of the way so they cannot be found.
Now look at the very last line

Code:

libdir='/usr/lib64'

You really don't want to try using its contents when you are building for ARM.
You can go through all the *.la files removing that if you like but its faster to move them all. I can't say I've regretted it._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

Forgive the ignorance, but what is a good API for pastebin? I emerged pastebin and the API apparently isn't supported anymore._________________"It's ok, they might have guns but we have flowers." - Perpetual Victim

My crossdev is seriously broken just now. It lives on a 4 spindle kernel raid5 set. One partition dropped out and everything kept going in degraded mode.
Unfortunately, when it was resyncing after being added back another drive was kicked out of the set, leaving a raid5 set with two drives missing. That's a very bad thing.

I need to replace at least one drive to get things going again. That's going to take a few days._________________Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

My raid is fixed. I had three drives with the same event count but one had 58 unrecoverable read errors. Which I didn't spot until another drive got kicked out of the array and the sync failed.
I suspect that those blocks were in unused space, or I would have noticed something nasty in dmesg.
I was lucky, they were all in /usr, so nothing priceless lost.

I took the decision a long time ago to only backup /home and live with the possibility of needing to reinstall the system. Looking back, that might have been faster than imaging the dead drive.
I'm catching up with email and other stuff in the week where I have had limited use of the internet.

!!! /usr/armv6j-hardfloat-linux-gnueabi/etc/make.profile is not a symlink and will probably prevent most merges.
!!! It should point into a profile within /usr/portage/profiles/
!!! (You can safely ignore this message when syncing. It's harmless.)