Bug 218483 - java/openjdk8 does not build in poudriere
Summary: java/openjdk8 does not build in poudriere
Status: Closed DUPLICATE of bug 217846
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: freebsd-java (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-08 12:48 UTC by Thomas Zander
Modified: 2017-04-10 05:13 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Zander freebsd_committer freebsd_triage 2017-04-08 12:48:01 UTC
With up to date ports tree and packages, this happens:

...
===========================================================================
=======================<phase: configure      >============================
===>  Configuring for openjdk8-8.121.13
Warning: You are using legacy autoconf cross-compilation flags.
It is recommended that you use --openjdk-target instead.

Running generated-configure.sh
./../../common/autoconf/generated-configure.sh: redirection error: cannot duplicate fd: Bad file descriptor
./../../common/autoconf/generated-configure.sh: line 560: 0: Bad file descriptor
configure exiting with result code 1
===>  Script "../../configure" failed unexpectedly.
Please report the problem to java@FreeBSD.org [maintainer] and attach the
"/wrkdirs/usr/ports/java/openjdk8/work/openjdk/common/autoconf/config.log"
including the output of the failure of your make command. Also, it might be
a good idea to provide an overview of all packages installed on your system
(e.g. a /usr/local/sbin/pkg-static info -g -Ea).
*** Error code 1

Stop.
make: stopped in /usr/ports/java/openjdk8
Comment 1 Walter Schwarzenfeld 2017-04-08 22:03:14 UTC
Maybe it is the same as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217846
Comment 2 Thomas Zander freebsd_committer freebsd_triage 2017-04-09 05:31:01 UTC
(In reply to w.schwarzenfeld from comment #1)

Possibly, thanks for the hint!
I'll rebuild world and all my ports and in about 40 hours we probably know more :-)
Comment 3 Thomas Zander freebsd_committer freebsd_triage 2017-04-10 05:13:25 UTC
It seems this was the problem. Updating world to a recent revision resolves the issue. Thanks!

*** This bug has been marked as a duplicate of bug 217846 ***