Re: How to keep uncommitted work in a git clone

> On 5 Nov 2016, at 9:58 pm, Rainer Müller wrote: > >> On 2016-11-05 09:07, Mojca Miklavec wrote: >> # go to master and pull the latest changes >> git checkout master >> git pull --rebase >> >> # if you did your work on libpng in master, you are then set >> >> # else go to your libpng branch

Re: GitHub migration complete

As to those who don't have commit access but consider doing pull requests: am I right that they could set up their working copy of the ports tree to use a personal fork on github as the default remote for pushing while still pulling from the official repo? I don't think I've seen that mentioned

Re: GitHub migration complete

On 07/11/16 16:52, Lawrence Velázquez wrote: On Nov 7, 2016, at 11:16 AM, René J.V. Bertin wrote: Well, yes, I was indeed thinking about something more readable than the old syntax (though I don't see what'd be wrong with making it compatible with the `what` command). Any sort of Git keywor

Criteria for picking compilers from fallback list ?

Hi, I'm working on an update to the root6 port, where the minimum compiler requirement has been increased in the latest release, such that I need to update the compiler blacklist/fallback to force a macports compiler to be used on OSX 10.8 and 10.9 (whereas previously the system one was OK).

Re: Handling C++11

> On 18 Jan 2017, at 4:15 pm, Mojca Miklavec wrote: > >> On 18 January 2017 at 04:43, Marcus Calhoun-Lopez wrote: >> I think perhaps I am not being clear in what I am proposing. >> >> Currently, if cxx_stdlib is equal to libstdc++ then the cxx11PortGroup >> returns an error and the port does

Re: Handling C++11

Hi, See https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html For the details. Set the ABI controls whether or not you compile using the new c++11 standards compliant implementations of string and list. If you set the ABI back to 0 then yes, you can then mix different std libs.

Re: Handling C++11

for > macOS prior to Mavericks, where libstdc++ is the default. > So _GLIBCXX_USE_CXX11_ABI is being used as it was intended, as a mechanism to > facilitate transition. > > -Marcus > >> On Jan 18, 2017, at 2:15 PM, Chris Jones wrote: >> >> Set the ABI

Re: Handling C++11

requests it (and is made aware of the consequences), I guess its reasonable enough... Chris On 20/01/17 00:02, Marcus Calhoun-Lopez wrote: On Jan 19, 2017, at 2:04 PM, Chris Jones wrote: I don't think we should, under any circumstances, but making the use of gcc to build c++ ports a sta

Re: Feedback on clang change (#53194)

Hi, To be blunt, i am not in favour of any of your proposals. I do not think we should have any update that allows builds to default to using macports stdlibc++. Old (ancient in my view) systems where the system c++ runtime is stdlibc++ should be allowed to die the graceful death they deserve.

Re: gcc, AVX (and newer) intrinsics and binutils

GCC vs. clang comparisons on sites like Phoronix suggest that GCC still has the upper hand compared even to clang 4.0 in computation-intensive tasks so it would make a lot of sense to get it to support the full instruction set. Please provide links to support such a claim. My reading is th

Re: about the libc++ conversion

Hi, The fact that in some cases mixing the two C++ runtimes does not lead to obvious issues is *not* a general proof that there is not a problem in doing this. The issues generally occur when the application passing information between the two runtimes, if in those two runtimes the same type

Re: Are macports builds prevented from accessing /dev/random ?

On 14/06/17 00:20, Joshua Root wrote: On 2017-6-14 08:18 , Christopher Jones wrote: Had a look into this. The ROOT source never explicitly opens /dev/random in read/write mode. Only read only. However, it also uses a number of external library calls, like std::rand(), and my best bet is o

Re: Are macports builds prevented from accessing /dev/random ?

Thanks ! On 14/06/17 13:56, Joshua Root wrote: On 2017-6-14 19:21 , Chris Jones wrote: On 14/06/17 00:20, Joshua Root wrote: On 2017-6-14 08:18 , Christopher Jones wrote: Had a look into this. The ROOT source never explicitly opens /dev/random in read/write mode. Only read only

Buildbots not accessible ?

Hi, Are there still problems with the build bots ? I cannot seem to get to https://build.macports.org cheers Chris

Re: Build Machine(s) & Java

Unless I am mis-remembering Apple stopped shipping any java version with OSX a while back. So unless you manually install something the build bots will not have any java version available. versions now should be downloaded direct from Oracle. https://support.apple.com/en-gb/HT204036 I belie

Re: Build Machine(s) & Java

Hi, On 05/07/17 13:38, Ryan Schmidt wrote: On Jul 5, 2017, at 04:00, Chris Jones wrote: On 05/07/17 01:14, Ryan Schmidt wrote: On Jul 3, 2017, at 13:29, Mohamed Issa wrote: Do the build machines have Java installed? As it stands right now, any changes to the Bazel port (or others like it

Re: Fix Sierra Trac query

You could just avoid the problem by using the numerical OS designation. macOS10.13 etc. Personally i prefer these to the random cat/place names anyway. Perhaps i am in a minority on this... Chris > On 26 Sep 2017, at 1:36 am, Ryan Schmidt wrote: > > Could someone with some Trac knowledge fix

Re: Fix Sierra Trac query

On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has both sierra and highsierra as keywords..

Re: Fix Sierra Trac query

On 27/09/17 15:58, Chris Jones wrote: On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has bot

Re: Fix Sierra Trac query

On 27/09/17 15:58, Chris Jones wrote: On 27/09/17 15:41, Rainer Müller wrote: On 2017-09-27 16:12, Chris Jones wrote: [[TicketQuery(component=ports&status!=closed&keywords~=sierra -highsierra,or,keywords~=10\.12)]] As I understand it, this will exclude any ticket which has bot

Macports Clang 3.9 compilation failures due to missing include

Hi All, I am investigating some build failures, with port that are being built with macports clang 3.9 What I am seeing is on some older systems, OSX10.(6,7,8) failures like [ 7%] Building CXX object src/CMakeFiles/XrdUtils.dir/XrdSys/XrdSysIOEvents.cc.o cd /opt/local/var/macports/build/_U

Re: Macports Clang 3.9 compilation failures due to missing include

rote: Dear Chris, On 28 September 2017 at 16:48, Chris Jones wrote: Hi All, I am investigating some build failures, with port that are being built with macports clang 3.9 What I am seeing is on some older systems, OSX10.(6,7,8) failures like fatal error: 'atomic' file not found #inc

Re: Macports Clang 3.9 compilation failures due to missing include

On 28/09/17 16:02, Mojca Miklavec wrote: On 28 September 2017 at 16:57, Chris Jones wrote: Hi, Thanks. In fact I tried adding PortGroup cxx11 1.1 but that gave me the error below. Presumably I am missiong something else ? clang: error: invalid library name in argument

Re: Macports Clang 3.9 compilation failures due to missing include

it doesn't add > anything when using the cxx11 1.1 PortGroup, and it messes up the PPC fixes > (small group, but what the heck). > > Best, > > Ken > > >> On 2017-09-28, at 8:20 AM, Mojca Miklavec wrote: >> >>> On 28 September 2017 at 17:05,

Re: Releasing 2.4.2

Hi, How long until this macports update is expected to be available via selfupdate, as I am not getting this yet, it is still returning 2.4.1 as the latest ? See below. Is the rsync server for some reason not yet updated ? cheers Chris Titan ~ > sudo port -d selfupdate DEBUG: Copying /Users

Re: establish installed dependency not in portfile

Please keep replies on list On 09/10/17 14:00, db wrote: On 9 Oct 2017, at 12:38, Chris Jones wrote: Why would you still build from source on 10.13 ? No binaries for all ~20K ports yet. Ryan said ~3K not long ago. I cannot seem to find his message in the lists though. There will be a

Re: establish installed dependency not in portfile

.. and of course I redirected it back to the wrong list... On 09/10/17 14:05, Chris Jones wrote: Please keep replies on list On 09/10/17 14:00, db wrote: On 9 Oct 2017, at 12:38, Chris Jones wrote: Why would you still build from source on 10.13 ? No binaries for all ~20K ports yet. Ryan

Re: https fetch error on older (<10.9) OSX releases due to rejected protocol

> On 18 Oct 2017, at 9:48 pm, Ryan Schmidt wrote: > > >> On Oct 18, 2017, at 15:40, Christopher Jones wrote: >> >> Hi, >> >> OK, thanks. >> >> Thing is fixing this isn’t something I am thinking of for myself. I would >> never use such an old OS (I have some VMs I use only for testing stuf

Re: Question about compiler blacklisting (llvm-gcc for wxWidgets)

On 02/11/17 14:39, Mojca Miklavec wrote: On 2 November 2017 at 15:16, Ryan Schmidt wrote: So wait... does wxWidgets require C++11 or not? If it does, that settles the discussion; treat it like any other port that requires C++11 and include the cxx11-1.1 portgroup. No, it doesn't. But one

Re: Addressing Port submission failures on Travis

On 20/12/17 14:19, Ken Cunningham wrote: On Dec 20, 2017, at 1:04 AM, Mojca Miklavec wrote: On 20 December 2017 at 09:04, Ken Cunningham wrote: keep the master branch up to date, but leave your PR branch alone until it's merged, then delete the branch. Indeed, that's the correct advice

Re: why does standard configure uses -Os?

Hi, > On 23 Dec 2017, at 11:12 pm, Joshua Root wrote: > >> On 2017-12-24 08:40 , Eitan Adler wrote: >> In macports base in standard_configure.sh >> >> there is this line: >> 6 env PATH=/usr/bin:/bin:/usr/sbin:/sbin CFLAGS="-pipe -Os" >> ./configure --enable-readline >> >> Why do we compile wi

Re: why does standard configure uses -Os?

> On 24 Dec 2017, at 7:57 pm, Ryan Schmidt wrote: > > >> On Dec 24, 2017, at 04:36, Chris Jones wrote: >> >> In general its not possible to say one setting will always perform better >> than another, its very use case dependant. For instance if you

Re: why does standard configure uses -Os?

> On 25 Dec 2017, at 5:37 pm, Clemens Lang wrote: > > Hi, > > On Mon, Dec 25, 2017 at 08:32:00AM +0000, Chris Jones wrote: >>> Ports are free to override configure.optflags if desired. >> >> That’s not the same as simply letting the underlying package de

Re: Blacklisting gcc

> On 27 Mar 2018, at 5:52 pm, Ken Cunningham > wrote: > > > On 2018-03-27, at 7:43 AM, Benjamin Redelings wrote: > > >> I suppose there could be a c++14 portgroup? > > There could be. > > But I would instead propose that MacPorts never puts forward a compiler that > can't handle c++14 at

Re: port & root

> On 5 Apr 2018, at 6:39 pm, Bjarne D Mathiesen > wrote: > > Rainer Müller wrote: >>> On 2018-04-05 18:26, Bjarne D Mathiesen wrote: >>> When running './diffPorts php72-' as root I get this : >> >> Just to be specific, did you open a root shell first or did you run it >> with sudo? > > root

Re: Is it possible to specify variant as part of depends_lib?

Hi, Do you *really* mean root5 ? port info says it requires root6 Titan ~ > port info gds gds @2.18.7 (science) Variants: universal Description: LIGO Scientific Collaboration Algorithm Library containing core routines for gravitational wave data analysis. Homepage: https:

Re: Agility

I have one request though. You are sometimes asking people to close the PRs because you don't want unfinished PRs in the queue. I would like to suggest adding a special label to such PRs before closing them, saying something like "workneeded". I would occasionally like to be able to search for s

Re: Agility

Doing this should prevent the MR being merged, and make it clear the author is still working on something, but want to submit the MR now for other reasons (like not to forget it, or start to get comments etc.). I use this regularly in other systems at work and it works really well... We shou

Re: Agility

> On 25 Apr 2018, at 5:46 pm, Ryan Schmidt wrote: > > >> On Apr 25, 2018, at 11:31, Chris Jones wrote: >> >> Personally, I would like to see MacPorts go in exactly the opposite >> direction, so migrate away from using trac for anything much. I also happen

Re: Agility

> On 25 Apr 2018, at 5:47 pm, Ryan Schmidt wrote: > >> On Apr 25, 2018, at 11:23, Chris Jones wrote: >> >> I don't think there is any need to re-invent our own system here. There is >> an already standard why of dong this, which is to declare the request

Re: Agility

> On 25 Apr 2018, at 7:08 pm, Perry E. Metzger wrote: > > On Wed, 25 Apr 2018 11:47:21 -0500 Ryan Schmidt > wrote: >> On Apr 25, 2018, at 11:23, Chris Jones wrote: >> >>> I don't think there is any need to re-invent our own system here. >>>

Re: Agility

> On 25 Apr 2018, at 7:11 pm, Ryan Schmidt wrote: > > >> On Apr 25, 2018, at 13:02, Chris Jones wrote: >> >> On 25 Apr 2018, at 5:46 pm, Ryan Schmidt wrote: >> >>>> On Apr 25, 2018, at 11:31, Chris Jones wrote: >>>> >>>>

Re: Agility

> On 25 Apr 2018, at 7:13 pm, Perry E. Metzger wrote: > > On Wed, 25 Apr 2018 18:48:33 +0200 Mojca Miklavec > wrote: >> I admit that I do find value in WIP PRs from time to time. Like ... >> someone submitting an update to a library that needs coordinated >> update with dependent ports that ne

Re: Agility

On 26/04/18 07:52, Mojca Miklavec wrote: On 26 April 2018 at 08:21, Jan Stary wrote: What are the top three Trac features that Github issues don't have? This is my personal list, others might have something different on their priority list: 1.) Add labels for ports. This is a feature that

Re: Agility

On 26/04/18 07:19, Jan Stary wrote: On Apr 25 09:25:44, ken.cunningham.web...@gmail.com wrote: We should allow (encourage even) WIP PRs to be submitted, when the work is in a state that warrants it. Chris Personally i would think those would better be trac tickets, as that model seems to

Re: Request for discussion: lowering the backlog of old Trac tickets.

> Anyway, that was what I wrote. I'd be interested in hearing other > people's thoughts. In short, I would agree with you. MPs current trac is bogged down with too many open tickets such that it is arguably not 100% fit for purpose. I certainly have preferred to largely ignore it as much as I c

Re: Request for discussion: lowering the backlog of old Trac tickets.

On 30/04/18 23:52, Rainer Müller wrote: On 2018-04-30 21:09, Chris Jones wrote: I would also argue we are using the same system, for two different things. Short term bug reports and longer term 'work goals' are not the same, but we seem to mix them up in the same system. Mayb

Re: [macports-ports] branch master updated: root6: update default compiler variants

On 02/05/18 07:07, Ryan Schmidt wrote: On May 1, 2018, at 12:52, Chris Jones wrote: +# Enable variants that only seem to work when not using macports clang... +if [expr ![string match macports-clang-* ${configure.compiler}] ] { +default_variants-append +veccore +davix +} You don&#

Re: Compiler blacklist 'shorthand'

> On 6 May 2018, at 11:19 am, Ryan Schmidt wrote: > > >> On May 6, 2018, at 05:18, Rainer Müller wrote: >> >>> On 2018-05-06 12:07, Ryan Schmidt wrote: >>> On May 5, 2018, at 19:36, Craig Treleaven wrote: A couple of times recently, I’ve noticed boilerplate in ports that requ

Re: Compiler blacklist 'shorthand'

> On 6 May 2018, at 11:28 am, Ryan Schmidt wrote: > > >> On May 6, 2018, at 05:27, Chris Jones wrote: >> >>> On 6 May 2018, at 11:19 am, Ryan Schmidt wrote: >>> >>>> On May 6, 2018, at 05:18, Rainer Müller wrote: >>>> >&g

Re: kmymoney4 not working!

It appears to have all installed correctly, though when I try to open KMyMoney4, the icon just bounces in the dock, along with 'drkonqi', for about 20 seconds, and then just quits and never opens. That's all I get. These "bounces and never opens" is one of the most nasty things on Mac that

Re: Pull Request Etiquette

Hi, In my view, if you can you should push your changes to the branch used for the existing PR. As you used it as the basis for your work best to keep the update in one place. Chris > On 19 May 2018, at 11:22 pm, Marcus Calhoun-Lopez > wrote: > > Thank you for the advice. > > I do not beli

Re: Pull Request Etiquette

Hi, > On 20 May 2018, at 7:26 am, Mojca Miklavec wrote: > > > > V ned., 20. maj 2018 00:06 je oseba Marcus Calhoun-Lopez napisala: >> There is a pull request to update Octave to 4.4.0. >> A significant amount of work has been put in to it. >> While attempting to address some of the outstanding

Re: [macports-ports] branch master updated: Add optimizations variant to python{27, 35, 36, 37}

> On 16 Jul 2018, at 1:00 am, Perry E. Metzger wrote: > > I want to be clear about something. In theory, we could turn on > runtime trace guided optimization for _every_ binary. Python isn't > particularly special on this. It would also, in my opinion, be a > horrible mistake -- the benefits a

Re: iTerm Upcoming Versions

Hi, 10.13 only would be quite a harsh requirement, so I think limiting iTerm2 to only that would not be good. Do you know why exactly they are doing this ? Is it the Metal 2 requirement, or Xcode or something else ? Sometimes within MacPorts we can support OSes beyond what upstream expects,

Darwin 9 PPC tester ?

Hi, Is there anyone who has a PPC machine running Darwin 9 (OSX 10.5) that would be willing to run a test of the PR https://github.com/macports/macports-ports/pull/2296 ? For the reasons outlined in the PR it would be useful to know if the port libgcc builds properly on this platform. I have t

Re: Darwin 9 PPC tester ?

before a final release (which >> is why right now I don’t think its a big deal). >> >> Chris >> >>> On 29 Jul 2018, at 7:12 pm, Ryan Schmidt wrote: >>> >>> >>> >>>> On Jul 29, 2018, at 11:32, Chris Jones wrote: >>&g

Re: GCC Dependencies

Hi, What you are proposing seems to suggest no long making, for instance, libgcc6 depend on the libgcc7 or libgcc. This means if you install only libgcc6 you will not get a complete runtime, only the incomplete part that provides. I am not sure this is a good idea. For one it means all the old

Re: GCC Dependencies

Hi, > On 13 Aug 2018, at 1:38 am, Marcus Calhoun-Lopez > wrote: > > > >> On Aug 12, 2018, at 5:14 PM, Chris Jones wrote: > > Thank you for your response. > >> What you are proposing seems to suggest no long making, for instance, >> libgcc6 depe

Re: the size checksum

This is being discussed in another thread. Guess you did not see that.. > On 18 Aug 2018, at 8:16 am, Jan Starý wrote: > > Hi all, > > beside sha25 and rmd160, some ports use a 'size' field in the checksums. > Why was it added? The fact that the distfile has the prescribed sha256 > and the pr

Re: Help wanted doing some xorg-* updates

Hi, As its one of the ports i use most, i do have an interest in keeping it updated. Are the updates you have so far somewhere if git, in a branch ? If so I will also take a look when I can. Chris > On 24 Aug 2018, at 10:57 pm, Perry E. Metzger wrote: > > On Fri, 24 Aug 2018 08:50:09 -0400 "

Re: noise on selfupdate

> On 25 Sep 2018, at 12:58 am, Ryan Schmidt wrote: > > > >> On Sep 24, 2018, at 18:54, Eitan Adler wrote: >> >> When i ran "sudo port selfupdate" for the first time on a new (from >> source) install I see this >> >> --- >> ∴sudo port -v selfupdate >> Password: >> ---> Updating MacPorts ba

Re: Potential problem with small subset of Cocoa ports on Xcode 10

> On 28 Sep 2018, at 2:35 pm, Joshua Root wrote: > >> On 2018-9-28 23:12 , Perry E. Metzger wrote: >> Note that the new build system is also much more strict about many >> things, you may have to clean up latent sloppy code (like the use of >> for something that should be "include.h" in C) to

Re: Potential problem with small subset of Cocoa ports on Xcode 10

> On 28 Sep 2018, at 8:58 pm, Perry E. Metzger wrote: > > On Fri, 28 Sep 2018 08:22:01 -0500 Marius Schamschula > wrote: >> Perry, >> >> I’ve just run into this problem with TeXShop4. The build phase >> succeeds, but destroot fails. >> >> How does one revert to the “old” build system under

Re: Potential problem with small subset of Cocoa ports on Xcode 10

> On 28 Sep 2018, at 10:55 pm, Perry E. Metzger wrote: > > On Sat, 29 Sep 2018 07:40:22 +1000 Joshua Root > wrote: Here's the kludge for a Portfile: if {[vercmp ${xcodeversion} 10.0] >= 0} { destroot.pre_args -UseNewBuildSystem=NO } Arguably, one shoul

Re: Commit History vs User Convenience

Hi, This makes absolutely no sense unless one change is straightforward and urgent (and could be merged quickly), and the other change is controversial & requires a lot of time to reach the consensus. Or some other "similar" scenario. Merging the first commit will necessarily introduce more work

Re: Merging pull requests before 72 hours

Hi, On 15/10/18 06:41, Joshua Root wrote: I agree with the points in Mojca's first message in the thread. On 2018-10-15 09:20 , Mojca Miklavec wrote: On Mon, 15 Oct 2018 at 00:10, Blair Zajac wrote: We could add a rule that should help a bit that openmaintainer only lets people do minor ver

Re: Merging pull requests before 72 hours

and so on... Do we have a guide for something like this written done anywhere ? "7.4.1. Non-Maintainer Port Updates" in our guide. https://guide.macports.org/#project.update-policies.nonmaintainer That is not what I am asking for. Specifically it does not give any guidance on exactly what

Re: Merging pull requests before 72 hours

Hi, 1. if the person doing the update is skilled (and at this point I generally know the difference), 2. if they indicate that they've tested the result, 3. if it seems based on history that the listed maintainer is unlikely to comment then or ever (and I usually guess right), 4. and that if wha

Re: Merging pull requests before 72 hours

Hi, > On 15 Oct 2018, at 10:34 pm, Leonardo Brondani Schenkel > wrote: > > My two cents: > > I'm a committer, and if I'm doing a trivial bump of an openmaintainer port > I'll push it directly. Depends entirely on what you consider trivial. If you consider a version update a trivial bump the

Re: Merging pull requests before 72 hours

> On 15 Oct 2018, at 11:18 pm, Chris Jones wrote: > > Hi, > >> On 15 Oct 2018, at 10:34 pm, Leonardo Brondani Schenkel >> wrote: >> >> My two cents: >> >> I'm a committer, and if I'm doing a trivial bump of an openmaintainer por

Re: Merging pull requests before 72 hours

Hi, On 16/10/18 07:37, Leonardo Brondani Schenkel wrote: On 15 Oct 2018, at 11:18 pm, Chris Jones wrote: On 15 Oct 2018, at 10:34 pm, Leonardo Brondani Schenkel at macports.org> wrote: I'm a committer, and if I'm doing a trivial bump of an openmaintainer port I'l

Re: Merging pull requests before 72 hours

Hi, On 16/10/18 13:37, Leonardo Brondani Schenkel wrote: Please point me to where this is documented ? i.e. where is it stated that openmaintainer allows revision changes. This appears to be one of the issues here since not everyone, myself included, agrees with you. The only statement I have

Re: OT: Apple 64-bit changes

It is correct but has nothing really to do with the specific changes in macOS 10.14. The macOS has been 64 bit for a long time now. Mojave depreciates the running of 32 bit applications, and removes the ability to build them, using the 10.14 SDK. > On 19 Oct 2018, at 10:14 pm, Randolph M. Frit

Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

Hi, I've stumbled into the same issue twice in recent days, with two different ports, which is the use of clock_gettime(CLOCK_REALTIME, &wait); which is only available in macOS 10.12 or newer. See for instance the issue I found yesterday in xrootd. https://github.com/xrootd/xrootd/issues/8

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

We have worked around this in a number of ports so far, and turned off some functionality in others. I use the_silver_searcher to find stuff like this, for example in the macports-ports repo: ag -i clock_gettime . Sorry, I don't follow the reference to the_silver_searcher or what the 'ag

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

Hi, On 23/10/18 16:35, Ken Cunningham wrote: On 2018-10-23, at 8:18 AM, Chris Jones wrote: We have worked around this in a number of ports so far, and turned off some functionality in others. I use the_silver_searcher to find stuff like this, for example in the macports-ports repo: ag -i

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

BTW, here is a nice clock_gettime() replacement that Jeremy wrote up: Thanks. That is a bit better than what I cooked up for xrootd. I might replace it ;) Actually, I take that back. I

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

Hi, > On 23 Oct 2018, at 11:26 pm, Ken Cunningham > wrote: > > Yep, that is exactly what I was thinking as well. > > I was pondering a specific include folder like > > ${prefix}/include/snowleopardfixes > > for want of a better title for it, where these could be placed. Then we could > just

Re: Creating a port for non-free software

Hi, As i understand it reading the links below the user has to register themselves, name and email etc., in order to get a password to allow access to the downloads. I don’t really see how this is compatible with macports, how would you integrate this into the port file ? Chris > On 24 Oct

Re: Creating a port for non-free software

k the oracle port well enough as I missed that. -Marcus On Oct 23, 2018, at 7:35 PM, Chris Jones wrote: Hi, As i understand it reading the links below the user has to register themselves, name and email etc., in order to get a password to allow access to the downloads. I don’t really see how

Re: Creating a port for non-free software

018, at 7:35 PM, Chris Jones mailto:jon...@hep.phy.cam.ac.uk>> wrote: > > Hi, > > As i understand it reading the links below the user has to register themselves, name and email etc., in order to get a password to allow access to the downloads. I d

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

Hi, On 24/10/18 01:44, Ken Cunningham wrote: On 2018-10-23, at 4:23 PM, Chris Jones wrote: I see no reason to not just place them directly in the main MacPorts include prefix, i.e. normally /opt/local/include. Placing them anywhere else requires that specific folder to be included as well

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

Hi, I am interested in working on this, as I think it would ease some issues in a few ports I have stumbled over recently. Let me try and put something to test together. I have started to put something together for this. I have a little new project in github https://github.com/cjones051073

Re: Issues with clock_gettime(CLOCK_REALTIME, &wait) pre macOS 10.13

ere is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. so the `include_next` directive is fine that far back... OSX 10.6 is the oldest I can test, but it would be interesting to see if it also works on 10.5 (PPC) Chris On 24/10/18 10:17, Chris Jones wrote:

Re: forcing 10.12 or 10.13 builds onto 10.14 for 32bit fix?

At the moment, you're right, we don't have anything that can do that. So at the moment we would need to find a way to compile 32-bit on 10.14. Jack Howarth mentioned that the system dylib still has 32-bit symbols (of course, so that it can run 32-bit software) but that the tbd file for the

Re: dealing with java opened SSL errors

I don't know about java, but the python portgroup deliberately disables the ability to download dependencies. We don't want ports to download things except during the fetch phase. And if a port has dependencies on other ports, it should declare them. It looks like py-tensorflow already decla

Re: Discovering and using setup.py options

Can you post a link to an example of such a file you have been looking at ? Chris > On 6 Nov 2018, at 11:05 pm, Ryan Schmidt wrote: > > For Python projects that build using a setup.py file, how do I discover what > options are available -- what's the equivalent of "./configure --help"? I've

Re: Xcode configuration woes

> On 9 Nov 2018, at 7:40 pm, Vincent Habchi wrote: > > Ryan, > >> Yup, NSAppearanceNameDarkAqua is new in macOS 10.14. > […] > >> So you must be on macOS 10.13 with Xcode 10. > > Unfortunately not : >> uname -a > Darwin Air.local 18.2.0 Darwin Kernel Version 18.2.0: Sat Nov 3 12:30:49 PDT

Re: Xcode configuration woes

On 9 Nov 2018, at 7:57 pm, Vincent Habchi wrote: >>> Weird, no? >> >> Not necessarily. You are running beta versions. Anything is possible. >> >> Do you really need do this ? Wouldn't switching to the production version >> not make sense now ? > > How do you mean? Isn't it obvious ? Beta

Re: Xcode configuration woes

> On 9 Nov 2018, at 8:11 pm, Vincent Habchi wrote: > > Chris, > >> >> Isn't it obvious ? Beta releases are more likely to have problems… > > I mean I run a beta-version of 10.14.2 but the Xcode I’ve installed is 10.1, > the production release. > Also that doesn’t explain why the headers i

Re: Xcode configuration woes

> On 9 Nov 2018, at 8:37 pm, Vincent Habchi wrote: > > Chris, > >>> On 9 Nov 2018, at 21:12, Chris Jones wrote: >>> >>> I mean I run a beta-version of 10.14.2 but the Xcode I’ve installed is >>> 10.1, the production release. >>

Re: C error: Expected expression

Perhaps a semicolon is needed? i.e. int APIENTRY; glutExtensionSupported(const char *extension) nope, that is definitely invalid code. As Joshua said, you need to investigate how APIENTRY is defined. Chris

Re: Macport migration error

On 14/11/18 04:10, peter wrote: Hi all, I upgraded to Mac OS 10.14 recently. Due to some reason, I thought I should migrate macports after the OS upgrade. I ran the commands according to the following link: https://trac.macports.org/wiki/Migration And the errors pop up when I ran the follow

Re: Xcode configuration woes

On 21/11/18 09:02, Vincent Habchi wrote: Ryan, Did you file a bug report with Apple w/r to that, or do you want me to go ahead? Do as you like, but I suspect /usr/include being missing is not a bug but intentional. I've updated the buildbot machine, and it also still doesn't have /usr

Re: calculix-ccx fails to build

Please use trac to report build failures, not the mailing lists. https://trac.macports.org/wiki/Tickets I for one do not appreciate all the (uncompressed) text files you have been sending as attachments recently. > On 3 Dec 2018, at 7:14 am, Mark Brethen wrote: > > I found this in the insta

Re: calculix

Again, please refrain from sending attachments to the mailing list. If you wish to have people look at a port, create a branch in github with it and direct people to that. Chris On 10/12/18 23:17, Mark Brethen wrote: I’m working on a new port for an FEA pre/post processor called calculix.

Re: Issues with compiler flags in gfortran

Hi, What exactly version (and variants) of cctools do you have installed ? Perhaps try force removing it, then reinstall, to make sure you are using the current default variants. Chris > On 21 Jan 2019, at 2:47 pm, Nicolas Pavillon wrote: > > Hi, > > I stumbled on some issues with the for

Re: Issues with compiler flags in gfortran

ls returns version 1.38, which quite behind compared to the > version provided by binutils, for example. > > /opt/local/bin/as -v > Apple Inc version cctools-921, GNU assembler version 1.38 > > Cheers, > > Nicolas > >> On Jan 22, 2019, at 0:23, Chris Jones wrote

Re: Issues with compiler flags in gfortran

provided as, from cctools, is *supposed* to be the same as that provided by Xcode 10. Actually, one thing you have not said is what macOS version are you using ? Chris Cheers, Nicolas On Jan 22, 2019, at 11:23, Chris Jones <mailto:jon...@hep.phy.cam.ac.uk>> wrote: Hi, Could

  1   2   3   4   >