On 01/03/14 03:54, Frank Ch. Eigler wrote:
> ...
> On pcpfans.git, the fche/i686 branch has two commits for this problem.
> The first adds -latomic if it's available (but isn't on Fedora 17 due
> to gcc <= 4.7). The second drops the rpmbuild --target=FOO override.
> Now Makepkgs, manual CFLAGS...=-march=i386 builds all work. I do not
> have <i686 hardware to test the results on. Does anyone?
I have one machine showing the problem ... pulled your two commits and
=== pmmgr ===
g++ -O2 -g -march=i386 -mtune=i686 -fPIC -fno-strict-aliasing -D_GNU_SOURCE
-fstack-protector-all -D_FORTIFY_SOURCE=2 -Wall -O2 -g -DPCP_DEBUG
-DPCP_VERSION=\"3.9.1\" -I./src/include -I./src/include/pcp -fPIC
-fno-strict-aliasing -D_GNU_SOURCE -fstack-protector-all -D_FORTIFY_SOURCE=2
-Wall -O2 -g -DPCP_DEBUG -DPCP_VERSION=\"3.9.1\" -I../src/include
-I../src/include/pcp -fPIC -fno-strict-aliasing -D_GNU_SOURCE
-fstack-protector-all -D_FORTIFY_SOURCE=2 -fPIE -Wall -O2 -g -DPCP_DEBUG
-DPCP_VERSION=\"3.9.1\" -I../../src/include -I../../src/include/pcp -O2 -g
-march=i386 -mtune=i686 -O2 -g -march=i386 -mtune=i686 -c pmmgr.cxx -o pmmgr.o
g++ -O2 -g -march=i386 -mtune=i686 -fPIC -fno-strict-aliasing -D_GNU_SOURCE
-fstack-protector-all -D_FORTIFY_SOURCE=2 -Wall -O2 -g -DPCP_DEBUG
-DPCP_VERSION=\"3.9.1\" -I./src/include -I./src/include/pcp -fPIC
-fno-strict-aliasing -D_GNU_SOURCE -fstack-protector-all -D_FORTIFY_SOURCE=2
-Wall -O2 -g -DPCP_DEBUG -DPCP_VERSION=\"3.9.1\" -I../src/include
-I../src/include/pcp -fPIC -fno-strict-aliasing -D_GNU_SOURCE
-fstack-protector-all -D_FORTIFY_SOURCE=2 -fPIE -Wall -O2 -g -DPCP_DEBUG
-DPCP_VERSION=\"3.9.1\" -I../../src/include -I../../src/include/pcp -O2 -g
-march=i386 -mtune=i686 -o pmmgr -Wall -L../../src/libpcp/src
-L../../src/libpcp_pmda/src -rdynamic -pie -Wl,-z,relro -Wl,-z,now pmmgr.o
-lpcp -lpthread
pmmgr.o: In function `__exchange_and_add':
/usr/lib/gcc/i686-redhat-linux/4.7.2/../../../../include/c++/4.7.2/ext/atomicity.h:48:
undefined reference to `__atomic_fetch_add_4'
I don't know if this is different to last time ... is there anything else from
the failed build that might help diagnose/resolve this?
> (All this is moot as to normal Fedora/EPEL builds, since those use
> neither Makepkgs, nor rpmbuild --target=FOO overrides.)
Well it is kind of relevant for anyone wanting to rebuild PCP from source on
this platform combination.
I am happy to have my option (a) or option (b) discussion from my previous
mail, especially as this would waste less of Frank's time ... 8^)>
|