On 24 Apr 2013, at 00:55, Lawrence Velázquez lar...@macports.org wrote:
In any case, Apple has never released a compiler versioned at 4.7, so it's
still not clear to me what René is referring to.
vq
Undoubtedly a slip of the finger, sorry about that!
Are there any differences between the
On Apr 24, 2013, at 01:18, RenE J.V. Bertin wrote:
On 24 Apr 2013, at 00:55, Lawrence Velázquez wrote:
In any case, Apple has never released a compiler versioned at 4.7, so it's
still not clear to me what René is referring to.
Undoubtedly a slip of the finger, sorry about that!
Are
Hi,
it appears atlas does as well… so it has both mpclang33 and clang33 ….
You can see from port variants atlas that's not so. The pseudoport syntax
variants:clang33 means ports whose list of variants *contains* the string
clang33. Pseudoport syntax uses regular expressions.
On Apr 22, 2013, at 21:23, Ned Deily wrote:
That's correct. xcode-select sets the defaults that are used by several
other build tools, primarily xcodebuild and xcrun but it has no effect
on what is installed in system locations. If you allowed the Xcode 4.2
Yes. xcode-select is just a
In article 0307d314-6374-4fbb-ac6d-7e229a5ba...@gmail.com,
Rene J.V. Bertin rjvber...@gmail.com wrote:
On Apr 22, 2013, at 21:23, Ned Deily wrote:
That's correct. xcode-select sets the defaults that are used by several
other build tools, primarily xcodebuild and xcrun but it has no effect
On Apr 23, 2013, at 08:46, René J.V. Bertin wrote:
I must admit I hadn't thought about universal build implications of choosing
a non-Apple compiler. Curiously, the first port of which I installed a
universal variant was ffmpeg, and that package cannot (easily) be built as
universal by
On Apr 22, 2013, at 12:00, Chris Jones wrote:
yes. and no…. other ports use the more standard 'clangXY' variant naming (to
match the gccXY names).
Chris-Jones-Macbook-Pro ~ port list variants:clang33
atlas @3.10.1 math/atlas
root
On Apr 23, 2013, at 17:57, Ned Deily wrote:
Out of curiosity: is gcc-4.2 the last compiler for which Apple made it
possible to build it on systems where you cannot obtain the binaries
directly
from Apple? If so, are there any plans to provide ports of those compilers
(supposing there's
On Apr 23, 2013, at 5:02 PM, René J.V. Bertin rjvber...@gmail.com wrote:
I saw that Apple's clang is at 4.7 or thereabouts. I guess (naively?) it'd be
nice to have access to the latest Apple compiler(s) even if Apple don't
support (= provide) it for older OSes.
What? The Apple LLVM Compiler
On Tue, Apr 23, 2013 at 05:38:43PM -0400, Lawrence Velázquez wrote:
What would be the benefit of providing a port for Apple LLVM Compiler
4.2?
The benefit would be that ports that still do not build correctly with
clang will also build after Xcode 4.7 has been released without llvm-gcc
4.2, and
On Apr 23, 2013, at 17:49, Clemens Lang wrote:
On Tue, Apr 23, 2013 at 05:38:43PM -0400, Lawrence Velázquez wrote:
What would be the benefit of providing a port for Apple LLVM Compiler
4.2?
The benefit would be that ports that still do not build correctly with
clang will also build after
On Apr 23, 2013, at 6:49 PM, Clemens Lang c...@macports.org wrote:
On Tue, Apr 23, 2013 at 05:38:43PM -0400, Lawrence Velázquez wrote:
What would be the benefit of providing a port for Apple LLVM Compiler
4.2?
The benefit would be that ports that still do not build correctly with
clang
Hello,
I've been using MacPorts for years now, under 10.6 (which I'm still running).
To my knowledge it has always used Apple's gcc-42 for building, and never
attempted to install a duplicate copy of that compiler.
I've installed XCode 4.2 *in parallel to my Xcode 3x* the other day, and today
Probably related to my previous question: ports now also seems to insist on
using clang as its compiler, despite the fact that *once more* I did
port select --set gcc gcc42
I already had to make /usr/bin/clang point to the 3.0 version that got
installed with Xcode 4 to get other projects to
On Mon, Apr 22, 2013 at 11:07:39AM +0200, René J.V. Bertin wrote:
I've been using MacPorts for years now, under 10.6 (which I'm still
running). To my knowledge it has always used Apple's gcc-42 for
building, and never attempted to install a duplicate copy of that
compiler.
I've installed
On Apr 22, 2013, at 14:08, Clemens Lang wrote:
Which version of MacPorts are you running? Do you use MacPorts trunk?
What port are you trying to install when MacPorts attempts to install
apple-gcc42?
I'm at 2.1.3, I've been keeping the tree up to date with selfupdate and upgrade
outdated.
On Mon, Apr 22, 2013 at 02:35:45PM +0200, René J.V. Bertin wrote:
The culprit port is ffmpeg in its universal variant.
Yes, see this part from the ffmpeg Portfile:
if {[lsearch [get_canonical_archs] i386] != -1} {
# clang-3.1 hits https://trac.macports.org/ticket/30137
On Apr 22, 2013, at 15:12, Clemens Lang wrote:
The port specifically blacklists clang and llvm-gcc and the next in the
fallback list seems to be apple-gcc, which Xcode 4.2 apparently doesn't
have, which causes the Portfile to add a dependency on MacPorts' version
of it.
I'm sure there's a
On Mon, Apr 22, 2013 at 10:16 AM, René J.V. Bertin rjvber...@gmail.comwrote:
As said, if there is, this is unsupported. You should instead file bugs
for the ports that break with clang so they can have clang or broken
versions of it selectively blacklisted.
Sure, but apart from that a
On Apr 22, 2013, at 17:47, Brandon Allbery wrote:
Ask yourself this: is your use case so *very* important that users who are
not as advanced as you --- which is to say, most of the MacPorts userbase ---
should be inconvenienced or even be left with a broken system, so that your
use case
At 6:26 PM +0200 4/22/13, René J.V. Bertin wrote:
On Apr 22, 2013, at 17:47, Brandon Allbery wrote:
Ask yourself this: is your use case so *very*
important that users who are not as advanced as
you --- which is to say, most of the MacPorts
userbase --- should be inconvenienced or even
be
On 2013-04-22 16:16, René J.V. Bertin wrote:
As said, if there is, this is unsupported. You should instead file bugs
for the ports that break with clang so they can have clang or broken
versions of it selectively blacklisted.
Sure, but apart from that a user can have good reasons to use a
Hi,
You could set a default variant (say +mpclang33, for example) and then any
port you install that offers that variant would do what you wanted. (Ironic
twist: only one port--atlas--offers a mpclang33 variant! gcc46 is more
common, there are 106 ports with that variant. You can see
On Apr 22, 2013, at 10:16 AM, René J.V. Bertin rjvber...@gmail.com wrote:
On Apr 22, 2013, at 15:12, Clemens Lang wrote:
While it is uncommon to have multiple Xcode versions I guess if you have
a patch to fix this we'd be happy to apply it.
As I said, I executed xcode-select /Developer to
On Apr 22, 2013, at 10:16 AM, René J.V. Bertin rjvber...@gmail.com wrote:
I don't see however why macports-clang-3.3 isn't accepted; I have it
installed?
None of the compiler precedence lists contains macports-clang-3.3. If you'd
like, you can view the current lists yourself:
2.1.3 release:
On Apr 22, 2013, at 1:38 PM, Lawrence Velázquez lar...@macports.org wrote:
Be aware that building a MacPorts-provided GCC
Building WITH a MacPorts-provided GCC, that is.
vq
___
macports-users mailing list
macports-users@lists.macosforge.org
In article ff6b7ac5-a89f-4ae1-9aa9-7bf5b173b...@macports.org,
Lawrence Velázquez lar...@macports.org wrote:
On Apr 22, 2013, at 10:16 AM, René J.V. Bertin rjvber...@gmail.com wrote:
On Apr 22, 2013, at 15:12, Clemens Lang wrote:
While it is uncommon to have multiple Xcode versions I guess
27 matches
Mail list logo
