Summary: | blas-19980702.ebuild installs the package even if compile fails | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Emil Erlandsson <emil> |
Component: | New packages | Assignee: | Gentoo Science Related Packages <sci> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | ||
Priority: | High | ||
Version: | 2004.1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Emil Erlandsson
2004-05-09 17:35:25 UTC
Forgot to add that the script does not die either if the make process fails or if the files it tries to install does not exist. Hi Emil. Please take a look at app-sci/blas-* packages (blas-reference and blas-atlas). These are going to be the future of blas (and the same for lapack-*) in portage. They introduce an ability to mix and match different variants of blas via blas-config. Plus they should have this issue fixed already (but please check!). I am actually about to unmask blas-* packages and do a bit of explanation on the lists (the change is sizeable and will effect other devs), so if you could post your test results that would be awesome! See #30453 for more details (and please report to that bug as well). Closing this bug as a dup correspondingly.. George *** This bug has been marked as a duplicate of 30453 *** Ok, I shall see what I can do. I re-compiled GCC with support for fortran, so should I recompile again without it, and try to install the other blas-packages instead? Hm, that's quite involved, but I am not sure if there is an easier way to do the testing. May be try renaming g77 into something, then try emerging the package and then rename that back into g77? IIRC the blas build script tests for g77 presence, but I am not totally sure atm. I'll be revisiting blas_* packages soon, before unmasking them, but it would be nice to have many test reports in order to be sure that we do not screw things up. George. |