Opened 6 years ago

Closed 6 years ago

#46894 closed defect (fixed)

clang-3.7 @3.7-r229298_0+analyzer+assertions no binaries available for Mavericks

Reported by: michele-segata (Michele Segata) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: mavericks Cc: ryandesign (Ryan Schmidt)
Port: clang-3.7 llvm-3.3 llvm-3.5 llvm-3.7

Description

Dear all,

I was doing an upgrade of my ports this morning (Mac OS X Mavericks) forcing the installation of binary packages only (port -pub upgrade outdated). From time to time, I obviously encounter failures because of missing binary packages, but before mac ports start compiling, I want to know which ports are going to be compiled, because some of them might take hours to build (e.g., clang-3.7 and libgcc). This time, however, all the ports failed to find a pre-compiled binary package (so the title of my post is not entirely correct, as it refers to clang-3.7 only). So I had a closer look at the upgrade for clang-3.7. I was upgrading from 3.7-r226372_0+analyzer+assertions (which was installed through binaries, not built) to 3.7-r229298_0+analyzer+assertions. Macports failed to fetch the binaries, so I had a look into http://packages.macports.org/clang-3.7 and I noticed that there exists binary packages for darwin12 and for darwin14, but not for darwin13 (the ones that I need). The same problem holds for llvm-3.3, llvm-3.5, llvm-3.7, and many more ports. I tried to have a look at the buildbot page as well, but I didn't get any useful information. Could you guys try to help me understanding what happened, or what's wrong?

Thank you in advance Michele

Change History (10)

comment:1 Changed 6 years ago by ryandesign (Ryan Schmidt)

Cc: ryandesign@… added
Keywords: binaries missing removed
Type: updatedefect

The Mavericks buildbot builder was recently offline for several days. It is up and running again now, but it looks like ports that were updated during the time it was offline did not get built. I will try to identify the list of affected ports and force a build.

comment:2 in reply to:  1 ; Changed 6 years ago by michele-segata (Michele Segata)

Replying to ryandesign@…:

The Mavericks buildbot builder was recently offline for several days. It is up and running again now, but it looks like ports that were updated during the time it was offline did not get built. I will try to identify the list of affected ports and force a build.

Thank you for your quick answer. Just as an information, by looking into http://packages.macports.org/clang-3.7/ it looks like the binaries for darwin 10 and 11 are missing as well.

Last edited 6 years ago by michele-segata (Michele Segata) (previous) (diff)

comment:3 in reply to:  2 ; Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to michele.segata@…:

Just as an information, by looking into http://packages.macports.org/clang-3.7/ it looks like the binaries for darwin 10 and 11 are missing as well.

Yes, but the reason is different. As far as I know, clang 3.5 and later do not support those old versions of OS X anymore.

comment:4 in reply to:  3 ; Changed 6 years ago by michele-segata (Michele Segata)

Replying to ryandesign@…:

Replying to michele.segata@…:

Just as an information, by looking into http://packages.macports.org/clang-3.7/ it looks like the binaries for darwin 10 and 11 are missing as well.

Yes, but the reason is different. As far as I know, clang 3.5 and later do not support those old versions of OS X anymore.

Sorry I was not giving enough details: the clang-3.7 binaries for the previous version (clang-3.7-3.7-r226372_0+analyzer+assertions), for darwin 10 and 11 are actually available in that folder. That's why I was telling you that the ones for the newest version were missing.

comment:5 Changed 6 years ago by ryandesign (Ryan Schmidt)

Let's start by dealing with the known recent unavailability of the Mavericks builder.
Looks like the first build that failed due to this problem was Mavericks build 10841 which was to have built r132903.
The last build that failed due to this problem was Mavericks build 10924 which was to have built r133006.
The ports affected by that range of revisions are:

  • FileZilla
  • MongoHub
  • MongoObjCDriver
  • adns
  • babl
  • cctools
  • cmake
  • ffmpeg
  • ffmpeg-devel
  • fltk
  • gcc5
  • geomview
  • gimp2-devel
  • gimp3-devel
  • git-cal
  • glm
  • gnuradio
  • ld64
  • libbson
  • libcaca
  • libgpg-error
  • libgpod
  • libpcl
  • liferea
  • liquid-dsp
  • llvm-3.3
  • llvm-3.4
  • llvm-3.5
  • llvm-3.6
  • llvm-3.7
  • minipro
  • mongo-c-driver
  • mongo-cxx-driver
  • mtr
  • npm
  • nspr
  • octave
  • openmpi
  • p5-app-cpanminus
  • p5-appconfig
  • p5-config-tiny
  • p5-error
  • p5-extutils-installpaths
  • p5-image-exiftool
  • p5-libwww-perl
  • p5-list-moreutils
  • p5-module-corelist
  • p5-mojolicious
  • p5-net-frame
  • p5-net-stomp
  • p5-palm
  • p5-palm-pdb
  • p5-params-validate
  • p5-plack-middleware-methodoverride
  • p5-text-autoformat
  • perl5
  • petsc
  • py-blaze
  • py-cairosvg
  • py-cython
  • py-datashape
  • py-into
  • py-ipython
  • py-llvmlite
  • py-llvmpy
  • py-pyglet
  • py-python-poppler-qt4
  • py-sphinx-contrib
  • qore-devel
  • qrupdate
  • rNMR
  • signify
  • splash
  • stunnel
  • surfraw
  • task
  • tellico
  • tmux
  • uhd
  • vcs_blackbox
  • vowpal_wabbit
  • xauth
  • xmp
  • xterm

(And their subports. The clang ports, for example, are subports of the corresponding llvm ports.)

I have started Mavericks build 10935 to build these ports. Assuming it works correctly, it will take many hours or even a day or more to complete. After it finishes, any available binaries will be automatically uploaded to the packages server.

comment:6 Changed 6 years ago by mf2k (Frank Schima)

Port: and more removed

comment:7 in reply to:  4 Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to michele.segata@…:

Sorry I was not giving enough details: the clang-3.7 binaries for the previous version (clang-3.7-3.7-r226372_0+analyzer+assertions), for darwin 10 and 11 are actually available in that folder. That's why I was telling you that the ones for the newest version were missing.

Snow Leopard build 33657 shows llvm-3.7 @3.7-r229298 failed to build. This problem is already reported in #42051.

Lion build 27032 shows llvm-3.7 @3.7-r229298 failed to build. This is a new problem which I have filed as #46897.

comment:8 in reply to:  5 ; Changed 6 years ago by ryandesign (Ryan Schmidt)

Replying to ryandesign@…:

I have started Mavericks build 10935 to build these ports. Assuming it works correctly, it will take many hours or even a day or more to complete. After it finishes, any available binaries will be automatically uploaded to the packages server.

This build finished. Here is the part of the log showing the packages that got uploaded: https://build.macports.org/builders/buildports-mavericks-x86_64/builds/10935/steps/deploy%20archives/logs/stdio

Is there anything else I need to do to resolve this ticket?

comment:9 in reply to:  8 Changed 6 years ago by michele-segata (Michele Segata)

Replying to ryandesign@…:

Replying to ryandesign@…:

I have started Mavericks build 10935 to build these ports. Assuming it works correctly, it will take many hours or even a day or more to complete. After it finishes, any available binaries will be automatically uploaded to the packages server.

This build finished. Here is the part of the log showing the packages that got uploaded: https://build.macports.org/builders/buildports-mavericks-x86_64/builds/10935/steps/deploy%20archives/logs/stdio

Is there anything else I need to do to resolve this ticket?

I tried upgrading this morning and I got all the binaries. For me the ticket can be marked as solved. Thanks for your help

comment:10 Changed 6 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.