On Wed, Jul 02, 2003, julien Touche wrote:
> >Ok, I've looked at this and it looks like a reasonable optional
> >addition to our GCC package. I've integrated it now (see
> >http://cvs.openpkg.org/chngview?cn=10135 for details), but in a
> i think, it miss 1 things an option to activate by default (patch
> protectonly.dif)
> >>>
> %if "%{with_spp}" == "yes"
> ( cd gcc
> %{l_gzip} -d -c %{SOURCE protector-%{version}-%{V_spp}.tar.gz} |
> %{l_tar} xf -
> - %{l_patch} -p1 <protector.dif )
> + %{l_patch} -p1 <protector.dif
> +%if "%{with_spp_def}" == "yes"
> + %{l_patch} -p1 <protectonly.dif
> +%endif
> + )
> %endif
> <<<
Err... as I said: "...as source (principle of pristine source files) and
intentionally do not provide the enabling of the patch's functionality
by default (because this breaks POLA IMHO too much)." If you want other
packages built with gcc and this option enabled, you can use --define
"use_cc /prefix/bin/gcc -f...." on the RPM command line (if that is what
you want to achieve).
> [...]
> one last question, would it be seen in gcc32/gcc33 spec file ?
There is no SPP for gcc 3.2.3 (only 3.2.2) and GCC 3.3.1 snapshots.
So I cannit add this to gcc32 and gcc33 packages at this time.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
