Re: Can brew and port be used on the same system?

OK Mike, If you care to try out a MacPorts build of OpenJK yourself, the Portfile is in reasonable working condition. > I have not yet added in all the deps -- this builds through on my system. I have SDL1.2 and SDL2 installed, and

Re: Can brew and port be used on the same system?

HFS had file IDs. I'm not sure about HFS+. You could open a file by its ID. Suppose you had a file on the desktop then copied it into a folder. Or alternatively you have a file in a folder and copy it to the desktop. The file IDs for each scenario will be different. (Hope that makes sense.)

Re: Can brew and port be used on the same system?

> > Oh -- did you know that the filenames displayed in finder do not have to have > any correlation to the filenames as seen by the shell and other programs? Or > that Finder is perfectly happy to display two different "files with the same > name"? In fact, I did notice that, and was rather

Re: Can brew and port be used on the same system?

On 2017-05-27, at 11:24 PM, Ken Cunningham wrote: > It sounds like you got a build working already, so you probably done care > about this anymore, but this Portfile Works? It launches. It behaved so poorly that ... yuck. >

Re: Can brew and port be used on the same system?

It sounds like you got a build working already, so you probably done care about this anymore, but this Portfile with it's associated patches actually does build the port. I have not added in the deps yet. It builds just fine on my

Re: Can brew and port be used on the same system?

You could install OS X in a VirtualBox virtual machine, then use nothing but brew there. Mike Crawford, Baritone mdcrawf...@gmail.com One Must Not Trifle With Wizards For It Makes Us Soggy And Hard To Light. On Sat, May 27, 2017 at 9:33 PM, Ken Cunningham

Re: Can brew and port be used on the same system?

On 2017-05-27, at 9:33 PM, Ken Cunningham wrote: > I'm about 95% finished a Portfile for OpenJK. It doesn't take but a few > minutes to make one for a port like this. It's fully built and sitting on my > hard drive. Just working out a patchfile or two for an

Re: Can brew and port be used on the same system?

I'm about 95% finished a Portfile for OpenJK. It doesn't take but a few minutes to make one for a port like this. It's fully built and sitting on my hard drive. Just working out a patchfile or two for an openGL glitch on MacOS that is widely known, and I'll test it out. If it works, I'll send

Re: Can brew and port be used on the same system?

Yes, but I'd advise against it. I thought I had to for RVM and it caused me loads of trouble. Then I learned I could set it to MacPorts and a deleted brew and never looked back. I've been using MacPorts since before Intel, so I'm attached. —Mark ___ Mark E. Anderson

Re: Can brew and port be used on the same system?

I'm told it can be done now, but can get messy. I gave up on brew several years ago. Too many conflicts back then. Sent from Janet's iPad -Al- -- Al Varnell Mountain View, CA On May 27, 2017, at 7:13 PM, Michael wrote: > So apparently the open source code version of Jedi

Re: py34-rpy2 port dependence on R...

> On May 11, 2017, at 1:10 PM, Christopher Jones > wrote: > > >> On 11 May 2017, at 5:56 pm, Carlo Tambuatco wrote: >> >> >>> On May 11, 2017, at 12:52 PM, Christopher Jones >>> wrote: >>> >>> I would suggest the

Re: py34-rpy2 port dependence on R...

> On 11 May 2017, at 5:56 pm, Carlo Tambuatco wrote: > > >> On May 11, 2017, at 12:52 PM, Christopher Jones >> wrote: >> >> I would suggest the opposite instead. Remove your external R and just use >> the MacPorts version. Any reason not to

Re: py34-rpy2 port dependence on R...

> On 11 May 2017, at 5:56 pm, Carlo Tambuatco wrote: > > >> On May 11, 2017, at 12:52 PM, Christopher Jones >> wrote: >> >> I would suggest the opposite instead. Remove your external R and just use >> the MacPorts version. Any reason not to

Re: py34-rpy2 port dependence on R...

> On May 11, 2017, at 12:52 PM, Christopher Jones > wrote: > > I would suggest the opposite instead. Remove your external R and just use the > MacPorts version. Any reason not to do this ? In general MacPorts (rightly) > ignores anything outside its ${prefix}.

Re: py34-rpy2 port dependence on R...

I would suggest the opposite instead. Remove your external R and just use the MacPorts version. Any reason not to do this ? In general MacPorts (rightly) ignores anything outside its ${prefix}. Chris > On 6 May 2017, at 3:54 am, Carlo Tambuatco wrote: > > I have the

Re: py34-rpy2 port dependence on R...

Generally using MacPorts with anything in /usr/local will cause problems, so see if R will install to another location. You may be able to use binpaths in macports.conf in the way one can with MacTeX, though this relies on ports having binary rather than port name dependencies. Let me know if

Re: Failure to build glib2 as part of xsane dependency

You need to uninstall any ports built using 4.0, then uninstall clang-4.0 and llvm-4.0, then reinstall the ports you need using clang 3.9. Chris On 09/05/17 19:56, ges...@ftp83plus.net wrote: Doesn't work. The following ports will break: cctools @895_4 ld64-latest @274.2_1 I selected

Re: Failure to build glib2 as part of xsane dependency

Doesn't work. The following ports will break: cctools @895_4 ld64-latest @274.2_1 I selected "y" anyway, but as expected, got the same error message: cctools: Variant llvm39 conflicts with llvm40 El 2017-05-09, a las 13:58, Ken Cunningham escribió: > sudo port uninstall clang-4.0 llvm-4.0

Re: Failure to build glib2 as part of xsane dependency

sudo port uninstall clang-4.0 llvm-4.0 should do it for you. don't forget to change the line in macports.conf about default_compilers, removing clang-4.0. BTW I appear to have fixed clang-4.0 for snow leopard, and depending on what Jeremy wants to do with that, it should be working in macports

Re: Failure to build glib2 as part of xsane dependency

Me again. I forgot, but how do I uninstall the broken llvm40 version? On Step 7, it complains about conflict between llvm39 and llvm 40. Thanks El 2017-05-05, a las 19:05, Ken Cunningham escribió: > > On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote: > >>> Hello there, >>> >>> I

Re: Feature request

Hi, Thanks for your advice. I will set a feature request on trac. Rmgls rm...@orange.fr > On 5 May 2017, at 23:06, Mojca Miklavec wrote: > > On 5 May 2017 at 22:04, rmgls wrote: >> hi all, >> >> installing a port compute all dependancies, and

Re: Failure to build glib2 as part of xsane dependency

On 2017-05-04, at 12:32 PM, ges...@ftp83plus.net wrote: >> Hello there, >> >> I needed to reinstall MacPorts on Snow Leopard, and followed the >> instructions in LibcxxOnOlderSystems (I recall some ports wouldn't compile >> properly without it), including the experimental steps. Only there,

Re: Feature request

On 5 May 2017 at 22:04, rmgls wrote: > hi all, > > installing a port compute all dependancies, and print: > installing ... do you want to continue Y/N? > > its ok! but what would be useful is to print the required space for all > packages: Yes, it would be nice, but we don't always know how big

Re: Frescobaldi @2.20.0_1+app apparently broken

Hi Davide, thanks for enlightening me about the $PATH settings. I have fixed that now and repeated the upgrade of Frescobaldi once more, and now it works (at least from the Terminal, but I'm sure the other one will also). Best, Thomas Am 04.05.17 um 14:03 schrieb Davide Liessi: 2017-05-04

Re: Frescobaldi @2.20.0_1+app apparently broken

Dear Thomas, 2017-05-04 13:08 GMT+02:00 Thomas Ruedas : > PYTHONPATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/:$PYTHONPATH the problem is the PYTHONPATH variable, which should not point to a Python version different from the one

Re: Frescobaldi @2.20.0_1+app apparently broken

/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/copyreg.py # code object from '/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/__pycache__/copyreg.cpython-35.pyc' import 'copyreg' # <_frozen_importlib_external.Sourc

Re: Frescobaldi @2.20.0_1+app apparently broken

Hi. 2017-05-03 0:08 GMT+02:00 Thomas Ruedas : > Traceback (most recent call last): > File "/opt/local/bin/frescobaldi", line 7, in > import main > File > "/opt/local/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/site-packages/frescobaldi_app/main.py", >

Re: Do I need +universal to be used when installing ports?

And Dosbox. > Am 30.04.2017 um 00:50 schrieb Ken Cunningham > : > > WINE is the only thing that comes to mind that really only runs i386 even on > x86_64. > > And that triggers all it’s deps to be i386 as well. > > K > > >> On Apr 28, 2017, at 8:06 AM,

Re: Do I need +universal to be used when installing ports?

WINE is the only thing that comes to mind that really only runs i386 even on x86_64. And that triggers all it’s deps to be i386 as well. K > On Apr 28, 2017, at 8:06 AM, Barrie Stott wrote: > > I have an iMac as my only computer and am near the beginning of installing

Re: Upgrading python from 27 to 36

On which interpreter is used, you can control this with (IIRC) something like port select --set python3 python3.6 port select --set python2 python2.7 port select --set python python2 # or "port select --set python python3" if you like It's most flexible to say #!/usr/bin/env python2 or

Re: Upgrading python from 27 to 36

In short, most stuff works with 2 and 3, and you should use 3. You can install both, they're independent. virtualenvs are your friend. Also, "import this" if you haven't already :) In full, it's quite complex. See https://wiki.python.org/moin/Python2orPython3 For most features and least

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Bachsau wrote: Am 02.11.2016 um 23:48 schrieb Murray Eisenberg: After upgrading from OS X El Capitan to macOS Sierra (10.12.1), I’m following the migration steps at https://trac.macports.org/wiki/Migration. Against the recommendations in that article, I discovered the easiest way to migrate

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

On Fri, 4 Nov 2016, Dominik Reichardt wrote: > For what it’s worth, as an admin of other projects and reporter of bugs > *I* do appreciate notifications of all those changes. When I report or > CC: me to a bug I want to know what happens to the report and attached > files. Me too :-)

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Am 02.11.2016 um 23:48 schrieb Murray Eisenberg: After upgrading from OS X El Capitan to macOS Sierra (10.12.1), I’m following the migration steps at https://trac.macports.org/wiki/Migration. Against the recommendations in that article, I discovered the easiest way to migrate is to reinstall

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

On 04.11.2016 09:43, René J. V. Bertin wrote: > Filtering these notifications means filtering on email content, and > with the number of MUA's I'm using that'd have to be done on the server. Which is why I suggested Sieve as the first option. Works fine for me. I use Sieve "fileinto" to sort

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

> > > I'm going to be dropping this. There's clearly even less of a community > spirit > here than I thought, so I'll just find alternative ways to make to with the > tools > at hand when I cannot get around using them. > For what it’s worth, as an admin of other projects and reporter of

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

Ralph Seichter wrote: > Have you tried using Sieve or your MUA's filter options to get rid of > e-mails you personally don't consider of interest? Notifications are a No, as I said I'd rather not. Filtering these notifications means filtering on email content, and with the number of MUA's I'm

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

> On Nov 3, 2016, at 9:10 AM, Ken Cunningham > wrote: > > (Why is this not coming to you as a prebuilt binary from the buldbots, I > wonder?) The gmp portfile explains why this is so: # Prevent precompiled binaries. # See #41614. # might not be needed if we

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Problem with re-installing my ports after migration from El Capitan to Sierra is SOLVED — at least with respect to installing gmp (upon which quite a few other ports depend)! That ‘__SWIFT_UNAVAILABLE_MSG” error, which ultimately points back to Availability.h was the clue indeed

Re: GitHub migration complete

On 2016-11-03, at 4:44 AM, René J.V. Bertin wrote: > On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > >> It's something we all have to deal with. Presumably, we will all learn over >> time. > > Presumably. Question is, who has to learn what, and how reasonable

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

>> >> If so, the workaround for that was to make a local copy of Availability.h in >> /opt/local/include and edit it there. >> I'd still reinstall Xcode and the command line tools -- but you don't have a rogue Availability.h sitting /opt/local/include do you? If so, that's your trouble. K

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

(active) platform='darwin 16' archs='x86_64' >>>> >>>> I just rebuilt it right now from source without trouble. >>>> >>>> so it's something on your machine. Jerermy points to a possibly corrupt >>>> Availability.h file in the trac ticket.

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

>> The following ports are currently installed: >>>> gmp @6.1.1_0 (active) platform='darwin 16' archs='x86_64' >>>> >>>> I just rebuilt it right now from source without trouble. >>>> >>>> so it's something on your machine. Jere

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

;> >> So you might look at that file, or just reinstall Xcode and the command line >> tools. >> >> (Why is this not coming to you as a prebuilt binary from the buldbots, I >> wonder?) >> >> >> Best, >> >> Ken >> >> >

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

wrote: > After the re-install script (from the migration instructions) got into an > infinite loop, I started to reinstall ports manually, starting with the first > one on my “myports.txt” list: analitza > > The failure came when installing that failed during the automatic

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

After the re-install script (from the migration instructions) got into an infinite loop, I started to reinstall ports manually, starting with the first one on my “myports.txt” list: analitza The failure came when installing that failed during the automatic installation of dependencies

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

On Thursday November 03 2016 12:46:18 Rainer Müller wrote: > By now I received more mails from you with complaints about this than > actual "duplicate" Trac notifications for attachment replacements... You're welcome to filter out my emails, but you certainly won't receive any notifications

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

On 2016-11-03 09:30, René J.V. Bertin wrote: > Trac never sent notifications when you added or deleted (replaced) an > attachment, but a recent introduced that as a new feature. I find > this mostly useless and even annoying because when you update > (replace, delete) an attachment there will be 2

Re: GitHub migration complete

On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > It's something we all have to deal with. Presumably, we will all learn over > time. Presumably. Question is, who has to learn what, and how reasonable is it to require that of them when the general consensus usually is that "users

Re: GitHub migration complete

Hi, - On 3 Nov, 2016, at 10:57, René J.V. Bertin rjvber...@gmail.com wrote: > last time I checked, github's issue tracker wasn't available for the ports > repo. > I presume that's on purpose, but why? Even if "we already have a bug tracker", > why would it make life harder and not easier at

Re: Poll: should Trac send email notifications when adding or replacing an attachment?

On 03.11.2016 09:30, René J.V. Bertin wrote: > For active tickets I spend too much time weeding through and deleting > emails devoid of interest. Have you tried using Sieve or your MUA's filter options to get rid of e-mails you personally don't consider of interest? Notifications are a major

Re: GitHub migration complete

A question that came up due to another ticket: last time I checked, github's issue tracker wasn't available for the ports repo. I presume that's on purpose, but why? Even if "we already have a bug tracker", why would it make life harder and not easier at least for some things? I must admit

Re: 10.6.8 and ffmpeg

Mojca Miklavec wrote: > I'm pretty sure one can make it build without 10.7 SDK, it will just > take quite a bit of work to do so. Perhaps you know if there is an > elegant way to actually patch the code in a way that would be > acceptable for upstream in case we manage to find a sufficient set of

Re: 10.6.8 and ffmpeg

On Wed, Nov 2, 2016 at 11:49 PM, Al Varnell wrote: > When I first heard about it, over a year ago, I tried to sign my wife up > and the only thing offered for free was Safari Extension developement and > that free program was dropped at the same time as they reorganized the >

Re: 10.6.8 and ffmpeg

> On Nov 2, 2016, at 10:49 PM, Al Varnell wrote: > > On Nov 2, 2016, at 8:43 PM, Ryan Schmidt wrote: >> On Nov 2, 2016, at 10:41 PM, Al Varnell wrote: >>> On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote: On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote: Most

Re: 10.6.8 and ffmpeg

Wouldn’t it just be a treat if Jeremy fixed libsdl2’s code and this all went away :> Ken > On Nov 2, 2016, at 8:49 PM, Al Varnell wrote: > > On Nov 2, 2016, at 8:43 PM, Ryan Schmidt wrote: >> On Nov 2, 2016, at 10:41 PM, Al Varnell wrote: >>> On Nov 2, 2016, at 8:38 PM,

Re: 10.6.8 and ffmpeg

On Nov 2, 2016, at 8:43 PM, Ryan Schmidt wrote: > On Nov 2, 2016, at 10:41 PM, Al Varnell wrote: >> On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote: >>> On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote: >>> Most users don't have access to Apple's developer download site and cannot >>> be

Re: 10.6.8 and ffmpeg

On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote: > On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote: > Most users don't have access to Apple's developer download site and cannot be > expected to pay $99 to be able to do so. > > Um? $99 is only if you want signing certificates. The Mac

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

no, it just points into a pthread folder. let me try building (from source) a port that triggers your err. > On Nov 2, 2016, at 8:40 PM, Ken Cunningham > wrote: > > hmmm, So do I > > lrwxr-xr-x 1 root wheel 17 31 Oct 09:43 >

Re: 10.6.8 and ffmpeg

> On Nov 2, 2016, at 10:41 PM, Al Varnell wrote: > > On Nov 2, 2016, at 8:38 PM, Brandon Allbery wrote: >> On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote: >> Most users don't have access to Apple's developer download site and cannot >> be expected to pay $99 to be able to

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

hmmm, So do I lrwxr-xr-x 1 root wheel 17 31 Oct 09:43 /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h -> pthread/pthread.h feels like we’re finding a bug, maybe. Where is that symlink pointing, I wonder? K > On

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

I do have a symlink there: [~]$ ls -la /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h lrwxr-xr-x 1 root wheel 17 Oct 28 15:04

Re: 10.6.8 and ffmpeg

On Wed, Nov 2, 2016 at 11:37 PM, Al Varnell wrote: > Most users don't have access to Apple's developer download site and cannot > be expected to pay $99 to be able to do so. Um? $99 is only if you want signing certificates. The Mac Developer subscription granting access to

Re: 10.6.8 and ffmpeg

On Nov 2, 2016, at 8:14 PM, Ken Cunningham wrote: >> Why would you do that? It can be downloaded from the Apple developer web >> site (in a newer version of Xcode). > > Well, everyone seems to feel it’s way to difficult to expect a user to do > that, so I’m trying to help you come up with an

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Is there a cure (yet)? > On Nov 2, 2016, at 11:31 PM, Brandon Allbery wrote: > > > On Wed, Nov 2, 2016 at 11:26 PM, Ken Cunningham > > > wrote: > So I'd open that file and look at line 423 and see

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

On Wed, Nov 2, 2016 at 11:26 PM, Ken Cunningham < ken.cunningham.web...@gmail.com> wrote: > So I'd open that file and look at line 423 and see if you can figure out > what is happening. It showed what was happening, clang is good about that. What was happening was an Apple-defined macro that

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/include/pthread.h:423:25: error: expected parameter declarator So I'd open that file and look at line 423 and see if you can figure out what is happening. If this is only you, then it’s

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Note that lots of ports _have_ installed OK during the process of re-installing my ports under Sierra (and after installing tMacPorts-2.3.4-10.12-Sierra package) and checking that Xcode 8.1 and Command_Line_Tools_macOS_10.12_for_Xcode_8.1 was installed, too): [~]$ sudo port installed

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Yep, just noticed that when I was about to install clang-3.8 and remembered that didn’t update for me under OS X El Capitan and I saw that ticket. > On Nov 2, 2016, at 11:17 PM, Ken Cunningham > wrote: > > Murray, I note the error in your log looks somewhat

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Murray, I note the error in your log looks somewhat like this error in trac: __SWIFT_UNAVAILABLE_MSG … Ken___ macports-users mailing list macports-users@lists.macosforge.org

Re: 10.6.8 and ffmpeg

> > Why would you do that? It can be downloaded from the Apple developer web site > (in a newer version of Xcode). Well, everyone seems to feel it’s way to difficult to expect a user to do that, so I’m trying to help you come up with an easier way. Of course, I just downloaded the darned

Re: 10.6.8 and ffmpeg

> On Nov 2, 2016, at 10:11 PM, Ken Cunningham > wrote: > >> That's just: >> >> #if MAC_OS_X_VERSION_MAX_ALLOWED < 1070 >> # error SDL for Mac OS X must be built with a 10.7 SDK or above. >> #endif /* MAC_OS_X_VERSION_MAX_ALLOWED < 1070 */ >> > > that’s what

Re: 10.6.8 and ffmpeg

> That's just: > > #if MAC_OS_X_VERSION_MAX_ALLOWED < 1070 > # error SDL for Mac OS X must be built with a 10.7 SDK or above. > #endif /* MAC_OS_X_VERSION_MAX_ALLOWED < 1070 */ > that’s what I meant when I referred to using availability macros - sorry if it was the wrong term. Mojca did an

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Port symlinks does install OK. Environment look OK to me — see below. I didn’t show my whole .profile here, but the only actual change to it since worked OK with OS X El Capitan & macports is the date in the comment line “# MacPorts Installer addition on …: adding an appropriate PATH variable

Re: 10.6.8 and ffmpeg

> On Nov 2, 2016, at 09:31, Ken Cunningham > wrote: > > > On 2016-11-02, at 2:03 AM, Jeremy Huddleston Sequoia wrote: > >> Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 >> use the 10.6 SDK effectively? >> > > I took a quick

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

All sorts of warnings and some errors in: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.1.1-x86_64/config.log Here’s the file: This file contains any messages produced by compilers while running configure, to aid

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

here’s what I do when stuff like this happens check your path `printenv` and see if it’s set correctly cat ~/.profile try “which clang” and “clang —version” try writing up a very simple “hello.c” source file and see if it compiles (with the -v option to see what happens) and whether the

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

On Wed, Nov 2, 2016 at 9:20 PM, Murray Eisenberg wrote: > I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for > Sierra. (not sure how to verify the version of command-line tools there.) Then I would want to look at config.log to determine why it

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

I did install both Xcode 8.1 and the corresponding Xcode 8.1 tools for Sierra. (not sure how to verify the version of command-line tools there.) [~”]$ xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

On Wed, Nov 2, 2016 at 9:08 PM, Murray Eisenberg wrote: > So I started doing a reinstall of ports for migration, and at first got a > “no C compiler available” Sounds like missing command line tools to me. -- brandon s allbery kf8nh

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

So I started doing a reinstall of ports for migration, and at first got a “no C compiler available”. Next I tried installing gcc, but that depends on gmp. But even trying sudo port install gmp @6.1.1_0+universal failed. Error in configure, I thing at: :debug:configure could not read

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

Removed those 3 ports from myports.txt, ran the script again. Now another infinite loop: [~:]$ sudo ./restore_ports.tcl myports.txt Error: we appear to be stuck, exiting... infinite loop while executing "sort_ports $portList" invoked from within "set operationList [sort_ports $portList]"

Re: New mailing list host: lists.macports.org

On 03.11.16 01:06, Rainer Müller wrote: > For sender domains with a strict DMARC policy (p=reject or > p=quarantine), the From address will be rewritten to the list > address and the original sender will be in Reply-To. This implies that you'll need SPF to pass for the mailing list's domain if

Re: New mailing list host: lists.macports.org

On 2016-11-03 00:33, Ralph Seichter wrote: > On 03.11.16 00:23, Ryan Schmidt wrote: > >> The new mailing list server uses an updated version of mailman that is >> supposed to handle this problem without the need to remove the email >> footers. > > If the sender signs message bodies and mailman

Re: New mailing list host: lists.macports.org

On 03.11.16 00:23, Ryan Schmidt wrote: > The new mailing list server uses an updated version of mailman that is > supposed to handle this problem without the need to remove the email > footers. If the sender signs message bodies and mailman modifies the bodies, DKIM signatures should, by design,

Re: stuck in loop with restore_ports.tcl migrating to macOS Sierra (10.12.1)

> On Nov 2, 2016, at 5:48 PM, Murray Eisenberg > wrote: > > After upgrading from OS X El Capitan to macOS Sierra (10.12.1), I’m following > the migration steps at https://trac.macports.org/wiki/Migration . > > Got to step 3. e and after downloading script

Re: New mailing list host: lists.macports.org

On 02.11.16 23:58, Gabriel Rosenkoetter wrote: > I may be mistaken, but doesn't passing mail through an intermediate > mailing list (not just normal STMP routing) inherently invalidate your > source SMTP server's DKIM signature? No, it does not, if the mailing list is configured correctly. DKIM

Re: New mailing list host: lists.macports.org

On 02 Nov, 2016, at 16:48 CST, Ralph Seichter wrote: > On 02.11.16 23:24, Rainer Müller wrote: >> as part of the move off of macOS forge, we will migrate the mailing >> lists to the new mail server. > While you are working on the ML anyway: can you please change list >

Re: New mailing list host: lists.macports.org

On 02.11.16 23:24, Rainer Müller wrote: > as part of the move off of macOS forge, we will migrate the mailing > lists to the new mail server. While you are working on the ML anyway: can you please change list settings to *not* add footer information to mail bodies or modify subject lines. These

Re: 10.6.8 and ffmpeg

On 2016-11-02, at 2:03 AM, Jeremy Huddleston Sequoia wrote: > Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 > use the 10.6 SDK effectively? > I took a quick look at the code. It has a lot of AVAILABILITY_ macros in it, a few mentioning 10.7, most of them

Re: Error in updating macports

umanth" <cs15btech11...@iith.ac.in> > Date: 01-Nov-2016 12:36 PM > Subject: Re: Error in updating macports > To: "Ryan Schmidt" <ryandes...@macports.org> > Cc: <macports-users-ow...@lists.macosforge.org> > > I've tried using different networks. With an

Re: 10.6.8 and ffmpeg

On 2 November 2016 at 10:03, Jeremy Huddleston Sequoia wrote: > Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 > use the 10.6 SDK effectively? See my analysis at https://trac.macports.org/ticket/52210#comment:9 I'm pretty sure one can make it build without 10.7

Re: 10.6.8 and ffmpeg

On 2 November 2016 at 09:46, Davide Liessi wrote: > 2016-10-30 15:38 GMT+01:00 Ryan Schmidt: >> copying the 10.7 SDK into /Developer/SDKs is the simplest solution. > > How can I get a copy of the 10.7 SDK? > I have only the 10.5 and 10.6 SDKs on my machine. I didn't test this, but I guess that

Re: 10.6.8 and ffmpeg

Do you know *why* it is requiring the 10.7 SDK to build? Why can't libsdl2 use the 10.6 SDK effectively? > On Oct 31, 2016, at 20:44, Ken Cunningham > wrote: > >> >> I’d be happy to test the minimum requirements to build it, if Richard >> doesn’t beat me to

Re: GitHub migration complete

> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote: > >> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit : >>> On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: >>> >>> This issue only affects the very small percentage of the MacPorts user >>> population

Re: GitHub migration complete

On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: > This issue only affects the very small percentage of the MacPorts user > population (including developers and maintainers) that clones the git > repository. Most users will use the rsync server, on which we do generate > portindexes for

Re: GitHub migration complete

> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin wrote: > > Clemens Lang wrote: > >> If your question is not yet answered, ask on the mailing lists so it can >> be added. > > I may have overlooked this, but does github have any provisions that would > allow > the

Re: 10.6.8 and ffmpeg

On 2016-10-31, at 2:28 AM, René J. V. Bertin wrote: > > Probably an open door, possibly a forbidden one: it may be relevant here to > block concerned ports at the latest supported version for legacy platforms? Although I think not needed for libsdl2 (which builds and works without issue on

Re: GitHub migration complete

operation. hardly worth worrying about. Additionally, git does not preserve timestamps from the repository on checkout, so you might actually end up re-generating the index locally anyway. I think that wouldn't (or shouldn't) happen as the timestamp would be newer. And of course the auto

Re: GitHub migration complete

epository on >checkout, so you might actually end up re-generating the index locally >anyway. I think that wouldn't (or shouldn't) happen as the timestamp would be newer. And of course the auto-regeneration could be deactivated if the server always serves an up-to

  1   2   3   4   5   6   7   8   9   10   >