Bugzilla – Full Text Bug Listing
| Summary: | Missing #include <stdio.h> in core jni code | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Jan Schulz <jasc> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | mark |
| Version: | 3.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | |||
| Bug Blocks: | 71637 | ||
Our natives don't use any functions from stdio, so there is no reason to add it. The "simnplest JNI example" cited uses "printf", so in that case it is required. |
Hello, I'm curerntly packaging eclipse for debian and I tried to do it with free (so that eclipse can go into debian main) java virtual machines. When I compile with kaffe, I got compile errors in the native code of the core plugin. Thsi was fixed with adding a #include <stdio.h> in kaffes jni.h file. As it turns out, the jni spec doesn't require, that this is included there, but in the implementing jni code of the client. So I'm filing this bug here. This is a part of the email I got from kaffe upstream: >I think it is best to report this as a bug to the Eclipse hackers. >Even the simplest JNI example that I could find >http://java.sun.com/docs/books/jni/html/start.html#26865 >says you should include stdio.h separately. Nice greetings, Jan