Blender 2.37, spec and srpms

Toshio Kuratomi toshio at tiki-lounge.com
Wed Jun 8 23:33:57 UTC 2005


On Wed, 2005-06-08 at 10:58 -0800, luya at jpopmail.com wrote:
> > It looks like patch is not finding the correct files.  Diagnosing this
> > would be elped by specifying where you think that file resides instead
> > of skipping over it.  So on the "File to patch:" line try
> > blender/source[...]KX_HashedPtr.cpp
> > source/gameeng[...]KX_HashedPtr.cpp
> > etc
> > and see if you can figure out where patch is going wrong.
> > 
> Yeah, both spec and patch are from FE cvs. I have tried lines above but it asked me 
> for another file to patch. Thanks to Michael A. Peters, I used a condition for i386:
> 
> %prep
> %setup -q -n %{name}
> %ifarch x86_64
> %patch0 -p1 -b .x86_64
> %endif
> 
> until I have an odd problem:
> 
> -----
> $ rpmbuild -ba rpmbuild/SPECS/blender.spec
> Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.26366
> + umask 022
> + cd /home/Luya/rpmbuild/BUILD
> + LANG=C
> + export LANG
> + unset DISPLAY
> + cd /home/Luya/rpmbuild/BUILD
> + rm -rf blender
> + /usr/bin/gzip -dc /home/Luya/rpmbuild/SOURCES/blender-2.37.tar.gz
> + tar -xf -
> + STATUS=0
> + '[' 0 -ne 0 ']'
> + cd blender
> ++ /usr/bin/id -u
> + '[' 500 = 0 ']'
> ++ /usr/bin/id -u
> + '[' 500 = 0 ']'
> + /bin/chmod -Rf a+rX,u+w,g-w,o-w .
> + exit 0
> Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.95915
> + umask 022
> + cd /home/Luya/rpmbuild/BUILD
> + cd blender
> + LANG=C
> + export LANG
> + unset DISPLAY
> + sed -i 's/use_openal =.*/use_openal = '\''true'\''/g;' SConstruct
> sed: can't read SConstruct: No such file or directory
> error: Bad exit status from /var/tmp/rpm-tmp.95915 (%build)
> 
> Strange problem because this line only declares SConstruct, it was not
> present with previous spec.

Okay, I've figured out your problem.  You aren't using the upstream
tarball.  The last Compton release used a blender that installed into
the standard %{name}-%{version} directory structure.  The current
blender instals to %{name}.  From the tarball you listed in your
previous post, it appears you created a new tarball with a
%{name}-%{version} directory structure and left the upstream %{name}
directory structure as well... except empty.  This is why rpm isn't
erroring out with a more informative message about directory not
found.... instead it can't find the files it expects to operate on.

What you're going to want to do is either:
1) Use the blender built in the buildsystem.  They're in the fedora
extras repository now for FC4 and FC3.

2) Redownload the pristine blender tarball and the spec file from cvs.
Rebuild with that.

-Toshio
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-extras-list/attachments/20050608/adc9487e/attachment.sig>


More information about the fedora-extras-list mailing list