public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/4785] New: use .java -> .class -> .jar -> .a to build frysk? Date: Thu, 12 Jul 2007 14:03:00 -0000 [thread overview] Message-ID: <20070712140338.4785.cagney@redhat.com> (raw) At present frysk uses the path: .java -> .o -> .a to build its native code. This was forced by a number of problems with older java compilers mis-compiling, mis-re-building, and/or messing up errors when the more traditional .java -> .class route was taken. The .java -> .o route proved far more robust. Unfortunatly, now with Fedora 7++, the compiler is tuned more for the bulk .java->.class route so switching to that will improve the F7 build experience. On RHEL 4, just the ability to scratch build is needed. -- Summary: use .java -> .class -> .jar -> .a to build frysk? Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: cagney at redhat dot com OtherBugsDependingO 2235 nThis: http://sourceware.org/bugzilla/show_bug.cgi?id=4785 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2007-07-12 14:03 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20070712140338.4785.cagney@redhat.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).