Opened 9 years ago

Closed 3 years ago

Last modified 3 years ago

#3030 closed defect (worksforme)

Openmodelica fails to configure

Reported by: Adam Dershowitz <dersh@…> Owned by: sjoelund.se
Priority: high Milestone: 1.16.0
Component: Build Environment Version: trunk
Keywords: Cc:

Description

I am using openmodelica-devel on a mac, and I just tried to upgrade from 23710_0 to 23769_0.
But, I get an error that it fails on the config stage:

--->  Fetching distfiles for openmodelica-devel
--->  Verifying checksums for openmodelica-devel
--->  Extracting openmodelica-devel
--->  Configuring openmodelica-devel
Error: Failed to configure openmodelica-devel, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_build.openmodelica.org_macports_lang_openmodelica-devel/openmodelica-devel/work/openmodelica_23769/config.log
Error: org.macports.configure for port openmodelica-devel returned: configure failure: command execution failed
Please see the log file for port openmodelica-devel for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_build.openmodelica.org_macports_lang_openmodelica-devel/openmodelica-devel/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

I did recently use macports to install octave, which installed clang-3.4 as a dependent (before I just had 3.3). I don't know if that might be related. But, I tried this, as a test, but it didn't help:

sudo port select clang mp-clang-3.3

I have attached the config log with the failure.

Attachments (1)

config.log (100.2 KB) - added by Adam Dershowitz <dersh@…> 9 years ago.
Configure log

Download all attachments as: .zip

Change History (11)

Changed 9 years ago by Adam Dershowitz <dersh@…>

Configure log

comment:1 Changed 9 years ago by Adam Dershowitz <dersh@…>

Seems like the problem was that I had installed the atlas port, which includes lapack.
I don't know why that is causing a problem, and whether it is an openmodelica problem or an macports/atlas/lapack issue.
The workaround was to force disable atlas.
But, there is some incompatibility, in that having atlas installed causing openmodelica to fail to configure.

comment:2 Changed 9 years ago by sjoelund.se

If it was a shared libatlas, everything would have been fine. But it is static and does not include all of its own dependencies, so it fails to link :( It's good that configure caught this; otherwise it would take until the end of building to find the error.

comment:3 Changed 9 years ago by Adam Dershowitz <dersh@…>

Is atlas something that is not required, but is used if it is found on the system? So, not having it is fine, but adding a non-shared version, when a shared version is required, is what causes this problem?
I have also asked the macports folks about it https://trac.macports.org/ticket/46228.
I had installed atlas to install octave. And that seems to be working fine.
In order to build openmodelica, I can force disable atlas. It then builds fine, and after scans and finds some broken links related to other ports, and reinstalls atlas.

comment:4 Changed 9 years ago by Adam Dershowitz <dersh@…>

Just to clarify it seems that the problem is a conflict between openmodelica and atlas (which was installed as part of Octave). If Atlas is installed, openmodelica will fail, but the following is a work around to install, or upgrade openmodelica:

sudo port -f deactivate atlas
--->  Deactivating atlas @3.10.2_1+gcc48
--->  Unable to deactivate atlas @3.10.2_1+gcc48, the following ports depend on it:
--->  	arpack @3.1.5_0+atlas+gcc48
--->  	qrupdate @1.1.2_3+atlas+gcc48
--->  	octave @3.8.2_3+atlas+gcc48+gui
Warning: Deactivate forced.  Proceeding despite dependencies.
--->  Cleaning atlas

Then when you upgrade, macports will find the bad links from above and fix them:

sudo port  upgrade  openmodelica-devel  build.jobs=6
--->  Computing dependencies for openmodelica-devel
--->  Configuring openmodelica-devel
--->  Building openmodelica-devel
--->  Staging openmodelica-devel into destroot
--->  Installing openmodelica-devel @24037_0+gfortran48+libraries+qt+sundials
--->  Cleaning openmodelica-devel
--->  Computing dependencies for openmodelica-devel
--->  Deactivating openmodelica-devel @23951_0+gfortran48+libraries+qt+sundials
--->  Cleaning openmodelica-devel
--->  Activating openmodelica-devel @24037_0+gfortran48+libraries+qt+sundials
--->  Cleaning openmodelica-devel
--->  Updating database of binaries
--->  Scanning binaries for linking errors
--->  Found 2 broken file(s), matching files to ports    
--->  Found 2 broken port(s), determining rebuild order
--->  Rebuilding in order
     arpack @3.1.5 +atlas+gcc48
     qrupdate @1.1.2 +atlas+gcc48
--->  Computing dependencies for arpack
--->  Dependencies to be installed: atlas
--->  Activating atlas @3.10.2_1+gcc48
--->  Cleaning atlas
--->  Cleaning arpack
--->  Computing dependencies for qrupdate
--->  Cleaning qrupdate
--->  Scanning binaries for linking errors
--->  No broken files found.                             

comment:5 Changed 9 years ago by Adam Dershowitz <dersh@…>

According to the atlas maintainer, in macports, the problem is that the modelica configuration script doesn't include -latlas. And, that is where the missing functions are located (not in liblapack.a or in libblas.a where it looks). Is it possible to get that added to the script?
I'm not sure, but would that solve the problem?

Thanks,

comment:6 Changed 9 years ago by sjoelund.se

That could very well be the problem. Except we don't look for or want atlas; we look for "-llapack -lblas".

comment:7 Changed 9 years ago by Adam Dershowitz <dersh@…>

In your second comment, you said that if were shared it would work. There is a shared atlas that is build as part of installing atlas. Is there a way to get openmodelica to find that?
It is: /opt/local/lib/libtatlas.dylib
Or is there some conflict with using atlas?

comment:8 Changed 9 years ago by adeas31

  • Owner changed from adeas31 to sjoelund.se
  • Status changed from new to assigned

comment:9 Changed 3 years ago by perost

  • Milestone changed from Future to 1.16.0
  • Resolution set to worksforme
  • Status changed from assigned to closed

I assume this ticket is no longer revelant.

comment:10 Changed 3 years ago by dersh

I agree. I haven't seen this problem in a long time.

Note: See TracTickets for help on using tickets.