Support for building RHEL srpms has not been dropped at all. The
rhel/gcc efsdeploy rules are the same as the gnu/gcc efsdeploy rules,
because the only thing that's different is the source archive. How
you build them remains identical.
However, the default download->url in the gnu/gcc rules is the one for
the gnu.org gcc, of course, and the problem I didn't solve yet is how
to abstract the same url for the rhel/gcc builds. Since I only do
this for 2 projects (rhel/binutils, rhel/gcc), it's not a really
urgent problem.
To build the rhel/gcc releases, you have to specify the download->url
in a release-specific efsdeploy.conf file. For example:
/efs/dev/rhel/gcc/4.1.2-52.el5_8.1-build002/src/efsdeploy.conf:
[download]
url =
http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/$project-$releasealias.src.rpm
[defaults]
platforms = x86-32.rhel.5 x86-64.rhel.5
Note that you also have to restrict (or should restrict) this build to
just the RHEL5 platforms. For RHEL6, I build *that* releases
compiler natively.
On Fri, Nov 23, 2012 at 12:19 PM, Steven Jenkins
<[email protected]> wrote:
> I'm looking at the rhel/gcc* tree at the moment, and I'm a little
> confused: my previous understanding was that the rhel/* tree is built
> by using srpm's, using the same arguments as the upstream vendor, the
> same patches, etc, modulo a few changes to make the paths work in EFS
> (i.e., the only changes are to options like --prefix, --exec-prefix,
> etc).
>
> However, in the current efs-deploy-config-rhel repository, the only
> configuration information for gcc and gcclib is a redirect to gnu.
>
> Has support for building from the srpm's been dropped?
>
> Thanks,
> Steven
> _______________________________________________
> EFS-dev mailing list
> [email protected]
> http://mailman.openefs.org/mailman/listinfo/efs-dev
_______________________________________________
EFS-dev mailing list
[email protected]
http://mailman.openefs.org/mailman/listinfo/efs-dev
