Bug 443261
| Summary: | Get java-1.6.0-openjdk in EPEL-4 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Patrick Macdonald <patrickm> |
| Component: | java-1.6.0-openjdk | Assignee: | Lubomir Rintel <lkundrak> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | el4 | CC: | erik-fedora, herrold, mail, notting, tjb, walters |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | PackageBranch | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-03-01 20:02:42 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 438069 | ||
| Bug Blocks: | |||
|
Description
Thomas Fitzsimmons
2008-04-19 20:26:11 UTC
Seems like it won't be any fun to bootstrap gcj 1.5 on RHEL-4. Openjdk bianry from EPEL 5 depends on quite some glibc features unavailable in RHEL-4. What comes to my mind is forcing newer and older glibc be installed side by side with older glibc-devel. I did that once on RHEL-5/ppc and compilation surprisingly succeeded, but the resulting javac would not run anything, just die with oom exception. Thomas: is there any chances it will be possible to bootstrap OpenJDK with a proprietary Java VM, such as sun or ibm java? (In reply to comment #1) > Thomas: is there any chances it will be possible to bootstrap OpenJDK with a > proprietary Java VM, such as sun or ibm java? No, this is not an option because it risks propagation of proprietary bits. See here for a full explanation: https://bugzilla.redhat.com/show_bug.cgi?id=438421#c16 Have you attempted to build the RHEL-5 gcc SRPM on RHEL-4? If that succeeded you could use that gcj to build OpenJDK against RHEL-4's glibc. At that point you would include the resulting OpenJDK binaries in the OpenJDK SRPM and bootstrap from them. Once OpenJDK is in the EPEL-4 buildroots you would remove the OpenJDK binaries from the SRPM and rebuild. There may be other dependencies that aren't available on RHEL-4 that could complicate this approach -- I haven't looked. Also, this process would need to be done on every architecture. (In reply to comment #2) > (In reply to comment #1) > > > Thomas: is there any chances it will be possible to bootstrap OpenJDK with a > > proprietary Java VM, such as sun or ibm java? > > No, this is not an option because it risks propagation of proprietary bits. Quite understandable. > Have you attempted to build the RHEL-5 gcc SRPM on RHEL-4? If that succeeded > you could use that gcj to build OpenJDK against RHEL-4's glibc. At that point > you would include the resulting OpenJDK binaries in the OpenJDK SRPM and > bootstrap from them. Once OpenJDK is in the EPEL-4 buildroots you would remove > the OpenJDK binaries from the SRPM and rebuild. That's the way I built it on RHEL-5 (I used Fedora 8's gcc on RHEL-5 though). I thought OpenJDK can't be built with RHEL-5's gcj-1.4.2? Fedora 8's gcc can not be built with RHEL-4 one, but I may try RHEL-5 gcc first, and then Fedora 8 maybe... > There may be other dependencies that aren't available on RHEL-4 that could > complicate this approach -- I haven't looked. Also, this process would need to > be done on every architecture. Sure. (In reply to comment #3) > (In reply to comment #2) > > (In reply to comment #1) > > > That's the way I built it on RHEL-5 (I used Fedora 8's gcc on RHEL-5 though). I > thought OpenJDK can't be built with RHEL-5's gcj-1.4.2? Yes, that's right, my mistake. > Fedora 8's gcc can not > be built with RHEL-4 one, but I may try RHEL-5 gcc first, and then Fedora 8 maybe... Hmm, I'm surprised that Fedora 8 gcc can't be built with RHEL-4 gcc. But yeah, two step compiler bootstrapping is an option I guess. EPEL-4 has reached end of life and is no longer supported. Please retest your bug against EPEL-5 or EPEL-6 and re-open if the bug persists in the packages available in those releases, or file a new bug. See: http://lists.fedoraproject.org/pipermail/epel-announce/2012-February/000015.html |