Re: UsingTheRightCompiler
With xcode 4.2 (or 4.1 or 4.0) Apple did away with gcc and only brings llvm-gcc and clang. By default MacPorts uses the compiler that comes with Xcode and only uses a macports compiler when the xcode compilers don't work at all. And when people are using Lion, they are likely to have Xcode 4.x installed. That said, pango installs fine via default macports for me. And clang works fine on the projects I compile on my own. Dom Am 16.04.2012 um 08:08 schrieb Jan Stary h...@stare.cz: On Apr 15 23:04:58, Jeff Singleton wrote: Yes I am referring to the Wiki article found here... http://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 some are built with Clang, other built with GCC. I am simply fed up with Clang and I don't really want to use it anymore. *libtool: link: /usr/bin/clang -o .libs/pango-basic-coretext.so I must be missing something, but why do you even have clang installed on your system? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: use a different default configure.compiler (was: UsingTheRightCompiler)
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 another, yet some are built with Clang, other built with GCC. I've not heard of any problems related to some ports being built with clang and others built with other compilers; if you have examples of this please let us know. I am simply fed up with Clang and I don't really want to use it anymore. Clang does't respect architecture settings, no matter which I use (i386 or x86_64). clang of course does respect -arch settings. If individual ports that are compiling with an Xcode compiler (gcc-4.2, llvm-gcc-4.2 or clang) do not respect -arch settings, please file bug reports against those ports. (MacPorts gcc compilers do not respect -arch flags, so ports that use them cannot be made to respect -arch flags either.) Case and point - Pango crashes during compile no matter which Arch I use: libtool: link: /usr/bin/clang -o .libs/pango-basic-coretext.so -bundle .libs/basic-coretext.o -framework Carbon -L/opt/local/lib -O2 -arch x86_64 -arch x86_64 -framework Carbon -Wl,-exported_symbols_list,.libs/pango-basic-coretext-symbols.expsym Undefined symbols for architecture x86_64: snip unnecessary error output ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) I am just sick of running into linking errors -- either they happen now, or they happen eventually during an upgrade. Either way, I usually end up getting frustrated, and wiping out my whole ports tree, and attempt to rebuild from scratch. In this case…I still hit that link error with Pango. The unnecessary error output you snipped above might have been just what we needed to know whether this is a problem we've seen before or not. I have a feeling this is #32722 — which is not clang-specific, by the way; I see it on my Snow Leopard machine too, using gcc-4.2. The problem here is the quartz and/or no_x11 variants. I have enlisted the help of the pango developers in understanding why this is happening and how to fix it. Would someone PLEASE just tell me how I can force the default compiler to be GCC. No configure.compiler does not work, and no environment variables CC CPP CXX do not work. I have both set to gcc-4.2 and yet Pango still defaults to use Clang and crashes no matter what I try. I don't want to edit every single Portfile when I hit this issue, because when I sync again, my changes go away. 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. Is that so much to ask? Can I please just use GCC and never EVER have to see another Clang linking error again. PLEASE!???! As of MacPorts 2.1.0 beta 1 yes you can override the default value of configure.compiler than MacPorts chose for you, so feel free to upgrade to that version and change the appropriate value in macports.conf. Note that individual ports might specify an alternate compiler, if it is already known that using a particular compiler will not work (but I can't think of many ports that wouldn't work with Apple gcc 4.2). Note that Xcode 4.2 and up no longer include any Apple gcc compilers, so you cannot set configure.compiler to gcc-4.2 if you have Xcode 4.2 or later. You can however install the apple-gcc42 port, which is basically the same thing, and set configure.compiler to apple-gcc-4.2. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: use a different default configure.compiler (was: UsingTheRightCompiler)
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 just can't do it. Its ugly. It causes more problems between ports that depend on one another, yet some are built with Clang, other built with GCC. I've not heard of any problems related to some ports being built with clang and others built with other compilers; if you have examples of this please let us know. My own experience is that Clang works fine. LLVM based tools are now used extensively, be it by Apple for traditional GCC substitution, or by other companies like, e.g. NVidia for its OpenGL JIT compiler. LLVM is modern, extensible, modular and easily ported to any hardware whereas GCC is hoary, monolithic and totally cryptic, let alone code documentation. The only drawback I still see to the use of Clang is its inferior performance when it comes to floating point brute force. In fact, I carried out some tests with Clang on Atlas latest development version. Good news is that Clang works fine, even with AVX assembly; Bad news is that performance is still worse than GCC, sometimes by more than 40%, at least on Linux. On OS X, no comparison is possible since the provided assembler ‘/usr/bin/as’ is antiquated and does not recognize AVX instructions, and using Clang as an assembler fails because GCC emits non Intel compliant instructions that llvm-mc does not recognize. This might be slightly different on OS X because since LLVM is basically Apple driven there might be additional optimizations enabled for Darwin. But there is still room for additional improvements. Additional tools like a new linker, lld, are underway; It will eventually replace ld64. By the way, is it possible to add GCC 4.7 as a possible compiler? Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: use a different default configure.compiler (was: UsingTheRightCompiler)
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 macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: UsingTheRightCompiler
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 for PSPP). Have you tried rebuilding all your packages? smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: use a different default configure.compiler
On Apr 16, 2012, at 02:00, Ryan Schmidt wrote: 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. As of MacPorts 2.1.0 beta 1 yes you can override the default value of configure.compiler than MacPorts chose for you, so feel free to upgrade to that version and change the appropriate value in macports.conf. Note that individual ports might specify an alternate compiler, if it is already known that using a particular compiler will not work (but I can't think of many ports that wouldn't work with Apple gcc 4.2). Note that Xcode 4.2 and up no longer include any Apple gcc compilers, so you cannot set configure.compiler to gcc-4.2 if you have Xcode 4.2 or later. You can however install the apple-gcc42 port, which is basically the same thing, and set configure.compiler to apple-gcc-4.2. What I forgot to add is that the ability of MacPorts to influence what compiler a port will use (whether that's MacPorts' default value of configure.compiler or one you set yourself in macports.conf or on the command line when installing an individual port) depends on that port respecting the configure.compiler variable, which is what the UsingTheRightCompiler wiki page is all about. If you discover a port that does not respect configure.compiler (and I'm sure there are still several), please file a ticket in the issue tracker referencing that wiki page (assuming one has not already been filed) so someone can look into fixing the port. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: UsingTheRightCompiler
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 compiler, and not defaulting to Apple's default compiler. I just was hoping that the maintainers for the overall MP sources would create something similar. 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 and using MacPorts pretty much as is, with some minor variant changes and setting x86_64 only as my build_arch. (Though I have tried i386 and get the same results). Jeff On Mon, Apr 16, 2012 at 5:33 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: 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 for PSPP). Have you tried rebuilding all your packages? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
I need to instal gap in Macos tiger
Hi everyone, I need to instal plugins GAP for GIMP, in MACOS, tiger 10.4. iMac4,1 Intel Core Duo Thanks a lot! Cordialment, Rosa M. Alonso Garcia Il.lustradora gràfica http://rosailustradora.com http://rosailustradora.blogspot.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: UsingTheRightCompiler
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) 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 compiler, and not defaulting to Apple's default compiler. I just was hoping that the maintainers for the overall MP sources would create something similar. 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 and using MacPorts pretty much as is, with some minor variant changes and setting x86_64 only as my build_arch. (Though I have tried i386 and get the same results). Jeff On Mon, Apr 16, 2012 at 5:33 AM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: 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 for PSPP). Have you tried rebuilding all your packages? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: I need to instal gap in Macos tiger
On Apr 16, 2012, at 11:13, Rosa Alonso Garcia wrote: I need to instal plugins GAP for GIMP, in MACOS, tiger 10.4. Ok. Then I guess you want: sudo port install gimp-gap No idea if gimp-gap, or gimp itself, works on Tiger anymore. Tiger is very old and becoming less well supported in MacPorts all the time. iMac4,1 Intel Core Duo Your Mac can be upgraded to Snow Leopard, and I would highly recommend considering doing that. You'll have less trouble getting new software. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: I need to instal gap in Macos tiger
Please remember to Reply All to keep the conversation on the mailing list. On Apr 16, 2012, at 13:51, Rosa Alonso Garcia wrote: Your Mac can be upgraded to Snow Leopard, and I would highly recommend considering doing that. You'll have less trouble getting new software. Thanks a lot. But it's no possible nowadays. If you wanted to, I'm certain you could locate a used copy that someone would be willing to sell you. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Which version of Wine, or am I on the wrong track?
On Apr 15, 2012, at 10:56 AM, Michael_google gmail_Gersten wrote: I am not sure which version of Wine to install from Macports (there are three), or if this is even the right approach for what I want to do. The goal: Edit a movie (screen recording), from the view that 80-90% of what I recorded will be tossed. iMovie is a failure (as far as I can tell) as selecting sections and removing them. Pretty sure you can cut frames with iMovie. This means I'm going to use VirtualDub (only program I've found so far that is good at selecting lots of specific frame ranges and tossing them). There are going to be better options for video editing on the Mac then running a Windows program. Quicktime Pro Player has been able to cut video many years. The pro version used to cost $35. Have you looked at the MacPorts ports for Avidemux and Kdenlive. Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Error: Dependency 'p5.12-locale-gettext' not found.
I am on version 2.0.4 Several times, I have tried 'sudo port selfupdate' per Trac ticket #30801 After it ran, I ran: sudo port upgrade outdated I received: Error: No ports matched the given expression I am trying to run 'sudo port install libtool' When I do this (or any other install), I get: --- Computing dependencies for libtool Error: Dependency 'p5.12-locale-gettext' not found. Error: Status 1 encountered during processing. To report a bug, see http://guide.macports.org/#project.tickets Can anyone provide any other suggestions? Thanks! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Dependency 'p5.12-locale-gettext' not found.
On Apr 16, 2012, at 16:06, Stephen Blackmore wrote: I am on version 2.0.4 Several times, I have tried 'sudo port selfupdate' per Trac ticket #30801 After it ran, I ran: sudo port upgrade outdated I received: Error: No ports matched the given expression I am trying to run 'sudo port install libtool' When I do this (or any other install), I get: --- Computing dependencies for libtool Error: Dependency 'p5.12-locale-gettext' not found. Error: Status 1 encountered during processing. To report a bug, see http://guide.macports.org/#project.tickets Can anyone provide any other suggestions? Can you show the output of sudo port -v selfupdate? ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Which version of Wine, or am I on the wrong track?
On 16/04/2012, at 10:00 PM, macports-users-requ...@lists.macosforge.org wrote: I am not sure which version of Wine to install from Macports (there are three), or if this is even the right approach for what I want to do. The goal: Edit a movie (screen recording), from the view that 80-90% of what I recorded will be tossed. iMovie is a failure (as far as I can tell) as selecting sections and removing them. This means I'm going to use VirtualDub (only program I've found so far that is good at selecting lots of specific frame ranges and tossing them). And this means I'm going to need either XviD or DivX for Windows (or am I wrong?) Note that the standard apple mp4 encoder does not produce good enough quality. A quick look shows three different, incompatible versions of wine, with different sets of patches and features. Additionally, Crossover has their commercial version with their keep everything separate/bottles feature. So what's the proper version of Wine, to get VirtualDub and Divx or Xvid, and has anyone already done this and knows what warnings to watch out for? YMMV but I was unable to do any editing under wine. I did three things ... Install vbox from oracle. BUY a copy of XP and use that. Worked well. Get a native dmg of avidemux which has a nice transcode stack and works well. install ffmpeg from macports (I think it includes mjpegtools, but in any event mjpegtools) which worked very very well. Needless to say I am a CLI geek and ffmpeg has a CLI from hell. See http://www.gentoo-wiki.info/MEncoder/Tips_and_Tricks which was also useful to me. James ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error: Dependency 'p5.12-locale-gettext' not found.
On Apr 16, 2012, at 16:36, Stephen Blackmore wrote: On Mon, Apr 16, 2012 at 5:15 PM, Ryan Schmidt wrote: On Apr 16, 2012, at 16:06, Stephen Blackmore wrote: I am on version 2.0.4 Several times, I have tried 'sudo port selfupdate' per Trac ticket #30801 Can you show the output of sudo port -v selfupdate? Thanks for the suggestion!! Rather than say what all it printed, I will just say that after running this and then rerunning the install, it worked. I am new to macports, so I really appreciate your help! Hmm, interesting. I'm glad you got it working, though I'm not clear on what fixed it. Running sudo port selfupdate any time in the past twelve months should have fixed it, since the p5 ports were changed to p5.8/p5.10/p5.12/p5.14 ports over a year ago; the fact that you said you ran it and it did not help suggested to me that some hidden error was occurring, and running with -v should have shown us that error. But since none occurred, and your problem has been resolved, I guess we should just leave it at that! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: UsingTheRightCompiler
On Apr 15, 2012, at 9:04 PM, Jeff Singleton gvib...@gmail.com 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.
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 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, yet some are built with Clang, other built with GCC.
There are no problems here. Binaries built with clang are compatible with
those built by other compilers. What specific issues are you seeing?
I am simply fed up with Clang and I don't really want to use it anymore.
Clang does't respect architecture settings, no matter which I use (i386 or
x86_64).
Yes it does. It respects them better than gcc (which doesn't btw, it's Apple's
driver-driver that parses those).
Case and point - Pango crashes during compile no matter which Arch I use:
That's not a crash.
*libtool: link: /usr/bin/clang -o .libs/pango-basic-coretext.so -bundle
.libs/basic-coretext.o -framework Carbon -L/opt/local/lib -O2 -arch
x86_64 -arch x86_64 -framework Carbon
-Wl,-exported_symbols_list,.libs/pango-basic-coretext-symbols.expsym*
*Undefined symbols for architecture x86_64:*
*snip unnecessary error output*
*ld: symbol(s) not found for architecture x86_64*
*clang: error: linker command failed with exit code 1 (use -v to see
invocation)*
Yous snipped out necessary output. This is not a clang issue. It's a linking
issue. The problem has *NOTHING* to do with clang. You probably have an i386
library installed that you're trying to link into an x86_64 binary.
I am just sick of running into linking errors -- either they happen now, or
they happen eventually during an upgrade. Either way, I usually end up
getting frustrated, and wiping out my whole ports tree, and attempt to
rebuild from scratch.
Ok, that's one way to deal with it, but this has nothing to do with clang, and
you should report individual linking issues separately. There's probably a
missing dependency somewhere, or something was built +universal but it actually
is thinned to i386 because the *port* doesn't support +universal (again,
nothing to do with clang).
In this case…I still hit that link error with Pango.
Please file a bug with the full output (including the relevant sections that
you commented out as unnecessary)
Would someone PLEASE just tell me how I can force the default compiler to
be GCC.
Use trunk base, but there's no way I'm going to support you using anything
other than clang on modern systems.
No configure.compiler does not work
yes it does.
, and no environment variables
CC CPP CXX do not work.
No, they don't
I have both set to gcc-4.2 and yet Pango still
defaults to use Clang and crashes no matter what I try.
It doesn't crash. Also the fact that it fails despite you setting it to
gcc-4.2 should prove to you that it has NOTHING to do with clang.
I don't want to edit every single Portfile when I hit this issue, because
when I sync again, my changes go away.
That would be stupid.
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.
Is that so much to ask? Can I please just use GCC and never EVER have to
see another Clang linking error again.
clang doesn't have linking errors. clang doesn't link. ld64 links, and guess
what, gcc-4.2 uses the same linker as clang.
--Jeremy
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
