| Summary: | sys-cluster/redhat-cluster-suite-2.01.00.ebuild (NEW EBUILD) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | r01 <crquan> |
| Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | VERIFIED DUPLICATE | ||
| Severity: | enhancement | CC: | alexxy, bpkroth |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | http://sources.redhat.com/cluster/ | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
sys-cluster/redhat-cluster-suite-2.01.00.ebuild
files/cluster-2.01.00-turn-off-werror-on-gcc4.patch |
||
|
Description
r01
2007-12-31 18:24:03 UTC
Created attachment 139754 [details] sys-cluster/redhat-cluster-suite-2.01.00.ebuild this is the ebuild for 2.01.00 release of redhat cluster suite: ftp://sources.redhat.com/pub/cluster/releases/cluster-2.01.00.tar.gz its only denpendency is openais-0.80.3, which is on #160847 Created attachment 139755 [details]
files/cluster-2.01.00-turn-off-werror-on-gcc4.patch
sorry, I cannot find the right way to compile the redhat cluster suite 2.01.00 on my gcc-4.2.2, without any one warning, so I changed the Makefiles to remove the -Werror parameter.
If you can find the right way, please post here.
Another approach is to add an explicit warning turning off: -Wno-strict-aliasing Um, no. Individual packages one dependeing on the other is the right way to go. There is nothing wrong with a meta package, though. Dupe anyway... *** This bug has been marked as a duplicate of bug 195730 *** (In reply to comment #5) > Dupe anyway... > ...by the same user. Please don't play silly games with us raeL. (In reply to comment #7) So sorry, I've forgotten that bug #195370, But if the public don't accept it, I can only use it on my own, it runs well here. Separate ebuilds for cman,ccs,gfs2 is a little troublesome, I will try to resolve it. (In reply to comment #8) > Separate ebuilds for cman,ccs,gfs2 is a little troublesome, I will try to > resolve it. Your are welcome to file bugs for those as necessary. (In reply to comment #8) > Separate ebuilds for cman,ccs,gfs2 is a little troublesome, I will try to > resolve it. So does this mean you're already working on creating split ebuilds? If not, I'll get started on them tomorrow. (In reply to comment #10) > So does this mean you're already working on creating split ebuilds? ??? That's what we already have; the request here is for monolithic beast which is not going to happen. (In reply to comment #11) > ??? That's what we already have; the request here is for monolithic beast which > is not going to happen. > Do we have the 2.* versions somewhere? The only ones I see in portage are 1.03.00, 1.04.00. Irrelevant here; take version bump requests out of this bug please, and note this ain't forums.gentoo.org. This is for bugs *only*. CLOSED (In reply to comment #10) > (In reply to comment #8) > > Separate ebuilds for cman,ccs,gfs2 is a little troublesome, I will try to > > resolve it. > > So does this mean you're already working on creating split ebuilds? If not, > I'll get started on them tomorrow. I have worked out the dependency of components of cluster-2.01.00, there's big difference between gfs2 and gfs, and gfs2-2.01.ebuild has been on #201132 However, we could cont to discuss on forums: http://forums.gentoo.org/viewtopic-p-4710605.html |
