[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: getting architecture/os info when building an rpm
- From: rpjday <rpjday mindspring com>
- To: <rpm-list redhat com>
- Subject: Re: getting architecture/os info when building an rpm
- Date: Tue, 8 Jan 2002 12:22:47 -0500 (EST)
On Tue, 8 Jan 2002, Jeff Johnson wrote:
> RPM_{ARCH,OS} are set by the %___build_pre macro that is expanded at
> the beginning of a scriptlet (to make it a script):
>
> %___build_pre \
> RPM_SOURCE_DIR=\"%{u2p:%{_sourcedir}}\"\
> RPM_BUILD_DIR=\"%{u2p:%{_builddir}}\"\
> RPM_OPT_FLAGS=\"%{optflags}\"\
> RPM_ARCH=\"%{_arch}\"\
> RPM_OS=\"%{_os}\"\
so, just to make sure i have an answer to my previous question,
these variables and respective macros are based on the host that
the build is being done on, right? and not subject to selection
by the user.
> > %_target sparc-sunos
> > %_target_arch %_target_arch (clearly no such macro)
>
> The macro you want is %{_target_cpu}, same name as what autoconf uses.
which implies that the rpmbuild man page needs fixing.
> %ifarch uses the expansion of %_target_cpu, %ifos uses %_target_os.
>
> >From build/parseSpec.c:247
oh, right -- read the *source* to get the answer. :-)
> Yup. Isn't legacy wonderful :-(
this is a rhetorical question, i assume. thanks for the info.
rday
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]