do you have? Give specifics. Your
entire rambling email does not actually describe a single issue with clang,
nor UsingTheRightCompiler (which is about getting ports to respect
${configure.compiler}, not about you setting what you want for
configure.compiler.
Its ugly. It causes more
On Apr 17, 2012, at 4:16 p.m., Jeff Singleton wrote:
If its not Clang as you suggest, and you think its a linking issue, then it
is a Macports problem. I don't mix my architectures. My macports.conf either
says build_arch i386 or it says build_arch x86_64. I don't add anything to
the
On Apr 16, 2012, at 11:51 a.m., Jeff Singleton wrote:
If you are able to build Pango weekly…then you must be doing something
differently that I. Possibly not using the same Arch/Platform or possibly
you customize your Portfile prior to building. My issues stem from the
default Portfile
Nope. Sorry. But the it works for me argument just isn't going to work.
Continuing to chant it doesn't work is just as helpful. Post logs detailing
your issues and point them out. You've been asked to do this a couple times now.
Without those, the whole thread appears useless.
I have tried
this before. I have
taken many suggestions. Tried Tried and Tried some more to like Clang.
clang is awesome. What problems do you have? Give specifics. Your entire
rambling email does not actually describe a single issue with clang, nor
UsingTheRightCompiler (which is about getting ports
On Apr 17, 2012, at 1:16 PM, Jeff Singleton gvib...@gmail.com wrote:
Nope. Sorry. But the it works for me argument just isn't going to work.
I have tried both i386 (32 bit) and x86_64…and have the same issues
(eventually) and IT IS because of Clang.
Prove it. File a bug, and I will fix
I'm not sure why the pango won't build portion of this thread is continuing,
since it's already been fixed:
https://trac.macports.org/ticket/32722
___
macports-users mailing list
macports-users@lists.macosforge.org
://trac.macports.org/wiki/UsingTheRightCompiler
I just can't say a lot for Clang. I have mentioned this before. I have
taken many suggestions. Tried Tried and Tried some more to like Clang.
I just can't do it.
Its ugly. It causes more problems between ports that depend on one
another, yet
On Apr 15, 2012, at 23:04, Jeff Singleton wrote:
I just can't say a lot for Clang. I have mentioned this before. I have
taken many suggestions. Tried Tried and Tried some more to like Clang.
I just can't do it.
Its ugly. It causes more problems between ports that depend on one
Hi everybody,
Le 16 avr. 2012 à 09:00, Ryan Schmidt ryandes...@macports.org a écrit :
On Apr 15, 2012, at 23:04, Jeff Singleton wrote:
I just can't say a lot for Clang. I have mentioned this before. I have
taken many suggestions. Tried Tried and Tried some more to like Clang.
I
On Apr 16, 2012, at 04:46, vincent habchi wrote:
By the way, is it possible to add GCC 4.7 as a possible compiler?
That's in 2.1.0 beta 1:
https://trac.macports.org/browser/tags/release_2_1_0-beta1/base/ChangeLog#L7
___
macports-users mailing list
There simply HAS to be some way of forcing Macports to use the compiler that
I want to use and not argue and not make changes whenever and just do what I
tell it to.
There is a default compiler option in trunk, but no one is having the issues
you are (I build pango weekly to make installers
If you had read my entire email you would have seen that I have tried
building (rebuilding) everything again.
I guess the reason I am asking for what I am … is that (for example), the
less popular HomeBrew for OS X offers methods for using GCC (a switch for
'install --use-gcc') as my preferred
Clang also compiles way faster for me, and the binaries are faster. I'd
like to keep GCC only to where clang breaks.
Mark
On Mon, Apr 16, 2012 at 11:51 AM, Jeff Singleton gvib...@gmail.com wrote:
If you had read my entire email you would have seen that I have tried
building (rebuilding)
rambling email does not actually describe a single issue with clang, nor
UsingTheRightCompiler (which is about getting ports to respect
${configure.compiler}, not about you setting what you want for
configure.compiler.
Its ugly. It causes more problems between ports that depend on one
another
15 matches
Mail list logo
