FRC Plugins Won't Install (Netbeans on Fedora)

[WilliamY]

Now, this isn't an immediate issue, seeing as how I've just been using Windows, but it's still bugging me. When the install.xml runs, I get this error (has been seen over several plugin versions).

/home/team342/sunspotfrcsdk/install.xml:183: The following error occurred while executing this line:
/home/team342/sunspotfrcsdk/lib/WPILibJ/build.xml:43: The following error occurred while executing this line:
/home/team342/sunspotfrcsdk/ant/preverify.xml:54: Execute failed: 
java.io.IOException: Cannot run program "/home/team342/sunspotfrcsdk/bin/preverify" (in directory "/home/team342/sunspotfrcsdk/lib/WPILibJ"): java.io.IOException: error=2, No such file or directory

Those lines it references are

<ant dir="${wpilibjhome}" antfile="build.xml" inheritall="false" target="create-lib"/>

<antcall target="jar-app"/>

and

<exec executable="${preverify.executable}" failonerror="true">

in that order.

This appears to be nowhere here or on Google (at least as far as I have seen), leading me to believe this is an issue with my machine. I have tried this on various versions of both Netbeans and Java. I checked alternatives to make sure Java was assigned correctly. Anybody have a clue?

[derekwhite]

I'm not seeing this on Mac or Windows.

The first thing to check is that you do have an executable program in /home/team342/sunspotfrcsdk/bin/preverify

Does this only happen on install/netbenas startup, or does it happen on suite/deploy/run also?

[WilliamY]

Preverify is there and executable. It does this every time I run it, both at startup and manually.

[java4first]

We're using Fedora 14 ... some things to look for (it's hard to remember, as we didn't have any problems this year getting Netbeans and Eclipse running on our Linux laptops). And these "fixes" may not have been what actually fixed it.

(1) Can't use the default open Java that comes with Fedora? We've installed the download from Sun. Make sure to fix your path to point to the right location (modify bash files).

(2) Can't use 64-bit Java? Even on the 64-bit laptops we always install the 32-bit SDK and JRE - before installing NetBeans (although I suppose there is a way, like in Eclipse, you can say which JRE / SDK you are using).

Hope that helps ... I seem to recall similar problems last year when we first tried to support Windows, Linux and MacOS to make everyone happy ;-)

[Kevin Wang]

Excuse the necropost, but I found a solution if there are any 64-bit Linux users out there with the same problem.

I found the solution in a cached copy of a post from a dead blog:

While migrating our development laptops off Windows and towards Linux, we discovered that WPIlib would not build, preventing us from actually doing development work.
The preverify binary would fail to execute, with the ant script complaining about an IOException.

I poked through a hexdump and saw references to ld-linux.so.2 and glibc, both of which I knew were installed. I took a wild guess and installed ia32-libs (Ubuntu's metapackage for a couple of common 32-bit libraries). After that, there were no issues with either compiling WPIlib or our own code.

TL;DR: If you're running a 64-bit linux distribution, install 32-bit glibc. Otherwise WPIlib will fail to compile.

I find it interesting that there is no precompiled 64-bit binary, despite the ant scripts recognizing 64-bit linux installs.

[ozzloy]

Originally Posted by Kevin Wang

Excuse the necropost, but I found a solution if there are any 64-bit Linux users out there with the same problem.

I found the solution in a cached copy of a post from a dead blog:

i just did `sudo apt-get install -y ia32-libs` and it worked! i didn't even have to close and reopen netbeans. just hit the build button again.

thanks!

[chadbarbe1]

Thanks for this thread!!!

Using the information here I was able to get my robot project working on fedora 17 using yum with this command:

sudo yum install glibc-devel.i686 glibc.i686

At least I can get it to the point of trying to connect to the robot - which is farther than i was before! Don't have a robot at work to test with but i'll be able to try it this weekend.

[joelg236]

Awesome. Thanks for this. Was stumped at the error.