This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: installed, compiled, how to link?


hill0093 wrote:
Thanks, you are all so nice; ./a.out worked. Windows looks in local directory first.
Linux is unexpectedly different from windows.
It's tempting to say unexpectedly dumb,
but unix looked in local directory first 30 years ago,
so I suppose there is good reason to have changed it.
How do I deal with paths?


On a slightly more complicated program that uses imports,
I get the following when I compile and run:
gcj --main=LandsBug LandsBug.java
./a.out
Exception in thread "main" java.lang.UnsupportedOperationException
   at java.awt.image.ColorModel.createCompatibleSampleModel(libgcj.so.70)
   at java.awt.image.ColorModel.createCompatibleWritableRaster(libgcj.so.70)
   at java.awt.image.BufferedImage.<init>(libgcj.so.70)
   at LandsBug.main2(a.out)
   at LandsBug.main(a.out)

And I can't figure out what to do.
libgcj evidently does not support what ever it is you are trying to do with BufferedImages.

Your options are fairly limited at this point. Either

1) Change your code to use BufferedImage operations that are supported by the version of libgcj that is part of your system.
2) Install Sun's JVM and use that instead.
3) Get the source code to libgcj and fix it.


When I have problems with gcj, I usually choose option 3. Unless you are familiar with software development on GNU/Linux, you probably would be better off with one of the other options.

David Daney


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]