Build failure for java/icedtea-web (stable/8 @r223930)
avg at FreeBSD.org
Tue Jul 12 14:20:14 UTC 2011
on 12/07/2011 16:56 David Wolfskill said the following:
> On Tue, Jul 12, 2011 at 03:50:55PM +0300, Andriy Gapon wrote:
>> Have you payed attention to the notice at the start of java/icedtea-web build?
>> You can easily reproduce it by doing make clean ; make.
> The message that says:
> | IMPORTANT: To build IcedTea-Web 1.1, you have to turn on 'ICEDTEA' option
> | for java/openjdk6 (default). Otherwise, it will neither build nor work.
> ? Yes; I had just finished upgrading openjdk6-b22_6 to openjdk6-b23.
To me your issue looked like ICEDTEA option is not turned on.
> I admit that I did not even see the notice about procfs & fdescfs
> until after the failure. And that I did not re-attempt the port
> build.install after taking the specified action.
> I did, however, verify that fdescfs had already been mounted (before the
> attempt), and I updated /etc/fstab to include the procfs mount.
> Now that I have since re-booted (as I had booted from a different slice
> in order to build a snapshot of head (9.0-CURRENT)), and procfs is
> already mounted:
> g1-222(8.2-S) mount
> /dev/ada0s1a on / (ufs, local)
> devfs on /dev (devfs, local, multilabel)
> tmpfs on /tmp (tmpfs, local)
> /dev/ada0s1d on /usr (ufs, local)
> /dev/ada0s2a on /S2 (ufs, local, soft-updates)
> /dev/ada0s2d on /S2/usr (ufs, local, soft-updates)
> /dev/ada0s3a on /S3 (ufs, local)
> /dev/ada0s3d on /S3/usr (ufs, local)
> /dev/ada0s4a on /S4 (ufs, local)
> /dev/ada0s4d on /S4/usr (ufs, local)
> /dev/ada0s4e on /var (ufs, local)
> /dev/ada0s4f on /repo (ufs, local)
> /dev/ada0s4g on /common (ufs, local)
> /dev/ada0s4h on /bkp (ufs, local)
> fdescfs on /dev/fd (fdescfs)
> procfs on /proc (procfs, local)
> I re-tried the "make clean install clean"; the results appear (to me) to be
> the same, and the config.log is the same in each case (same md5
> The salient whine appears to be "configure: error:
> sun.applet.AppletViewerPanel is not public." I don't even pretend to be
> a Java programmer, so I don't have a clue what sort of evasive actions
> are available to me, let alone what might be helpful.
Posting a link config.log is usually a good idea in general when configure step
fails. Maybe there would be something useful in it in this case too.
More information about the freebsd-java