Bug 208662 - lang/ruby22 fails to build on 9.3-RELEASE-p39
Summary: lang/ruby22 fails to build on 9.3-RELEASE-p39
Status: Closed Not Enough Information
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-ruby (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-10 00:17 UTC by MattS
Modified: 2016-12-05 20:21 UTC (History)
1 user (show)

See Also:
bugzilla: maintainer-feedback? (ruby)


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MattS 2016-04-10 00:17:28 UTC
Port fails to build on 9.3-RELEASE-p39. Also fails with "MAKE_JOBS_UNSAFE=yes". I'm not sure what information to include that may be helpful. Please let me know if there is anything else needed.
--------------------------------------------------------------------
compiling ripper.c
{standard input}: Assembler messages:
{standard input}:17516: Warning: end of file not at end of a line; newline inserted
{standard input}:18641: Error: unknown pseudo-op: `.l35'
cc: Internal error: Killed: 9 (program cc1)
Please submit a full bug report.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
*** [ripper.o] Error code 1
1 error
*** [ext/ripper/all] Error code 2
1 error
*** [build-ext] Error code 2
1 error
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** [do-build] Error code 1

Stop in /usr/ports/lang/ruby22.
*** [install] Error code 1
Comment 1 Steve Wills freebsd_committer freebsd_triage 2016-12-05 20:21:33 UTC
Not able to reproduce this issue and haven't seen another further reports. The packages build fine, see:

http://portsmon.freebsd.org/portoverview.py?category=lang&portname=ruby22

Which shows it building fine on 9.3. So would need a lot more detail, such as details on machine arch, full logs, perhaps even a full copy of the work directory to look at. That said, the signal 9 makes me think it might be a local issue, either hardware or lack of memory. And if the issue is specific to 9.3, I would be surprised, but also 9.3 goes out of support pretty soon.

So given all that, closing until there's more info. Feel free to re-open with details.