Issue with sundials macports

[Francesco Casella]

The MacOSX nightly is broken since 12 Oct. Seems to be a sundials port issue. This should be fixed prior to the 1.13.0 release.

[Adam Dershowitz]

About a month ago there was an "upgrade" to the Sundials port that caused a build problem. There is a ticket and a work around:
[​https://trac.macports.org/ticket/57358#comment:12
]

And, I can now build and run openmodelica-devel fine on my Mac.

[Francesco Casella]

@dersh, could you help fixing this issue via a PR on GitHub?

[Adam Dershowitz]

I've updated the ticket to see if I can get more information about sundials. I'm not clear about the status of that ticket.

[Adam Dershowitz]

The error showing up for nightly suggests that just cleaning the port on the server might allow it to build:

sudo port clean sundials

For me, what had allowed sundials to build was to edit the sundials portfile by just adding this to the file:

configure.fflags-append {*}${configure.f77_archflags}

Although, it doesn't now appear that sundials is listed as a dependent of openmodelica.

So, I'm really not sure how to issue a PR for this.

[Adrian Pop]

@dersh, where should I make the modification? Where is the sundials portfile located?

[Adam Dershowitz]

The port file should be something like this:

/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/math/sundials/Portfile

It is just a text file that is build instructions for the port. If you insert this:

configure.fflags-append {*}${configure.f77_archflags}

then hopefully, the sundials port should now build.
But, I'm not sure if the path is the same on the build server. I'm also not sure when the build server does a sync to macports, which would overwrite the Portfile. So, I'm can't provide all the fix details.

[Adrian Pop]

Ok. I edited another one which was here:

/opt/openmodelica/var/macports/registry/portfiles/sundials-3.1.2_0/fd62ace036663315a57fe70bb1b98ce7eb0e7e43aa0fa75ce34aeaa048e16f29-6007/Portfile

and that didn't work.

I'll try yours.

[Adam Dershowitz]

I'll also add, that there is another oddity. My recollection is the sundials is a dependent of openmodelica-devel. But, it isn't indicated as being one in the openmodelica-devel port. Further, one can see the dependent tree like this:

$port rdeps openmodelica-devel
The following ports are dependencies of openmodelica-devel @1.13.0~dev-1812-ga861c45_0+gfortran5+omnotebook+qt:
  gtime
  gsed
    xz
      libiconv
        gperf
      gettext
        ncurses
  cmake
    libcxx
    curl
      pkgconfig
      libidn2
        autoconf
        automake
        libtool
          xattr
            unzip
        libunistring
          perl5
            perl5.26
              gdbm
                readline
          texinfo
            help2man
              p5.26-locale-gettext
      libpsl
        python27
          bzip2
          db48
          expat
          libedit
          libffi
          openssl
            zlib
          sqlite3
          python_select
          python2_select
        glib2
          libxml2
          pcre
      curl-ca-bundle
    libarchive
      lzo2
      lz4
    libuv
  lp_solve
  omniorb
    python36
      python3_select
  qjson
    qt4-mac
      dbus
      tiff
        jpeg
        zstd
      libpng
      libmng
        lcms2
  ossp-uuid
  boost
    icu
  libgcc
    libgcc8
      cctools
        libunwind-headers
        llvm-7.0
          xar
          llvm_select
      gmp
      isl
      ld64
        ld64-xcode
      libmpc
        mpfr
  gcc5
    isl18
    gcc_select
    libgcc6
      libgcc7
  qwt52
  omlib-modelica-3.2.1

and it doesn't indicate that sundials is being used. So, I'm not sure exactly why the mismatch, or what to do about it. To be clear I do have sundials installed, and openmodelica-devel is installed and working fine, on my computer.

[Adrian Pop]

Same issues, i get a sundials config error:

:info:configure CMake Error at config/SundialsCMakeMacros.cmake:94 (MESSAGE):
:info:configure   ************************************************************
:info:configure   ERROR: FFLAGS='-pipe -Os' and FCFLAGS='-pipe -Os -m64' are both set but are
:info:configure   not equal.
:info:configure   ************************************************************

Somehow the FFLAGS append you suggested fails to add -m64.

There should be no need for sundials from the system, we compile our own from 3rdParty.

[Adrian Pop]

Ah, it doesn't work because we rsync during the job and the Portfile with my changes is overwritten.

[Adrian Pop]

I managed to change the file after the overwrite and before the build and that worked fine.
We'll see if it works now, the job is building.

[Adrian Pop]

Seems to be working now. I will keep this ticket open until the macports are fixed at the source.

[Francesco Casella]

No longer a blocker since we have a running workaround

[Francesco Casella]

Rescheduled to 1.14.0 after 1.13.0 releasee

[Francesco Casella]

Releasing 1.14.0 which is stable and has many improvements w.r.t. 1.13.2. This issue is rescheduled to 1.16.0

[Francesco Casella]

Retargeted to 1.17.0 after 1.16.0 release

[Francesco Casella]

Retargeted to 1.18.0 because of 1.17.0 timed release.

[Francesco Casella]

Ticket retargeted after milestone closed