On Thu, 5 Jun 2003, Bertrand wrote:
> I've done a very first SRPM for GWorkspace-0.5.1, the gnustep clone of
> the NeXT filemanager. I'm not very sure of my specfile and I've still
> got one problem : it can only compile on PowerPC (so x86 users will
> come after, this time ;-))) )
>
> My pr
I've done a very first SRPM for GWorkspace-0.5.1, the gnustep clone of
the NeXT filemanager. I'm not very sure of my specfile and I've still
got one problem : it can only compile on PowerPC (so x86 users will
come after, this time ;-))) )
My problem is at the beginning of the spec file :
%defi
Le Vendredi 06 Juin 2003 11:34, Bertrand a écrit :
> $GNUSTEP_HOST_CPU is gnustep specific. If %_target_cpu or %_host_cpu
> returns the same results, I could use them, but is it the case ?
> Here on PPC :
> [EMAIL PROTECTED] tranber]$ rpm --eval %_target_cpu
> ppc
> [EMAIL PROTECTED] tranber]$ rpm
On Fri, 6 Jun 2003, Bertrand wrote:
> $GNUSTEP_HOST_CPU is gnustep specific. If %_target_cpu or %_host_cpu
> returns the same results, I could use them, but is it the case ?
> Here on PPC :
> [EMAIL PROTECTED] tranber]$ rpm --eval %_target_cpu
> ppc
> [EMAIL PROTECTED] tranber]$ rpm --eval %_hos
$GNUSTEP_HOST_CPU is gnustep specific. If %_target_cpu or %_host_cpu
returns the same results, I could use them, but is it the case ?
Here on PPC :
[EMAIL PROTECTED] tranber]$ rpm --eval %_target_cpu
ppc
[EMAIL PROTECTED] tranber]$ rpm --eval %_host_cpu
powerpc
So it's clearly %_host_cpu to use.
Le Vendredi 06 Juin 2003 01:01, Stew Benedict a écrit :
> On Thu, 5 Jun 2003, Bertrand wrote:
> > I've done a very first SRPM for GWorkspace-0.5.1, the gnustep clone of
> > the NeXT filemanager. I'm not very sure of my specfile and I've still
> > got one problem : it can only compile on PowerPC (so
