Problems cross-compiling with clang 3.7 & 3.9 on 10.6

Hi, After a long time I tried cross-compiling a few things on 10.6, but most attempts failed: > clang-mp-3.4 -arch ppc test.c -o test [OK] > clang-mp-3.7 -arch i386 test.c -o test [OK] > clang-mp-3.7 -arch ppc test.c -o test ld: warning: ignoring file /opt/local/libexec/llvm-3.7/bin/../lib/cl

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 27 March 2017 at 17:14, Mojca Miklavec wrote: > Hi, > > After a long time I tried cross-compiling a few things on 10.6, but > most attempts failed: > >> clang-mp-3.4 -arch ppc test.c -o test > > [OK] Plus another problem that I don't quite understand: libtoo

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 27 March 2017 at 17:39, Mojca Miklavec wrote: > On 27 March 2017 at 17:14, Mojca Miklavec wrote: >> Hi, >> >> After a long time I tried cross-compiling a few things on 10.6, but >> most attempts failed: >> >>> clang-mp-3.4 -arch ppc test.c -o test

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 27 March 2017 at 22:26, Jeremy Huddleston Sequoia wrote: >> On Mar 27, 2017, at 08:14, Mojca Miklavec wrote: >> >> Hi, >> >> After a long time I tried cross-compiling a few things on 10.6, but >> most attempts failed: >> >>> clang-mp-3.4 -ar

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 28 March 2017 at 05:07, Ken Cunningham wrote: > It's been a few months since I went down this rabbit hole, but IIRC, > it worked a little better to build clang on ppc directly. Just to clarify. I want to compile some software for multiple architecture and provide backwards compatibility for as

Re: Problems cross-compiling with clang 3.7 & 3.9 on 10.6

On 28 March 2017 at 17:37, Ken Cunningham wrote: > On 2017-03-28, at 2:18 AM, Mojca Miklavec wrote: > > It had always been a design goal for llvm to produce workable PPC code, but > although close (lots of things do work) they never quite got there (Jeremy > has most of the bugs

Re: GSoC'17: Add migrate action to port command Project

Hi, I'm not too familiar with the project, but just some of my thoughts. One of the biggest pains at the moment is the fact that we don't record requested variants anywhere. We do record requested ports, but not the variants. It may easily happen that "port install foo" would install variant A o

Re: GSoC Proposal

Can you please elaborate a bit more on Travis CI will do lint and install tests on macOS 10.10-12 for PRs and commits. What does "install tests" refer to exactly? Mojca

Re: GSoC Proposal

On 2 April 2017 at 04:23, Zero King wrote: > macOS VMs on Travis would do `port lint | tee lint.txt; if grep > "^Error: " lint.txt ; then ...` > > and `port install ...` (`port test ...` if test exists) and if one of them > failed Travis will report that back to GitHub. > > Also Travis will keep l

Re: Registering a device with a particular software

On Apr 9, 2017 8:20 AM, "Sébastien DEWAILLY" wrote: > > Hi, > > > I want to use a device with one of your softwares but when I want to > register it, it doesn't find the executable. Please be more specific. This is like complaining to Apple that one of the programs running on their hardware is bu

Re: GSoC Proposal

Hi, Just to clarify one thing (also to any other GSOC applicant): this discussion does not provide any indication about the ranking of the submitted proposal or whether this or any other proposal might be or not be accepted. There might be better or worse applications where less clarification is n

Re: dvips from texlive-basic broken?

On 13 April 2017 at 01:42, Andrew Moore wrote: > Only by moving aside dvips(1) from MacPorts texlive-basic and using dvips(1) > from MacTeX 2016 distribution, was I able to upgrade to MacPorts asymptote > 2.41 vector graphics package. > > asymptote 2.40 was installed about a month ago without an

Re: dvips from texlive-basic broken?

On 13 April 2017 at 16:56, Andrew Moore wrote: > I did verify that ghostscript it is not causing the problem, and have now > completely rebuilt TeX and confirmed that MacPorts dvips is broken on my > system with regard to building asymptote documentation (it exits with trap 6 > - presumably SIGA

To force-push or not to force-push

Hi, A confused maintainer just pointed out "a problem" with our guidelines: https://trac.macports.org/wiki/CommitMessages#corrections ~~~ You cannot correct commits that you have already pushed. Comment on the commit's GitHub page instead. (Modifying your local history causes it to diverge f

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: -std=c++11 for gnuplot +qt5 (was Re: building from source with libc++)

On 20 April 2017 at 23:12, Andrew L. Moore wrote: > Sorry to land in the middle this discussion with some dumb questions... > > I'm on macOS 10.12.4 (Sierra)/Xcode 8.3.2, but was reviewing > LibcxxOnOlderSystems > after having to add `configure.cxxflags-append -std=c++11’ in gnuplot > Portfile f

Re: building from source with libc++

On 20 April 2017 at 23:06, Clemens Lang wrote: > On Wed, Apr 19, 2017 at 03:13:37PM +0200, Mojca Miklavec wrote: >> >> The thing is that a lot of these failures happen when developers don't >> put too much attention into consistently respecting all flags. Some >>

Re: [MacPorts] #53974: Dvips on macOS 10.12.4 exits with trap 6 building asymptote 2.41 documentation

On 24 April 2017 at 14:11, Andrew L. Moore wrote: > On Apr 21, 2017, at 10:48 PM, MacPorts wrote: >> >> #53974: Dvips on macOS 10.12.4 exits with trap 6 building asymptote 2.41 >> documentation > > DVIs have been attached to the ticket. Thank you. > Now please allow me a tangent rant. Or maybe j

Opportunistic (broken) build dependencies? (gdbm)

Hi, I just experienced a failure to build gdbm during "port upgrade outdated". The reason: configure checks for for ac_prog in gawk mawk nawk awk and then calls "gawk" which is temporarily broken due to readline which has been upgraded some seconds before (while gawk wasn't yet). But gawk is

Re: Opportunistic (broken) build dependencies? (gdbm)

On 25 April 2017 at 11:45, Mojca Miklavec wrote: > Hi, > > I just experienced a failure to build gdbm during "port upgrade outdated". > > The reason: configure checks for > for ac_prog in gawk mawk nawk awk > and then calls "gawk" which is temporaril

Re: Request for manual builds

Hi, This issue needs to be resolved first: https://trac.macports.org/ticket/53931 Mojca https://build.macports.org/builders/ports-10.6_x86_64_legacy-builder/builds/27001/ On 1 May 2017 at 12:18, Davide Liessi wrote: > Hi all. > > Due to the libarchive bug in March, many ports were not bui

Congratulations to all the selected GSOC students and projects

ing" (l2dy) Bot and CI for macports-ports mentors: Clemens Lang (cal/neverpanic) & Mojca Miklavec (mojca) At this point I would like to express my gratitude to Jackson Isaac who took over the administration and made sure that we applied in time :) Apart from (at least!) weekly meetin

Re: Maven 3.5.0 Pull Request 442

On 4 May 2017 at 22:25, John Patrick wrote: > evening, > > with github pull requests if it's not touched for a period of time > what is the process of getting it reviewed and merged now? Anything that can convince someone with commit rights to review it and commit it :) We are slightly understaff

Python 3.4

Hi, Often a question of what to do with Python 3.4 modules gets raised now that Python 3.6 has been out for a while (but its support is not nearly complete). That is: - Should new ports include 34 subports or not? - Should we actively remove 34 subports? I have nothing against leaving support fo

Re: Congratulations to all the selected GSOC students and projects

On 7 May 2017 at 23:12, Clemens Lang wrote: > > We also used to have a short introduction > round on MacPorts base in the last years. Since Zero King isn't working > on base, this probably makes sense for Umesh While he's not working directly on base, writing the buildbot setup still required some

can't read "env(COLUMNS)" in rev-upgrade

(was: Re: Congratulations to all the selected GSOC students and projects) On 8 May 2017 at 18:02, Zero King wrote: > > I'm trying to install MacPorts on Travis VMs. I want to avoid syncing > the ports tree to save more time for actual testing. Since the .pkg > installer would automatically call `

Re: MacPorts now listed on Repology.org

On 12 May 2017 at 05:17, Craig Treleaven wrote: > Just a heads up that MacPorts is now listed on a site that details all of the > packages carried by a wide variety of repositories: > > https://repology.org/repository/macports > > From a MacPorts developer standpoint, it is not a huge deal but the

Re: MacPorts now listed on Repology.org

Joshua, thanks a lot! https://github.com/repology/repology/blob/master/helpers/portindex2json/portindex2json.tcl Mojca

buildbot: don't skip building i386 packages

Hi, A while ago I requested changing mpbb-list-subports to exclude ports that have already been built and uploaded. May we please change this to only exclude "native" builds? Rationale: I would like to force build wine every now and then just for the sake of building all the universal dependenci

Re: buildbot: don't skip building i386 packages

Hi, On 12 May 2017 at 12:10, Mojca Miklavec wrote: > Hi, > > A while ago I requested changing mpbb-list-subports to exclude ports > that have already been built and uploaded. > > May we please change this to only exclude "native" builds? > > Rationale: I would

Re: macports-ports/Readme.md (was Re: LICENSE for macports-ports)

On 17 May 2017 at 15:33, Craig Treleaven wrote: > > I’ve drafted a Readme.md for macports-ports. > > If I commit it, will it cause any problems for the buildbots? Hopefully not (if it would cause problems, it would cause problems on each MacPorts installation :), but it would make sense to create

Re: [GSoC 2017] Community Bonding

Hi, On 18 May 2017 at 20:07, Jackson Isaac wrote: > Hi GSoC Students and Mentors, > > I hope you are utilizing the community bonding period well and had > some kind of introductory get to know interaction between > student-mentor(s) already. If not yet, please do so, it would help you > to get to

Buildbot emails

Dear Ryan, In case you have time, can you please check again where the buildbot email reports get lost? Thank you, Mojca

Closing pull requests

Dear Ken, I've seen that you closed a number of your own pull requests for probably no good reason other than being disappointed that your patch wasn't committed faster. We are heavily understaffed. Not so much understaffed by the number of committers (there are plenty in principle), but mostly b

Re: streamline github dev process

On 30 May 2017 at 20:23, Helmut K. C. Tessarek wrote: > Hello, > > Maybe we can streamline the github process a bit. As Mojca mentioned > earlier, the macports project is heavily understaffed. > > Is there a way to allow maintainers to set labels? (e.g. the > 'maintainer' or 'update' label) This i

Re: Buildbot emails

Dear Ryan (& Rainer/Clemens), The emails are now reaching the mailing list since May 28th, but they still don't end up in my inbox for the ports I maintain. Could you please look into that as well? Thank you, Mojca On 25 May 2017 at 13:35, Mojca Miklavec wrote: > Dear Ryan, >

Re: streamline github dev process

On 1 June 2017 at 03:43, Helmut K. C. Tessarek wrote: > On 2017-05-31 20:42, Joshua Root wrote: >> That's an unavoidable side effect of rebasing (or squashing) -- it's no >> longer the same commit that you signed. > Right, this is why one usually does a merge with --no-ff. Thus my commit > is intac

Re: [GSoC] Progress Report

Dear Zero King, On 4 June 2017 at 14:49, Zero King wrote: > Hi, > > GSoC coding phrase has begun and I'm implementing a CI bot that runs on > Travis CI and tests pull requests. > > My project includes two bots, the CI bot testing pull requests and the > PR bot assigning labels to PRs and notify ma

Re: [GSoC] Progress Report

On 6 June 2017 at 04:15, Zero King wrote: > On Mon, Jun 05, 2017 at 02:08:20PM +0200, Rainer Müller wrote: >> >> How is getopt relevant for the timing? If the dependency on getopt is a >> problem, let's find a portable solution for mpbb. Duplicating the exact >> same functionality we already have d

Re: how to install a subport rather than the main port from a local Portfile not in a repository

On 11 June 2017 at 16:27, Ken Cunningham wrote: > Long title … > > If you download a Portile into a folder, you can quickly install or work with > it with “sudo port -v install”, You don’t specify the name, and the primary > port in the local Portfile is used. > > Is there a way to work with a su

Re: [GSoC] migration

On 14 June 2017 at 05:47, Umesh Singla wrote: > > Okay, since there's already a OS comparison made, which I think can be > directly used here. But to clarify, just the OS check? a check on x86_64/ppc > changes is also needed. And potentially cxx_stdlib? Mojca

Where to find buildbot's home folder and .subversion/config?

Hi, I installed a buildbot slave using MacPorts (for stuff unrelated to to buildbot used for MacPorts itself) and I want to use the "buildbot" user created by the package manager. The problem is that I cannot figure out where to set use-commit-times = yes To start with, I don't know where t

Re: GitHub getopt repository

On 19 June 2017 at 22:13, Ryan Schmidt wrote: > >>https://github.com/macports/getopt/subscription > > What's this repository? Zero King might explain himself better, but this repository contains a dependency for Travis builds, to avoid having to install the second instance of MacPorts just for

Travis and "rebase before commit"

Hi, I'm so super grateful that we now have a working Travis setup :) As I suspected, there would be "problems" that we wouldn't be able to discover on a test setup and this is one of them. It's not really important to fix, but I wanted to mention it. Link: https://travis-ci.org/macports/macport

Error deleting com.apple.dt.Xcode.plist

Hi, With respect to: https://travis-ci.org/macports/macports-ports/jobs/245649003 I would imagine that "delete -force" would not error out if the file is missing. This code was added by Joshua: https://github.com/macports/macports-base/commit/485900103 So perhaps he has more insight. If

Re: Travis and "rebase before commit"

On 22 June 2017 at 16:07, Rainer Müller wrote: > On 2017-06-22 08:14, Sterling P. Smith wrote: >> The simple solution is to allow the "Rebase" option in GitHub. > > It is enabled and the default. The thing is that in the Mojca's workflow > for editing the PR commits, you would still need to push t

Re: Travis and "rebase before commit"

On 22 June 2017 at 21:05, Ryan Schmidt wrote: > On Jun 22, 2017, at 00:57, Mojca Miklavec wrote: > > I'm so super grateful that we now have a working Travis setup :) > > Did I miss an announcement email about this? https://lists.macports.org/pipermail/macports-dev/2017-June/0

Re: Travis and "rebase before commit"

On 22 June 2017 at 23:10, Mojca Miklavec wrote: > On 22 June 2017 at 21:05, Ryan Schmidt wrote: >> On Jun 22, 2017, at 00:57, Mojca Miklavec wrote: >> >> I'm so super grateful that we now have a working Travis setup :) >> >> Did I miss an an

Re: Buildbot now fails to build wine dependencies

On 27 June 2017 at 11:31, Ryan Schmidt wrote: > We used to be able to build wine on the buildbot, but we aren't anymore: > > https://build.macports.org/builders/ports-10.12_x86_64-builder/builds/32791 > > The error occurs when installing dependencies, specifically cairo: > >> > Installing depen

Why does autoconf.cmd remove autotools?

I was facing a strange problem, glibtoolize not being found despite libtool listed as a build dependency. It turned out that autoconf.cmd removes dependencies on autoconf, automake, libtool ... Is there a good reason for that? Wouldn't it be safer to simply leave the dependencies there, in partic

Re: Buildbot now fails to build wine dependencies

On 27 June 2017 at 12:04, Mojca Miklavec wrote: > > So I don't like the idea of generally removing variants, but we do > need to find a solution for this problem. To clarify. I'm not claiming that the current algorithm is 100% correct in specifying the variants, only that t

Travis: failed build reported as successful

Dear Zero King, Why is this build reported as successful? https://travis-ci.org/macports/macports-ports/jobs/248896726 Also: can it be that we're experiencing troubles due to an unusual $HOME variable? Mojca

Re: Travis: failed build reported as successful

On 1 July 2017 at 04:33, Zero King wrote: > On Fri, Jun 30, 2017 at 10:51:54PM +0200, Mojca Miklavec wrote: >> >> Dear Zero King, >> >> Why is this build reported as successful? >> >> https://travis-ci.org/macports/macports-ports/jobs/248896726 > &g

Travis: list of installed files

Hi, When looking at some pull requests which built successfully I realized that I would want to check the list of installed files. Now, we could either add that list to other logs, but I expect that for nearly all ports the list of installed files could probably be displayed at the end of the reg

Re: Travis: failed build reported as successful

On 1 July 2017 at 09:04, Zero King wrote: > On Sat, Jul 01, 2017 at 07:51:12AM +0200, Mojca Miklavec wrote: >> >> I tried to figure out where you call (anything that calls) portindex, >> but no luck :). > > > https://github.com/macports/macports-ports/blob/master/_

Re: Travis: failed build reported as successful

On 1 July 2017 at 09:21, Mojca Miklavec wrote: > On 1 July 2017 at 09:04, Zero King wrote: >> On Sat, Jul 01, 2017 at 07:51:12AM +0200, Mojca Miklavec wrote: >>> >>> I tried to figure out where you call (anything that calls) portindex, >>> but no luck :). >&g

Re: Travis: failed build reported as successful

On 1 July 2017 at 10:06, Zero King wrote: > On Sat, Jul 01, 2017 at 09:21:42AM +0200, Mojca Miklavec wrote: >> >> I would say that >>portindex || exit 1 >> should work. > > Does this make a difference? `portindex` returns 0 (success) even if > parse error

Travis: failed build reported as successful

Hi, Some builds seem to report build success while they in fact fail: https://travis-ci.org/macports/macports-ports/builds/249056960 Mojca

Re: Travis: failed build reported as successful

On 1 July 2017 at 18:51, Clemens Lang wrote: > On Sat, Jul 01, 2017 at 10:37:04AM +, Zero King wrote: >> Travis only fetches the merged ref >> `git fetch origin +refs/pull/542/merge:`, so it does complicate matters. Isn't that exactly what we want? >> I thought of `grep`ing the output for "F

Re: Buildbot now fails to build wine dependencies

On 3 July 2017 at 19:03, Rainer Müller wrote: > On 2017-06-27 11:31, Ryan Schmidt wrote: >>> > Installing dependency (55 of 120) 'cairo' with variants >>> '+quartz+universal+x11' >>> ... >>> Error: glib2: Variant quartz conflicts with x11 >> >> The cairo port has for years had both x11 and qua

Re: Is it time for a libc_fixes library yet?

On 3 July 2017 at 22:09, Rainer Müller wrote: > On 2017-07-03 19:07, Ken Cunningham wrote: >> So the last 10 or so tickets in trac seem like they are all for >> basically the same issue - a few missing symbols from libc prior to 10.7. > > Well, I would take this as a reason to just drop support for

Re: Buildbot now fails to build wine dependencies

Hi, One question: does a clean installation of "gtk3 +quartz" still work now? It depends on both glib2 and cairo, so I would expect problems or at least some weird non-determinism. On 4 July 2017 at 00:36, Rainer Müller wrote: > On 2017-07-03 22:26, Mojca Miklavec wrote: >>

Re: Petulant buildbots

Hi, Recalling from my memory (might not be accurate): whenever you first activate one xsl stylesheet, some entry remains somewhere and then subsequent builds fail unless that package is still installed. On the buildbot this is a problem because all packages were most likely once installed. The sa

Re: Petulant buildbots

See also https://trac.macports.org/ticket/53943 Mojca

Re: Whether to add "by: committer" label?

Dear Zero King, On 27 July 2017 at 06:13, Zero King wrote: > Hi, > > The "by: committer" label only provides extra information if the PR > sender is a committer but the port maintainer is not because the port > maintainer can only see the Member label on public members of the > macports organizati

Re: Build base archives for CI in a separate repository

Just my 2c. I would also prefer to do the necessary changes in the same repository unless there's a valid technical reason that would prevent us from being able to do it (like Travis not allowing us to build/upload often enough). In case there's a bug in base, it has to be fixed anyway. Mojca

Re: Possible patch for sox build failure on 10.7

On 12 August 2017 at 10:36, Jan Stary wrote: > > libtool: link: /usr/bin/grep -E -e > "^(sox_.*|lsx_(check_read_params|(close|open)_dllibrary|(debug(_more|_most)?|fail|report|warn)_impl|eof|fail_errno|filelength|find_(enum_(text|value)|file_extension)|getopt(_init)?|lpc10_(create_(de|en)coder_stat

tk +quartz on older systems

Hi, Is anyone willing to test (or ideally debug) "tk +quartz" on some older system? (Not sure how old is old enough, but it fails on 10.7 for example.) https://trac.macports.org/ticket/54673 Thank you, Mojca

Re: Why does macports require a migration across major version bumps?

On 30 August 2017 at 03:01, Eitan Adler wrote: > What is the underlying reason to require a reinstall across major > versions? I did something silly/stupid/smart and removed the check > from libexec/macports/lib/macports1.0/macports.tcl and just did 'sudo > port upgrade outdated' to rebuild the wo

Re: Why does macports require a migration across major version bumps?

Hi, Sorry, I accidentally clicked on the wrong place (Send) while the browser was doing its smart layout changes. On 30 August 2017 at 12:16, Mojca Miklavec wrote: > On 30 August 2017 at 03:01, Eitan Adler wrote: >> What is the underlying reason to require a reinstall across major >&

Fixing pypi2port

Hi, Do we have any guidelines about how to properly fix ports whose sources lived in out subversion repository? The pypi2port sources should be updated to: - switch from svn to git for the source - replace py34 with 36 - fix master_sites to use the new pypi syntax I think that perl modules also

Re: how to efficiently work through generating patches using git and macports build process?

On 30 August 2017 at 18:10, Ken Cunningham wrote: > >> Didn't we have a set of "shortcuts" that included the commands for >> setting up the local GIT repo? Might be worthwhile for folks with such >> shortcuts to push a link to this list (again). - MLD > > I do use a git repo to branch the macports

Re: how to efficiently work through generating patches using git and macports build process?

On 30 August 2017 at 18:50, Ken Cunningham wrote: > > Is there a way to make git ignore the *.o and *.a and other generated files > that might be in the source tree that we're not interested in tracking -- or > does the -A do that automatically? No, "git add -A" adds literally everything (other th

Re: Switching cxx_stdlib for C++11 on legacy macOS (was: Re: [GSoC] migration)

On 4 September 2017 at 10:47, Ryan Schmidt wrote: > On Sep 2, 2017, at 11:25, Rainer Müller wrote: > >> * archivefetch does not yet respect cxx_stdlib in any way > > Yeah that would need adjustment, based on how we decide to differentiate > libc++ archives from libstdc++ archives. Is there any ch

Re: [GSoC] migration

Hi, On 2 September 2017 at 15:18, Umesh Singla wrote: > On Thu, Jun 15, 2017 at 12:05 AM, Mojca Miklavec wrote: >> On 14 June 2017 at 05:47, Umesh Singla wrote: >> > >> > Okay, since there's already a OS comparison made, which I think can be >> > direct

Re: New project member: kencu

Dear PortMgr, On 11 September 2017 at 15:26, Rainer Müller wrote: > Please join us in welcoming the following new MacPorts project member: > > - Ken Cunningham (kencu) > > We look forward to continued excellent contributions from these new team > members. > > - Joshua, Rainer, and Ryan Thank you

Re: Pull request types in template on GitHub

10. sep. 2017 16:28 "Rainer Müller" : Hello, our GitHub pull request template [1] contains the following snippet which is used by the macportsbot to assign the corresponding label to it. ## Type(s) - [ ] bugfix - [ ] enhancement - [ ] security fix However, GitHub interpretes this as a list

Reversing use_bzip2

Hi, When trying to update x86_64-w64-mingw32-gcc I noticed that GCC 7.2 no longer provides bzip2 sources, but I'm not sure how to tell the Portfile that it should use xz instead of bzip2 given that the crossgcc group already contains "use_bzip2 yes". The alternative is of course to change all the

Re: Reversing use_bzip2

On 13 September 2017 at 15:42, Rainer Müller wrote: > On 2017-09-13 11:48, Mojca Miklavec wrote: >> When trying to update x86_64-w64-mingw32-gcc I noticed that GCC 7.2 no >> longer provides bzip2 sources, but I'm not sure how to tell the >> Portfile that it should use

Re: Switching cxx_stdlib for C++11 on legacy macOS (was: Re: [GSoC] migration)

On 4 September 2017 at 14:10, Ryan Schmidt wrote: > On Sep 4, 2017, at 04:25, Mojca Miklavec wrote: >> >> Is there any chance that we could schedule one 30-(max 90) minute long >> IRC meeting to finally settle this issue? At least from the >> philosophical point of view;

Fwd: Google Summer of Code 2018

Forwarding a message from Google ... Hello Mentors and Org Admins, We are pleased to announce Google Summer of Code 2018 , the 14th consecutive year of the program. We have announced the ma

Re: Fwd: Google Summer of Code 2018

On 26 September 2017 at 06:55, Jackson Isaac wrote: > On Tue, Sep 26, 2017 at 2:37 AM, Umesh Singla wrote: > > > > Have we ever participated in GCI before? > > Not yet. But we are open to volunteers. Let me know if anyone is > interested in mentoring. >From what I understand mentoring GCI requires

Re: Macports Clang 3.9 compilation failures due to missing include

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 > #include

Re: Macports Clang 3.9 compilation failures due to missing include

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 > '-stdlib=macports-libstdc++' This mea

Re: Macports Clang 3.9 compilation failures due to missing include

On 28 September 2017 at 17:05, Chris Jones wrote: > >> You need the variant +libstdcxx and clang-4.0 has that one enabled by >> default, while 3.9 doesn't. > > OK thanks. One of the ports I am interested in fixing will not compile with > clang 4.0 though. Is there a why to do this with 3.9 as well

Re: buildbot force build a variant?

30. sep. 2017 9:20 PM "Ken Cunningham" wrote: I'd like to force a build of webkit2-gtk +quartz on 15 & 16 to make sure my recent fixes play out as I think they will. After trying a few things, I can't seem to find the trick for that (if there is one). Is it possible to force a non-default build o

Re: Macports Clang 3.9 compilation failures due to missing include

On 28 September 2017 at 17:05, Chris Jones wrote: > 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 cxx1

Re: virtual machine for 10.5 intel ?

On 3 October 2017 at 05:01, Ken Cunningham wrote: > if anyone would care to enlighten me on the best approach to making a VM for > 10.5 intel, I would appreciate it. This is the only system I have that I > can’t presently see a way to virtualize. I didn't actually try it, but (other technical so

Re: ocaml ports need love

On 24 October 2017 at 06:10, Perry E. Metzger wrote: > On Mon, 23 Oct 2017 21:03:45 -0400 "Perry E. Metzger" wrote: >> On Mon, 23 Oct 2017 19:26:59 -0500 Marius Schamschula wrote: >> > Perry, >> > >> > Since February almost (all?) ocaml ports have been nomaintainer, >> > as mww relinquished maintai

Multitouch gestures for wxWidgets (request for review)

Hi, This is slightly off-topic, but hopefully not too much. In the past I submitted a number of tickets upstream to wxWidgets developers, often getting no response for years. During the GSOC mentor meeting I met the main developer and now suddenly most of those old tickets got addressed :) :) :)

Question about compiler blacklisting (llvm-gcc for wxWidgets)

Hi, I'm currently trying to fix wxWidgets-3.0 in various ways. One of the problems of the latest release is that it compiles fine with both clang >= 500 and llvm-gcc. If I blacklist clang < 500 on Lion, it will fallback to llvm-gcc which works in principle, but I don't know whether it makes more s

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

On 2 November 2017 at 12:01, Ryan Schmidt wrote: > On Nov 1, 2017, at 11:29, Mojca Miklavec wrote: > >> I'm currently trying to fix wxWidgets-3.0 in various ways. One of the >> problems of the latest release is that it compiles fine with both >> clang >= 500 an

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

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 needs a C++11 flavour of it if another p

Support for building +quartz

Hi, This is a reminder about one burning issue. I'm currently trying to build wine and I don't see any way to avoid building gtk3 from sources (gtk3 seems to build forever). Also, I would like to have gtk3 +quartz build anyway which means compiling from source on a no-matter-what basis. Could we

How to organize bootstrapping phase of cross-compiler?

Hi, A while ago I packaged MinGW's gcc and left out one optional step, but I need that one now. The procedure is as follows: (a) install a bunch of dependencies (b) compile gcc to phase 1 (I currently call that port i686-w64-mingw32-gcc-bootstrap) (c) install some more files (i686-w64-mingw32-

Re: meson

On 7 November 2017 at 19:18, Ryan Schmidt wrote: > We have a port for meson, a new build system. > > The libhttpseverywhere portfile uses it, and contains a lot of code for > dealing with it. > > Should we have a meson portgroup to abstract away these details? Has anyone > worked on that already?

Re: meson

Hi, On 8 November 2017 at 18:21, Rainer Müller wrote: > > I did not mean there is nothing else to do, but it seems simpler as what > is needed for cmake. meson using ninja to build is the same as cmake > using make. Just that ninja is an extra dependency as it is not assumed > to be provided by th

Additional labels for pull requests (and Trac tickets)

Hi, Something that would really help me in going through various pull requests would be additional labels that would make it clear what exactly is stopping us from merging that pull requests. Some examples (tags could/should be further simplified): - needs_review: nobody with sufficient experti

Re: Additional labels for pull requests (and Trac tickets)

On 11 November 2017 at 20:04, Jeremy Lavergne wrote: > These sound reasonable to me. > > When dealing with tags, my general encouragement is to ask: > "Are these tags the fewest necessary to reach your goal?" This is why I started the discussion. >> - needs_review: nobody with sufficient expertis

Re: meson

On 8 November 2017 at 17:29, Ryan Schmidt wrote: > > The port fails to build universal, so something is missing there. I tried a super simple hello-world program with a meson build. Setting CXXFLAGS='-arch i386 -arch x86_64' works fine there, so it must be something specific about this port.

<    1   2   3   4   5   6   7   8   >