On Wed, 8 Feb 2006, Anthony Philipp wrote:
Hello,
I was doing an upgrade today and one of the ports failed. I have
since checked /usr/ports/UPDATING, the mailing list and then
updated my ports tree again, all to no avail. Here is the error:
---
f77 -O -c ssyr2k.f
f77 -O -c strmm.f
f77 -O -c strsm.f
i386 cr ../../BLAS/SRC/libblas.a isamax.o sasum.o saxpy.o scopy.o sdot.o
snrm2.o srot.o srotg.o sscal.o sswap.o lsame.o xerbla.o sgemv.o sgbmv.o
ssymv.o ssbmv.o sspmv.o strmv.o stbmv.o stpmv.o strsv.o stbsv.o stpsv.o
sger.o ssyr.o sspr.o ssyr2.o sspr2.o sgemm.o ssymm.o ssyrk.o ssyr2k.o strmm.o
strsm.o
i386:No such file or directory
*** Error code 1
Stop in /usr/ports/math/lapack/work/LAPACK/BLAS/SRC.
*** Error code 1
Stop in /usr/ports/math/lapack/work/LAPACK.
*** Error code 1
Stop in /usr/ports/math/lapack.
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade78155.12
make
** Fix the problem and try again.
** Detected a package name change: libmikmod (audio/libmikmod) ->
'libmikmod-esound' (audio/libmikmod)
** No need to upgrade 'libmikmod-3.1.11' (>= libmikmod-esound-3.1.11). (specify
-f to force)
** Detected a package name change: mpg123 (audio/mpg123) -> 'mpg123-esound'
(audio/mpg123)
** No need to upgrade 'mpg123-0.59r_17' (>= mpg123-esound-0.59r_17). (specify
-f to force)
** Detected a package name change: libao (audio/libao) -> 'libao-esound'
(audio/libao)
** No need to upgrade 'libao-0.8.5' (>= libao-esound-0.8.5). (specify -f to
force)
---> Skipping 'math/scilab' (scilab-3.1.1_1) because a requisite package
'lapack-3.0' (math/lapack) failed (specify -k to force)
** Listing the failed packages (*:skipped / !:failed)
! math/lapack (lapack-3.0) (unknown build error)
* math/scilab (scilab-3.1.1_1)
---> Packages processed: 0 done, 561 ignored, 1 skipped and 1 failed
---
I have the same problem with 5.5-PRERELEASE. It's obvious that "i386" is
being used instead of "ar" - the routine that creates libraries - but the
problem is not in the source directory since using "make" there uses "ar"
correctly.
I suspect it has something to do with a patch that was reversed today, so
you may want to re-cvsup your ports sources and try again - I am.
Mike Squires
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
