Bug 247817

Summary: lang/ruby26 and lang/ruby27: fails to build with poudriere when unavailable
Product: Ports & Packages Reporter: bugs.freebsd
Component: Individual Port(s)Assignee: freebsd-ports-bugs (Nobody) <ports-bugs>
Status: New ---    
Severity: Affects Some People CC: andrew, meta
Priority: --- Flags: bugzilla: maintainer-feedback? (ruby)
Version: Latest   
Hardware: Any   
OS: Any   
Description Flags
Logfile of a failed build with poudriere. none

Description bugs.freebsd 2020-07-07 04:25:38 UTC
Created attachment 216274 [details]
Logfile of a failed build with poudriere.

Both lang/ruby26 and lang/ruby27 fail to build with a jailed poudriere where the loopback interface has an address other than "".

How to reproduce:
* On a FreeBSD 11.3 system, create a jail with a non-standard address on the loopback interface (such as
* Install poudriere inside the jail.
* Build ruby26 using poudriere. The build-jails created by poudriere should also use some IP other than

With this setup, Ruby fails to build succesfully with "poudriere bulk -j default -p default lang/ruby26". See the attached logfile for details of a recent attempt.

When poudriere is run in 'interactive' mode with "poudriere bulk -j default -p default -i lang/ruby26", it is possible to simply compile the port by running "make" inside the build-jail. Manually building the port inside a jail (even without a loopback address) also works. It only seems to fail whenever poudriere is used to perform the build.

Expected cause:
The "configuring socket" stage of the build compiles and runs a test program with getaddrinfo. At this point, a check is made if "" exists (which isn't the case).
Such hardcoded loopback addresses are used in "ext/socket/extconf.rb":
    if (strcmp(straddr, "") != 0) {
      goto bad;

If I understand correctly, this results in the build script trying to compile its own version of getaddrinfo (instead of using the one provided by the OS), which ultimately fails due to a conflicting function name (see the log).

Credits to RhodiumToad on freenode, who helped diagnosing the problem and pointing out the likely culprit.
Comment 1 Koichiro Iwao freebsd_committer 2021-04-08 02:46:16 UTC
No time to dig into this issue.