Re: building from source with libc++

On 20 Apr 2017, at 22:54, Ken Cunningham wrote: > You’ve made clang-3.9 a build dep for everything by setting the default > compiler to clang-3.9. It will always be listed, for all ports. I often check dependencies and sizes with a couple of functions and these are now a mess. I suppose I coul

Re: building from source with libc++

> On Apr 20, 2017, at 1:01 PM, db wrote: > > `port rdeps` now lists clang-3.9 and so does `port space`, giving the wrong > size even for a port that's just composed of a couple shell scripts. > You’ve made clang-3.9 a build dep for everything by setting the default compiler to clang-3.9. It

Re: building from source with libc++

On 20 Apr 2017, at 20:06, Ken Cunningham wrote: > On 2017-04-20, at 10:42 AM, db wrote: >> Could you please tell me if you see the warning I mentionend and the >> following line in every `port info` result? >> Build Dependencies: clang-3.x > Yes i do see that too - because of the way you've se

Re: building from source with libc++

>> >> Specifically, try to build it with a stock clang compiler and see if that >> builds your port. If that does fix the build, please don't report it as a >> ticket > > That's not true. If an old compiler is not able to build a port, that > compiler should be blacklisted, so that the port w

Re: building from source with libc++

On 20 April 2017 at 19:01, Ken Cunningham wrote: > > Specifically, try to build it with a stock clang compiler and see if that > builds your port. If that does fix the build, please don't report it as a > ticket That's not true. If an old compiler is not able to build a port, that compiler shoul

Re: building from source with libc++

On 2017-04-20, at 10:42 AM, db wrote: > > Could you please tell me if you see the warning I mentionend and the > following line in every `port info` result? > > Build Dependencies: clang-3.x Yes i do see that too - because of the way you've set your default compiler to be clang-3.9, it has

Re: building from source with libc++

On 20 Apr 2017, at 19:01, Ken Cunningham wrote: > Now to be fair, IF you get a build problem, there are increased expectations > on you to check into it before you file a ticket about it. Specifically, try > to build it with a stock clang compiler and see if that builds your port. If > that do

Re: building from source with libc++

On 2017-04-20, at 7:47 AM, db wrote: > Both highlight and nmap installed right away. In the end, that's the desired outcome. Now to be fair, IF you get a build problem, there are increased expectations on you to check into it before you file a ticket about it. Specifically, try to build it wi

Re: building from source with libc++

On 20 Apr 2017, at 00:13, Ken Cunningham wrote: > I think the Lion and Mountain Lion LibCxxOnOlderSystems instructions could > probably suggest/recommend installing and setting the default compiler to > something newer, but I defer to the gurus here. After skimming the instructions for 10.6, t

Re: building from source with libc++

> On Apr 19, 2017, at 2:10 PM, db wrote: > > Are the other steps described in the LibcxxOnOlderSystems instructions for > 10.6 not necessary for 10.8? 10.8 already has /usr/lib/libc++.dylib installed, so you don’t need to go through the bootstrapping hoops to get that as you do on 10.6. Jus

Re: building from source with libc++

On 19 Apr 2017, at 18:22, Ken Cunningham wrote: > You're right, that option is not listed there. It is listed in the > LibCxxOnOlderSystems instructions, which is where I originally found it. > It looks like this, in macports.conf on my system. > default_compilers macports-clang-3.8 Are t

Re: building from source with libc++

On 19 April 2017 at 21:34, Ken Cunningham wrote: >> I'm currently fighting with cross-compiling (for i386 and ppc) on 10.6 >> and usually setting CC="gcc -arch ppc" is a much safer recipe than >> making sure that the software consistently switches to obeying CFLAGS. > > I had mentioned a while back

Re: building from source with libc++

> I'm currently fighting with cross-compiling (for i386 and ppc) on 10.6 > and usually setting CC="gcc -arch ppc" is a much safer recipe that > making sure that the software consistently switches to obeying CFLAGS. > I had mentioned a while back that I came across a project to bring Apple’s gcc

Re: building from source with libc++

t listed there. It is listed in the LibCxxOnOlderSystems instructions, which is where I originally found it. It looks like this, in macports.conf on my system. default_compilers macports-clang-3.8 > >> 2. properly setting the standard c++ library. > > I'm now always building

Re: building from source with libc++

Posting this to the developer list, it probably got too off-topic for the user list. On 19 April 2017 at 02:29, Ken Cunningham wrote: > > After coming across this issue one too many times for my own liking, and > changing several dozen ports as you have done, I finally just patched clang > to make

Re: building from source with libc++

On 19 Apr 2017, at 10:59, Chris Jones wrote: > You cannot really compare the stock LLVM/Clang releases to the Apple versions. I read https://trac.macports.org/wiki/UsingTheRightCompiler and this comment from Rainer, I guess, https://superuser.com/a/130474 and thus I'm not quite sure if this cha

Re: building from source with libc++

On 19/04/17 09:51, db wrote: On 19 Apr 2017, at 10:13, Mojca Miklavec wrote: https://trac.macports.org/wiki/XcodeVersionInfo That doesn't tell me anything different from the output I posted. I still don't exactly know which clang version I have. You cannot really compare the stock LLVM/C

Re: building from source with libc++

On 19 Apr 2017, at 10:13, Mojca Miklavec wrote: > https://trac.macports.org/wiki/XcodeVersionInfo That doesn't tell me anything different from the output I posted. I still don't exactly know which clang version I have. > You would run into problems if you installed/built existing ports against

Re: building from source with libc++

gt; > I'm now always building from source with libc++. > > If I change compiler, what are the odds that I run into some other oddities > with the installed ports built with the default compiler? You would run into problems if you installed/built existing ports against libstdc++ an

Re: building from source with libc++

ion in macports.conf? I don't seem to find the right option in the guide, https://guide.macports.org/chunked/internals.configuration-files.html. > 2. properly setting the standard c++ library. I'm now always building from source with libc++. If I change compiler, what are the odds

Re: building from source with libc++

> On 19 Apr 2017, at 10:29 am, Ken Cunningham > wrote: > Jeremy has previously indicated privately to me that he wasn’t too keen on > the idea due to possible unexpected consequences of changing default > behaviour, and this is a respectable point coming from the honcho himself. Jeremy: inte

Re: building from source with libc++

On 2017-04-18, at 8:54 AM, Mojca Miklavec wrote: >> >> After coming across this issue one too many times for my own liking, and >> changing several dozen ports as you have done, I finally just patched clang >> to make it default to add -stdlib=lilbc++ by default on all systems, which >> solves

Re: building from source with libc++

> > Newer systems will stumble on these ports as by default clang will add > -stdlib=libstdc++ and that doesn't work with cxx11; you get link errors. > > One typo, sorry -- this should say "Older systems will stumble on these ports ...", not "Newer systems will stumble on these ports ." my a

Re: building from source with libc++

On 18 April 2017 at 17:45, Ken Cunningham wrote: > > After coming across this issue one too many times for my own liking, and > changing several dozen ports as you have done, I finally just patched clang > to make it default to add -stdlib=lilbc++ by default on all systems, which > solves this i

Re: building from source with libc++

There are two issues: 1. cxx11 features required. These crop up in more and more software as these features are increasingly used. Newer systems breeze right past them as their default compiler is new enough to handle this. Older systems (10.8 or less) hang up on them as their default compiler

Re: building from source with libc++

On 18 Apr 2017, at 09:50, db wrote: > I filed #53994, #53995, #53996 for highlight, nmap and ostinato respectively, > failing to build with libc++. I'd appreciate if anyone could peek at the logs > and recognize a pattern or tell these are unrelated. highlight (#53994) and nmap (#53995) build w

Re: building from source with libc++

I filed #53994, #53995, #53996 for highlight, nmap and ostinato respectively, failing to build with libc++. I'd appreciate if anyone could peek at the logs and recognize a pattern or tell these are unrelated.

Re: building from source with libc++

On 9 Apr 2017, at 11:39, Ryan Schmidt wrote: > Whether or not you use non-default variants, you can either automate the > reinstallation of ports using the script mentioned in 3.e, or you can do it > manually. Ok, that tcl script states in the comments # Once "good enough", integrate into port

Re: building from source with libc++

> On Apr 9, 2017, at 04:36, db wrote: > > On 8 Apr 2017, at 03:27, Ryan Schmidt wrote: >> On Apr 1, 2017, at 09:35, db wrote: >>> Could someone from MP team shed some light on this, please? >> All of MacPorts is on a best-effort basis. There is no guarantee of >> anything. Most of us are volun

Re: building from source with libc++

On 8 Apr 2017, at 03:27, Ryan Schmidt wrote: > On Apr 1, 2017, at 09:35, db wrote: >> Could someone from MP team shed some light on this, please? > All of MacPorts is on a best-effort basis. There is no guarantee of anything. > Most of us are volunteers working on MacPorts in our spare time on wh

Re: building from source with libc++

On Apr 1, 2017, at 09:35, db wrote: > Could someone from MP team shed some light on this, please? All of MacPorts is on a best-effort basis. There is no guarantee of anything. Most of us are volunteers working on MacPorts in our spare time on whatever limited set of hardware we happen to have

Re: building from source with libc++

On 3 Apr 2017, at 18:09, Mojca Miklavec wrote: > Basically yes. You could follow point 3 of > https://trac.macports.org/wiki/Migration Is the script from 3.e. relevant if no particular variants were installed? I ask because I probably won't automate the whole process as I might have to check s

Re: building from source with libc++

On 2 April 2017 at 21:06, db wrote: > >> Usually the >> biggest problem is C++11 nowadays and libc++ usually helps there, it's >> just that most developer don't have resources to actually test >> packages on older boxes. > > Re libc++, how would you go about it? Echo requested, uninstall installed,

Re: building from source with libc++

On 2 April 2017 at 00:55, db wrote: > What I would like to know is though, how is MP team's view on legacy OS > versions — I do know that it's focusing on 10.9+ supported systems, as stated > in the homepage, and that here and there software is still being patched for > the former and binaries s

Re: building from source with libc++

On 1 Apr 2017, at 17:24, Ken Cunningham wrote: > I am not (presently at least) on the macports team, but I have been building > all software from source with libc++ for over a year now on 10.6.8 with > outstanding success. I works extremely well for me. > ... > Not everything works --- the only

Re: building from source with libc++

On Sat, Apr 1, 2017 at 5:24 PM, Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > Email me directly if you want to, or ask here. If there is no objection, please, maintain this conversation in this list because I also have a PPC computer. ​Thank you. -- Eneko Gotzon Ares enekogot...@g

Re: building from source with libc++

Hi I am not (presently at least) on the macports team, but I have been building all software from source with libc++ for over a year now on 10.6.8 with outstanding success. I works extremely well for me. I also have 6 PPC machines running 10.4 and 10.5 using gcc4.2 to gcc6 that have extensive

Re: building from source with libc++

On 28 Mar 2017, at 17:42, db wrote: > On 28 Mar 2017, at 17:31, "Daniel J. Luke" wrote: >> On Mar 28, 2017, at 9:55 AM, db wrote: >>> Is there any MP official notice of support? >> It's right there on https://www.macports.org > > That is not. And one thing is targeting mainly systems still supp

Re: building from source with libc++

On 28 Mar 2017, at 17:31, "Daniel J. Luke" wrote: > On Mar 28, 2017, at 9:55 AM, db wrote: >> Is there any MP official notice of support? > It's right there on https://www.macports.org That is not. And one thing is targeting mainly systems still supported by Apple, another going along with it a

Re: building from source with libc++

On Mar 28, 2017, at 9:55 AM, db wrote: > Is there any MP official notice of support? It's right there on https://www.macports.org "We provide a single software tree that attempts to track the latest release of every software title (port) we distribute, without splitting them into “stable” Vs.

Re: building from source with libc++

ble future and start building from source with libc++? > Any version of macOS older than 10.9 Mavericks is considered legacy > already. This means we do not expect maintainers to actively look into > fixing issues, but submitted patches should be accepted and applied as > long as they do n

Re: building from source with libc++

On 2017-03-28 11:00, db wrote: > On 27 Mar 2017, at 11:12, Mojca Miklavec wrote: >> Dealbreaker: >>https://trac.macports.org/ticket/50448 > > Thanks for pointing that out. I skimmed through it. > > What's the actual state re libc++ binaries for <10.9? The support in base is missing to diffe

Re: building from source with libc++

On 27 Mar 2017, at 11:12, Mojca Miklavec wrote: > Dealbreaker: >https://trac.macports.org/ticket/50448 Thanks for pointing that out. I skimmed through it. What's the actual state re libc++ binaries for <10.9? Is dropping support for <10.9 something MP team is considering? As a 10.8-user, M

Re: building from source with libc++

On 27 March 2017 at 10:48, db wrote: > > Does the buildbot system have a machine with ≤10.8.5 building from source > using libc++ as PoC of https://trac.macports.org/wiki/LibcxxOnOlderSystems ? All the disabled builders without "legacy" in their name: https://build.macports.org/waterfall Dea

Re: building from source with libc++

On 24 Mar 2017, at 22:24, Ryan Schmidt wrote: >> Should I expect to encounter problems when switching to building from source >> with libc++ for the same ports whose binaries work fine with libstdc++? > > Certainly; libc++ on 10.8 is a nonstandard configuration that most MacP

Re: building from source with libc++

t;>>>> system with same versions. >>>> Another 10.8 system that you've also switched to libc++? Any differences >>>> between the two systems you can think of? >>> >>> OS X 10.8.5, Xcode 5.1.1, MP 2.4.1 — no differences that come to mind. >

Re: building from source with libc++

two systems you can think of? >> >> OS X 10.8.5, Xcode 5.1.1, MP 2.4.1 — no differences that come to mind. > > If the other 10.8 system also was switched to libc++ then I would believe > there is a problem with this system that does not exist on your other 10.8 > syst

Re: building from source with libc++

n I would believe there is a problem with this system that does not exist on your other 10.8 system. The problem could be an older version of Xcode, or mismatched or missing version of the command line tools. >> Not really. You could run into build problems. If you do, and it doesn'

Re: building from source with libc++

could run into build problems. If you do, and it doesn't seem > to be because of something unique to your system, please let us know. Should I expect to encounter problems when switching to building from source with libc++ for the same ports whose binaries work fine with libstdc++?

Re: building from source with libc++

On 24 Mar 2017, at 19:23, Ryan Schmidt wrote: > I agree that ticket describes the error you encountered. It was closed > because nobody could explain it and the problem went away for the reporter. > You could re-open it and add your new information to it. Re-open #52335 while it's for different

Re: building from source with libc++

> On Mar 24, 2017, at 10:12, db wrote: > > On 24 Mar 2017, at 16:00, Rainer Müller wrote: >> A similar ticket had been filed before: >> https://trac.macports.org/ticket/52335 > > I don't see how that explains that 1.6.4_0 in one system is the binary from > MP, but this same version fails to c

Re: building from source with libc++

On Mar 24, 2017, at 08:42, db wrote: > I use 10.8 (don't need/don't want to upgrade) and stumbled upon a couple of > ports that require libc++. Upgrading to a version of macOS with libc++ as default (10.9 and later) will probably make your MacPorts life easier, but it's up to you of course. >

Re: building from source with libc++

On 24 Mar 2017, at 16:00, Rainer Müller wrote: > A similar ticket had been filed before: > https://trac.macports.org/ticket/52335 I don't see how that explains that 1.6.4_0 in one system is the binary from MP, but this same version fails to compile in another identical system. OS X 10.8.5, Xcod

Re: building from source with libc++

On 2017-03-24 14:42, db wrote: > I use 10.8 (don't need/don't want to upgrade) and stumbled upon a couple > of ports that require libc++. > > So I gave building from source a try in a vm following these > instructions and > soon encountered a c

building from source with libc++

I use 10.8 (don't need/don't want to upgrade) and stumbled upon a couple of ports that require libc++.So I gave building from source a try in a vm following these instructions and soon encountered a couple of problems with python2_select (needed base updated) and xorg-libX11 (attached config.log),