#1
  1. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Oct 2006
    Posts
    27
    Rep Power
    0

    Issue with java install for jdk 1.5


    Morning.

    Going through setting up a system and have ran into a brick wall. When trying to install the 1.5 java jdk on my server for the upcoming install of jboss, it comes up with this error message out of the blue.

    ===> Script "configure" failed unexpectedly.
    Please report the problem to x11@FreeBSD.org [maintainer] and attach the
    "/usr/ports/x11/libXi/work/libXi-1.2.1/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. an `ls
    /var/db/pkg`).
    *** Error code 1

    Stop in /usr/ports/x11/libXi.
    *** Error code 1

    Stop in /usr/ports/java/diablo-jdk15.
    *** Error code 1

    Stop in /usr/ports/java/diablo-jdk15.

    as you can tell it's a freebsd server that I am using, version 6.3. Have also tried the java/jdk15 port but it asks to go to the java website, which has no BSD port available for download. Java has never been installed on this machine. Hopefully you folks might have ran into something like this before?
  2. #2
  3. No Profile Picture
    Contributing User
    Devshed Newbie (0 - 499 posts)

    Join Date
    May 2004
    Posts
    152
    Rep Power
    39
    It would be helpful to see a screenful of output above what you have posted. The problem seems to be with libXi so you could try upgrading that port before you install java.

    To see what version libXi is installed, run:
    Code:
    # pkg_info | grep libXi
    If you haven't already, install portupgrade:
    (but use portsnap to update your ports tree! much easier than CVS IMO)
    http://www.math.colostate.edu/~reinholz/freebsd/ports.html

    http://www.math.colostate.edu/~reinholz/freebsd/portupgrade.html
  4. #3
  5. No Profile Picture
    Registered User
    Devshed Newbie (0 - 499 posts)

    Join Date
    Oct 2006
    Posts
    27
    Rep Power
    0
    no worries found out it was an old version of inputproto that was gumming up the works (I didn't have libXi installed.)

IMN logo majestic logo threadwatch logo seochat tools logo