On Thu, Feb 7, 2013 at 2:26 PM, Alan McKay <[email protected]> wrote:
>
> On Thu, Feb 7, 2013 at 2:17 PM, Nico Kadel-Garcia <[email protected]> wrote:
>>
>> I also mistyped: it should have been "rpmbuild --rebuild
>> lapack-[version].src.rpm".
>
>
> I guess this is the build dependencies you were talking about.  Does not
> look like this will be easy either :-(
>
> [root@solexa-db lapack-srcrpm]# rpmbuild --rebuild
> lapack-3.4.1-4.fc19.src.rpm
> Installing lapack-3.4.1-4.fc19.src.rpm
> warning: user mockbuild does not exist - using root
> warning: group mockbuild does not exist - using root
> error: unpacking of archive failed on file
> /usr/src/redhat/SOURCES/Makefile.blas;5113ffad: cpio: MD5 sum mismatch
> error: lapack-3.4.1-4.fc19.src.rpm cannot be installed
> [root@solexa-db lapack-srcrpm]#

That is Fedora 19, or the rawhide version. I said Fedora 18, for good
reasons. Releases are more stable than rawhide.

That also looks like you're trying to build it on an SL 5 system. SL 6
uses a newer version of RPM, with new checksum algorithms compatible
with modern Fedora. Try building in on SL 6, or if you have to try on
SL 5, do this:

It also looks you're trying to build the RPM as a root user *STOP
DOING THAT*. It's a nasty, nasty, dangerous way to build RPM's because
even if you know the SRPM is valid, it only takes one bad mistake in
an installation script or a dependent Perl or Python macro to
overwrite your system files and cause..... chaos.

Try something like this, instead, if you need to try SL 5.

      rpm --showrc | grep ^_topdir
      # verify that _topdir is not /usr/src/redhat, it's typically
$HOME/rpmbuild
      # Set up $HOME/.rpmmacros if needed to fix this
      cd $HOME/rpmbuild/SOURCES
      rpm2cpio [dirname]/lapack-3.4.1-2.fc18.src.rpm
      mv lapack.spec ../SPECS
      rpmbuild -ba ../SPECS/lapack.spec

For SL 6 this should work fine:

      rpmbuild --rebuild lapack-3.4.1-2.fc18.src.rpm

That will report some build dependencies which you may need to
resolve, but it works fine on SL 6.

                                     Nico Kadel-Garcia <[email protected]>

Reply via email to