Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
gcc-mp-4.8 test.c
otool -L a.out
shows that the executable is linked with /opt/local/lib/gcc48/libgcc_s.1.dylib, and that’s not what I want, because the path won’t exist on a stock Mac OS X system.
How can I use MacPorts-installed GCC 4.8 to build MacPorts-independent executables that would use /usr/lib/libgcc_s.1.dylib instead?
I’ve tried adding -L/usr/lib/ -lgcc_s.1 to arguments, but that doesn’t change anything.
gcc isn’t meant to link against the library from older versions.. You should be able to statically link instead, however.