On Tue, Jul 08, 2003, julien Touche wrote:
> there is no way to have gcc??.rpm provides gcc but still use suffix (in
> this case rpm rebuild use gcc if present else other gcc??)
Most packages will search for the 'standard C compiler' using the
%{l_cc} macro.
In this case you can override that macro by defining a 'use_cc path' macro.
I.e.:
rpm -ba --define 'use_cc /usr/local/bin/mycc' package.spec
or
openpkg build -Duse_cc=/usr/local/bin/mycc package
The macro used to be known as 'with_cc', but we changed this to distinguish
it better from the package option system. There are analog macros for
other standard tools like %{l_make} for the make program or %{l_tar}
for the tar program.
Please note that even when the package honors the %{l_cc} macro it may fail
to build with a different compiler! This feature is meant as a last resort
for bootstrapping packages on new architectures where the gcc package
is not yet available.
Generally, the packages that depend on the gcc package also
require exactly the released version of the GNU compiler. I.e.
you can only build packages from OpenPKG-1.2 with the gcc package
from OpenPKG-1.2.
Greetings,
--
,eM""=. a"-. Michael van Elst
dWWMWM" - :GM==; [EMAIL PROTECTED]
:WWMWMw=--. "W=' cable & wireless
9WWMm==-.
"-Wmw-" CABLE & WIRELESS
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List [EMAIL PROTECTED]
