New answers tagged gcc
killall: hello\ fuser.o gcc -c -o libsignals.a signals.c gcc -o hello killall.o -L/usr/lib/ -L. -lsignals gcc -c killall.c -DHAVE_CONFIG_H -I. fuser: hello\ pstree.o gcc -c fuser.c -DHAVE_CONFIG_H -I. gcc -c -o libsignals.a signals.c gcc -o hello\ fuser.o -L/usr/lib/ -L. -lsignals pstree: gcc -c pstree.c -DHAVE_CONFIG_H -I. ...
Try this in your /etc/mk.conf, it usually works for me: GCCBASE=/usr/pkg/gcc49
Have you tried setting the GCC_REQD variable in /etc/mk.conf? See the documentation here: 5.4. Selecting and configuring the compiler
You may try Scientific Linux 5.9, which has the advantage of being heavily tested among big academic communities of users (notably, CERN & Fermilab). If your application is of the scientific category, I suggest you check out this argument. Also, at least once in the past, CentOS did not want to collaborate with downloaded postgresql rpms, while SL worked ...
I had a similar problem on CentOS 6on and fixed it by installing openssl-devel. Run this command as root: yum install openssl-devel
Over the last 10 years I've been running multiple Gentoo systems with 1000+ packages using -O3 -march=native globally and have yet to run into any of these mythical stability issues that -O3 is supposed to have. Benchmarks of CPU intensive applications (like math/science apps) consistently show -O3 to produce faster code, after all it would be pointless if ...
Top 50 recent answers are included