I am building funtoo root images for a different target architecture than the build system and wondering if that is causing some packages to fail to run.
I do that to hopefully ensure that gcc won't build for my system which is an i7 and the target systems are a 64-bit Intel Atom and a 64-bit AMD netbook processor. However, I still am unable to run a select few applications as I get invalid opcode during execution (they do run just fine on the system on which I built them).
Am I missing a step to build for a different target architecture? I don't believe distcc is required here, but all I really want to do is tell gcc not to use march=native which it prefers to do by default.
Question
walterw
I am building funtoo root images for a different target architecture than the build system and wondering if that is causing some packages to fail to run.
I am starting with a generic subarch: https://www.funtoo.org/Generic_64
And, I modify /etc/make.conf to:
CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=x86-64 -O2 -pipe"
CXXFLAGS="-march=x86-64 -O2 -pipe"
CPU_FLAGS_X86="mmx mmxext sse sse2"
I do that to hopefully ensure that gcc won't build for my system which is an i7 and the target systems are a 64-bit Intel Atom and a 64-bit AMD netbook processor. However, I still am unable to run a select few applications as I get invalid opcode during execution (they do run just fine on the system on which I built them).
Am I missing a step to build for a different target architecture? I don't believe distcc is required here, but all I really want to do is tell gcc not to use march=native which it prefers to do by default.
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now