Hello Pavel,
Pavel Roskin wrote:
>
> Hello!
>
> RPM (RedHat package manager) as of version 3.0.4 uses the following macro
> in its default configuration file
>
> %configure \
> %{?__libtoolize:[ -f configure.in ] && %{__libtoolize} --copy --force} \
^^^^^^^^^^
Doesn't this require package builders to install libtool. I thought
that libtool was designed to be included in a distribution.
Michael
> CFLAGS="%{optflags}" ./configure %{_target_platform} --prefix=%{_prefix}
>
> Package creators are encouraged to use this macro, i.e. they should call
> %configure instead on ./configure in the package build scripts.
>
> %{_target_platform} expands to the canonicalized triplet. For the packages
> using the future versions of Autoconf this should be
>
> --build %{_target_platform}
>
> But is it safe for old versions of Autoconf? Will it have the same effect
> if e.g. config.guess fails to recognize the architecture? If it is, we
> should recommend RPM developers to add "--build" before
> %{_target_platform}
>
> Regards,
> Pavel Roskin
--
------------------------------------------------------------------
Michael Bletzinger Software Developer, Alliance Computational
[EMAIL PROTECTED] Environment & Security
217 265 5137 NCSA
