Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 654386

Summary: net-proxy/haproxy-1.8.8 cross compile fails: No ABI matched, error: ‘_Float128’ is not supported on this target
Product: Gentoo Linux Reporter: Joe Harvell <landshark>
Component: Current packagesAssignee: Christian Ruppert (idl0r) <idl0r>
Status: RESOLVED TEST-REQUEST    
Severity: normal CC: hydrapolic
Priority: Normal Keywords: PATCH
Version: unspecified   
Hardware: ARM   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: output of sudo armv7a-pip-linux-gnueabi-emerge --info
contents of /usr/armv7a-pip-linux-gnueabi/etc/portage/make.conf
build.log
patched ebuild

Description Joe Harvell 2018-04-30 04:01:19 UTC
Cross compile fails because -I/usr/include is added to CFLAGS, which makes the wrong headers included (build machine versus host machine).

This is caused when the USE flag pcre is enabled, causing PCRE=1 to be passed to the make command line.  When PCRE=1, the Makefile adds -I$(PCREDIR)/usr/include to CFLAGS.  But the ebuild does not define PCREDIR, so -I/usr/include is the result.

I patched the ebuild to fix this as follows:

when USE contains pcre, add both of the following as arguments to make:

PCRE=1
PCREDIR=${EROOT}

The end result when cross-compiling is -I${SYSROOT}/usr/include, and everything compiles fine.
Comment 1 Joe Harvell 2018-04-30 04:01:51 UTC
Created attachment 528980 [details]
output of sudo armv7a-pip-linux-gnueabi-emerge --info
Comment 2 Joe Harvell 2018-04-30 04:02:29 UTC
Created attachment 528982 [details]
contents of /usr/armv7a-pip-linux-gnueabi/etc/portage/make.conf
Comment 3 Joe Harvell 2018-04-30 04:02:50 UTC
Created attachment 528984 [details]
build.log
Comment 4 Joe Harvell 2018-04-30 04:03:13 UTC
Created attachment 528986 [details, diff]
patched ebuild
Comment 5 Christian Ruppert (idl0r) gentoo-dev 2022-05-19 20:05:39 UTC
Hey Joe,

is this still an issue with a recent HAProxy version?
Comment 6 Joe Harvell 2022-05-23 19:39:07 UTC
(In reply to Christian Ruppert (idl0r) from comment #5)
> Hey Joe,
> 
> is this still an issue with a recent HAProxy version?

Sorry, I'm no longer using HAProxy and am no longer willing to dedicate any time to this issue.