Opened 13 years ago
Closed 12 years ago
#34295 closed defect (fixed)
Failed to install atlas
| Reported by: | matsukaze12@… | Owned by: | jameskyle@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | Cc: | matsukaze12@…, shapovalow@…, malix.ren@…, pixilla (Bradley Giesbrecht), mkeller@…, william@…, m1cha3ld0m1n0@…, ejtttje@…, maehne (Torsten Maehne), dershow | |
| Port: | atlas |
Description
When I try to install atlas, iget an error.
-- Environment are below --
Mac OS 10.6.8 Macports 2.0.4
Attachments (2)
Change History (30)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Owner: | changed from macports-tickets@… to jameskyle@… |
|---|---|
| Port: | atlas added |
Changed 13 years ago by matsukaze12@…
I updated this file (clean installed log )
comment:2 Changed 13 years ago by matsukaze12@…
according to the log file, it looks like http 404 error.
- :debug:archivefetch Fetching archive failed
- The requested URL returned error: 404
comment:3 Changed 13 years ago by mas@…
That 404 error only means that the binary archive could not be fetched, so macports then proceeds to (try to) build atlas from source. As of a few months ago, that was the primary procedure for building ports, and it's definitely a bug if it does not.
I'm currently facing what looks to be the same problem, using x86_32 on 10.7.3 Lion.
comment:9 Changed 13 years ago by pixilla (Bradley Giesbrecht)
atlas builds with either the +gcc44 or +gcc46 variants. Perhaps we should change the default variant to +gcc44 or +gcc46 variants.
comment:13 Changed 13 years ago by mkeller@…
I have the same issue. I try two variants (+gcc45 and +gcc46).
According to my (and the attached logs), the last command failed is: ../configure --prefix=/opt/local -C xc /opt/local/bin/gcc-mp-4.6 -C gc /opt/local/bin/gcc-mp-4.6 -C if /opt/local/bin/gfortran-mp-4.6 -C ic /opt/local/bin/gcc-mp-4.6 -C dm /opt/local/bin/gcc-mp-4.6 -C sm /opt/local/bin/gcc-mp-4.6 -C dk /opt/local/bin/gcc-mp-4.6 -C sk /opt/local/bin/gcc-mp-4.6 --cc=/opt/local/bin/gcc-mp-4.6 --with-netlib-lapack-tarfile=/opt/local/var/macports/distfiles/atlas/lapack-3.3.1.tgz -O 12 -b 64 -Fa alg -fPIC -D c -DPentiumCPS=2660 (in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/atlas-3.9.47/build )
Running this command by hand reveals another error: cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_math_atlas/atlas/work/atlas-3.9.47/build ; ./xprobe_comp -v 0 -o atlconf.txt -O 12 -A 17 -Si nof77 0 -C ic '/opt/local/bin/gcc-mp-4.6' -Fa ic '-fPIC' -C sm '/opt/local/bin/gcc-mp-4.6' -Fa sm '-fPIC' -C dm '/opt/local/bin/gcc-mp-4.6' -Fa dm '-fPIC' -C sk '/opt/local/bin/gcc-mp-4.6' -Fa sk '-fPIC' -C dk '/opt/local/bin/gcc-mp-4.6' -Fa dk '-fPIC' -C xc '/opt/local/bin/gcc-mp-4.6' -Fa xc '-fPIC' -C if '/opt/local/bin/gfortran-mp-4.6' -Fa if '-fPIC' -b 64 > config1.out UNKNOWN COMPILER '/opt/local/bin/gcc-mp-4.6' for ICC: you must also supply flags!
Removing the redirection "> config1.out" doesn't reveal something or in other word config1.out is empty.
ICC stands (most probably) for Intel C++ Compiler. Its the same error with gcc-mp-4.5.
An now my knowledge is gone, what flags are missing? I mean there are a lot flags floating in those 3 "xprobe_comp" lines.
Please ,we all would appreciate help for this topic from ICC experts or package maintainer.
comment:14 Changed 13 years ago by Veence (Vincent)
ICC is not the Intel C Compiler in that case, but Atlas internal reference for the C compiler used for a particular purpose. You can see Atlas docs to find out more info.
Besides, I have 3.9.74 ready (works with clang, and has AVX support), but I could not carry extensive tests. I’ll commit it ASAP.
comment:20 Changed 12 years ago by Veence (Vincent)
I have upgraded the port to 3.9.75. Please try again.
comment:21 Changed 12 years ago by ejtttje@…
This update may be causing issues in #25662... did the library build change?
comment:22 Changed 12 years ago by Veence (Vincent)
As I explained in #25662, yes, the dylibs are now built with Atlas itself, whereas before the Portfile was responsible for their generation. Their names have been altered during this shift.
comment:23 Changed 12 years ago by mkeller@…
@Vince: many thanks for your update. It still doesn't work, but the error is different - so we make progress I guess; crossing the fingers. I fetched: atlas3.9.75.tar.bz2, with MacPorts 2.1.1; German OS X 10.6.8 finally a make failed: 2 errors: (1) "Make.top" includes a "Make.inc"; maybe not created by configure, I touched "Make.inc" to bypass this error: (2) (the same Make.top) has "/AtlasTest" defined twice (as I understand the msgs) but this are warnings and (2.b) finally "cd bin/ ; /usr/bin/make xatlas_build" (called due to rule "build" in "Make.top") has no xatlas_build target defined. Frankly, the directory "../altas-3.9.75/build/bin" has only a "ATLrun.sh" file, nothing more.: paste of the log until June at http://pastebin.de/26451
comment:24 Changed 12 years ago by mkeller@…
uh sorry for the missing layout, pretty ugly, but I forgot wikiformatting
@Vince: many thanks for your update.
It still doesn't work, but the error is different - so we make progress I guess; crossing the fingers.
I fetched: atlas3.9.75.tar.bz2, with MacPorts 2.1.1; German OS X 10.6.8
finally a make failed: 2 errors:
(1) "Make.top" includes a "Make.inc"; maybe not created by configure, I touched "Make.inc" to bypass this error:
(2) (the same Make.top) has "/AtlasTest" defined twice (as I understand the msgs) but this are warnings and
(2.b) finally "cd bin/ ; /usr/bin/make xatlas_build" (called due to rule "build" in "Make.top") has no xatlas_build target defined.
Frankly, the directory "../altas-3.9.75/build/bin" has only a "ATLrun.sh" file, nothing more.
paste of the log until June at http://pastebin.de/26451
comment:25 Changed 12 years ago by Veence (Vincent)
Grüß Gott! ;)
Something is obviously wrong in your configuration. You ask for gcc46 (+gcc46 variant) and you end up using gcc-4.2 which is of course not registered as a possible compiler for Atlas, wherefore the failure. It is as if something in your environment was overriding port choices. Sonderbar.
comment:27 Changed 12 years ago by mkeller@…
@Vince:
Moin Moin!
I (try to) clean up my system with "port uninstall atlas @*all_versions_I_had*" and dependent packages; I successfully (re)install atlas with +gcc46.
Previous attempts to clean install (=previously "port uninstall" and "port clean package") atlas default (=omit +gcc44) and forced +gcc44 variant, failed due to gcc42 usage.
Thank you for your help. (I'm unsure if now the bug report can be closed, maybe the other CC-people check if it works on a "not wrong configured system" (like mine).
comment:28 Changed 12 years ago by Veence (Vincent)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Hallo! Thanks for your report. It should work for anybody else, so I’ll close the bug for now, if somebody still experience a difficulty, please reopen it.
Since this was not a clean build attempt, please "sudo port clean atlas", then try again. then attach the new main.log.