llvm-devel: update to 2.6 pre-release or mark as replaced_by llvm

[ryandesign (Ryan Carsten Schmidt)]

Could you please update llvm-devel to a version of the forthcoming LLVM 2.6? Pre-release 1 of LLVM 2.6 is available; pre-release 2 should be available 2009-09-11. Albert Graef, author of the ​Pure language, ​says I need LLVM 2.6 to be able to update to pure version 0.35.

From: Albert Graef <Dr.Graef@…>
Date: September 6, 2009 19:13:22 CDT
To: pure-lang@…
Subject: [pure-lang] Re: ANN: Pure 0.33
Reply-To: pure-lang@…

• You need LLVM >= 2.6 (pre1 works fine, you can grab this at

​http://llvm.org/prereleases/2.6/; trunk works fine, too). LLVM 2.5 won't work, as it generates broken code for double constants on ppc (symptom is a failed check in Pure test020). Make sure that you configure LLVM (at least) with --disable-expensive-checks, otherwise you'll hit the bogus assertions mentioned above.

See also #21173 for my request to add --disable-assertions and --disable-expensive-checks to llvm and llvm-devel.

[ryandesign (Ryan Carsten Schmidt)]

Replying to ryandesign@…:

I need LLVM 2.6 to be able to update to pure version 0.35

...on PowerPC. On Intel, the existing version is fine.

[erickt@…]

Committed, finally! Sorry for the delay.

[ryandesign (Ryan Carsten Schmidt)]

I see you updated llvm to 2.6 final in r60440, but did not update llvm-devel, which is what this ticket was for. Now that llvm is up to 2.6 final the need to update llvm-devel is less pressing. Still, it might make sense to either update llvm-devel, or remove it. If you don't wish to touch llvm-devel at this time, feel free to close this ticket as wontfix.

[erickt@…]

You know, I think pguyot handled the llvm-devel stuff. There's a file pguyot uploaded, and I'm not sure how do update it. Hopefully he/she can help.

[ryandesign (Ryan Carsten Schmidt)]

Paul had been a secondary maintainer for llvm-devel but he removed himself in r59973 leaving you as the sole maintainer. Which file are you referring to?

[erickt@…]

It looks like there was a snapshot made of llvm's svn r53722 that got uploaded to macports.org, and I'm not sure how you're supposed to do that. Is there a doc somewhere on how to do that? I couldn't find anything on the wiki.

[ryandesign (Ryan Carsten Schmidt)]

Replying to erickt@…:

It looks like there was a snapshot made of llvm's svn r53722 that got uploaded to macports.org, and I'm not sure how you're supposed to do that. Is there a doc somewhere on how to do that? I couldn't find anything on the wiki.

We only upload distfiles to the MacPorts repository if it isn't available elsewhere. I'm not sure why that was done here for llvm's svn source; the port could have just been set to fetch directly from their svn. But to answer the question, if you need to upload a distfile to our repository, then you simply use normal svn commands to do that. Looks like the llvm-devel distfile is in the directory "pguyot" in the distfiles directory. That's not usual; usually the directory name should be the port name. So in this case I would make an "llvm" directory ("svn mkdir http://svn.macosforge.org/repository/macports/distfiles/llvm"), check it out ("svn co http://svn.macosforge.org/repository/macports/distfiles/llvm"), put the distfile in there ("cp /path/to/llvm-12345.tar.bz2 llvm"), add it ("svn add llvm/llvm-12345.tar.bz2") and commit it ("svn ci llvm").

[macports@…]

The llvm-devel port should probably get marked as replaced_by llvm. This and several related enhancements are available in #24112

[mfeiri]

Marked as "replaced_by llvm" in r72199

[ryandesign (Ryan Carsten Schmidt)]

You must do a lot more than just add the "replaced_by" line to resolve this issue. Please see instructions in PortfileRecipes.

[ryandesign (Ryan Carsten Schmidt)]

Fixed in r78416 (maintainer timeout)