Re: Macports needs a little marketing ....

> > Taking on a labor-intensive editorial role does not make MacPorts better at > installing open-source software. > Although that statement in and of itself is true, I didn’t that as the topic of this email line, nor the standard by which all is to be judged. However - indeed - message

Re: Macports needs a little marketing

That is what spooked me too. If that could not happen, I kind of liked using it. On Mon, Nov 7, 2016 at 1:17 AM, Yongwei Wu wrote: > The tool seems quite useful. However, I had a big problem with it. I > tried to use it to uninstall a few inactive ports from the "Inactive"

Re: Check for binaries

There is also this: https://packages.macports.org/ which will show you which prebuilt packages exist. eg https://packages.macports.org/qt4-mac/ that might help you out as well. K On 2017-03-28, at 1:34 PM, Adam Dershowitz wrote: > Is there any way to check if a specific port will be

Re: libgphoto2 build failed on Snow Leopard

just do sudo port -v build libgphoto2 and you'll get a new log to submit. Ken On 2017-04-11, at 3:56 PM, Richard L. Hamilton wrote: > I can do that; but will that need any more info than below? I doubt that I > kept the log, once I got it built. > >> On Apr 11, 2017, at 04:03, Ryan

Re: JPortsUI has been updated

Thanks! I think I was the one (or one of the ones, at least) who expressed surprise at the old default behaviour, so thanks very much for changing that. Mostly, it was unexpected... I really like your GUI interface, and appreciate the effort you've put into it to make the less-obvious parts of

Re: building from source with libc++

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

Re: building from source with libc++

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

Re: building from source with libc++

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

Re: building from source with libc++

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

Re: building from source with libc++

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

Re: qt5 build dependency on clang

On 2017-04-22, at 1:55 PM, db wrote: > On 22 Apr 2017, at 21:58, Ryan Schmidt wrote: >> Sounds plausible. What's your question / problem with this? > > Ken already point me to cxx11-1.1.tcl, but I still don't get why 4.0 isn't > whitelisted in a system whose default

Re: qt5 build dependency on clang

On 2017-04-22, at 1:55 PM, db wrote: > On 22 Apr 2017, at 21:58, Ryan Schmidt wrote: >> Sounds plausible. What's your question / problem with this? > > Ken already point me to cxx11-1.1.tcl, but I still don't get why 4.0 isn't > whitelisted in a system whose default

Re: No default port source

you appear to have commented out the default ports source. Ken On 2017-04-18, at 3:00 PM, Dave Horsfall wrote: > I keep getting this message since around 2.4.1: > >Warning: No default port source specified in > /opt/local/etc/macports/sources.conf, using last source as default > > Yet I

Re: Is anyone successfully using lout on Sierra?

already fixed in clang 4.0+, > On Aug 15, 2017, at 4:17 AM, Ryan Schmidt <ryandes...@macports.org> wrote: > > >> On Aug 11, 2017, at 17:50, Ken Cunningham wrote: >> >> Abort trap 6 has lots of references on google, e.g. >> <https://stackoverflow.com/

Re: Is anyone successfully using lout on Sierra?

indeed, without the full log cant tell what is wrong. Best, K > On Aug 11, 2017, at 10:41 AM, Barrie Stott wrote: > >> On 11 Aug 2017, at 08:52, Ryan Schmidt wrote: >> >>> On Aug 11, 2017, at 01:21, Barrie Stott wrote: >>> >>> I don’t remember

Re: Is anyone successfully using lout on Sierra?

On 2017-08-11, at 2:14 AM, Barrie Stott wrote: >> On 11 Aug 2017, at 09:50, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> indeed, without the full log cant tell what is wrong. >> >> Best, K > > Sorry about that. Here is the f

Re: Is anyone successfully using lout on Sierra?

> On Aug 11, 2017, at 7:05 PM, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: > > While this is getting sorted out properly... See: https://github.com/macports/macports-ports/pull/662

Using qemu-system-ppc from MacPorts to run MacOS 9.2.1 in 10 minutes or less - QuickStart.

[Apologies if this is off-topic for the users’ list, but I hoped this might be of interest to both users of MacPorts and the interests of the members of this list, so I thought I would share it.] It is reported qemu-system-ppc can run MacOS 8.5 to MacOSX 10.4 PPC. Here is how to make it run

Re: Portfile for audiofile trying to fetch from wrong URL

e still a nuisance, > esp. for something fairly obvious, although I wouldn't know a Portfile from a > cannoli) > >> On Jul 12, 2017, at 10:25, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> Would you be interested in learning h

Re: Portfile for audiofile trying to fetch from wrong URL

Would you be interested in learning how to make a pull request to fix this up for everyone? If not, perhaps you might open a ticket. Best, Ken > On Jul 12, 2017, at 7:06 AM, Richard L. Hamilton wrote: > > ---> Attempting to fetch audiofile-0.3.6.tar.gz from >

Re: nmap doesn't like libc++ ?

Indeed it's a c++ thing and looking through the nmap build that just completed on my 10.6 system, some, but not all, the c++ build lines have the -stdlib=libc++ on them. So that would be why you see this error, indeed, as Ryan says. You

Re: 'log2' is not a member of 'std'

See this as well: Ken On 2017-07-02, at 3:28 AM, Jan Stary wrote: > This is MacOSX 10.6.8 running various compilers provided by MacPorts. > Compiling the following C++ source > > #include > > int main(void) > { >

Re: get portfiles from all sources

> > Then this is a problem with the documentation. I am not sure how else > this could be expressed, but you will never see "duplicate ports" with > the same name. As they said in "Independence Day" -- that may not be entirely true, Mr. President. I have a local report /opt/myports, and in

Re: Retro -- Tiger/Leopard PPC - libsdl2 infrastructure now available

SDL based stuff and if possible I > still offer a universal build with ppc support. > Having SDL2 is great. > > What's the holdup with SDL2? Upstream is about to release a new version any > day now and that will be 2.0.6. > > Thanks > > Dom > >

Re: Is it time for a libc_fixes library yet?

> This is a UNIX system. Tweaking the compiler and doing clever hacks > around standard string.h seems like the opposite of "keep it simple”. > OK.

Re: Is it time for a libc_fixes library yet?

> The compiler runtime is described as "optional" at > http://clang.llvm.org/get_started.html > > so I assume a default build of clang does not use it. > Do the clangs provided by the MP ports use it by default? > All versions of clang on all version of

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

This page says clang-3.9 supports openmp if you send the compiler the flag "-fopenmp". So perhaps that might give you a place to start. If you wanted to install imagemagick with macports instead of rolling your own build, you could do

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

On 2017-04-25, at 8:01 PM, Ryan Schmidt wrote: > > >> On Apr 25, 2017, at 19:48, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> sudo port -v install imagemagick configure.cppflags-append="-fopenmp" >> configure.compile

Re: Is There a Port for a compiler compatible with OpenMP and Imagemagick

> Ken, > > That looks very promising. I do not want to use the ImageMagick port, mainly > because I need to install both IM 6 and IM 7 and there is no IM 7 port. So I > would like to do my own manual install of ImageMagick using all the ports > from MacPorts. > > I think I can resolve what I

Re: qt5 build dependency on clang

On 2017-04-25, at 9:53 AM, db wrote: > On 22 Apr 2017, at 23:05, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: >> because cxx_stdlib will equal libc++ and therefore this test (which would >> lead to the code that does the whitelisting) will fail. > >

Re: gss 1.0.3 doesn't build on OS X Leopard or Snow Leopard due to use of getline()

I started working on such a library last summer (see this thread: )https://lists.macports.org/pipermail/macports-dev/2016-August/033453.html I updated it yesterday and indeed it builds gss on 10.6 nicely. See: https://github.com/kencu/snowleopardfixes I also have a port file to install the

Re: mesa @17.1.6 build failed on Snow Leopard

Could be a problem -- 10.6 supports TLS only with gcc/libgcc at present. Not sure yet if Marcus' clang/libgcc tricks will allow TLS on 10.6. But I notice this, which could be helpful: > -DGLX_USE_TLS Might be possible to turn that off. K

Re: mesa @17.1.6 build failed on Snow Leopard

any systems are affected). Ken On 2017-08-17, at 8:02 PM, Ken Cunningham wrote: > Could be a problem -- 10.6 supports TLS only with gcc/libgcc at present. Not > sure yet if Marcus' clang/libgcc tricks will allow TLS on 10.6. > > But I notice this, which could be helpful: >

Re: gstreamer1-gst-plugins-bad fails to update

Working on it K On 2017-08-22, at 4:09 PM, Curtis Matz wrote: > I’ve cleaned the port and then tried to install but it fails to build > consistently. I’m not a developer but it appears this is the latest error in > main.log. > > :info:build

Re: How to get date when port was added? To list ports added in last 1/2/3/.../X weeks?

The Portfiles used to have the date they were added in the top line, which was handy to see if the port was ancient. This line was removed once macports moved to git, which was in a way too bad. I use something like this (from the root directory of my git fork of macports-ports) git log

Re: libzzip fails to build on Snow Leopard -> snowleopardfixes can help also

The same few missing glibc functions keep popping up over and over on snowleopard (and earlier), so I built a library that replaces the most common ones. . And a portfile to install it is here:

Re: libzzip fails to build on Snow Leopard -> snowleopardfixes can help also

On 2017-05-25, at 12:32 AM, Mojca Miklavec wrote: > > I don't know what the cleanest approach would be, but I like the idea. > I can imagine a PortGroup, something in the spirit of: > >PortGroup legacy 1.0 >legacy.support darwin 10 ># legacy.support {darwin < 11} > > which would

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

OK. I believe it's all fixed now. I added the deps as I believe them to be at present. Works great! I'll upload the new port structure to here: <https://github.com/kencu/myports/tree/master/games/openjk> and submit a PR for it shortly. Best, Ken On 2017-06-13, at 6:59 PM, Ken Cunn

Re: gss 1.0.3 doesn't build on OS X Leopard or Snow Leopard due to use of getline()

Oh, I guess I misunderstood you. I thought you were asking for a getline compatibility library for snow leopard, so that's what I steered you towards. It works, to build nss. You can use it if you like. > On Apr 30, 2017, at 8:16 AM, Richard L. Hamilton wrote: > > From my

Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion

> If you know the point in time when all the ports worked you can also > do a git checkout of the tree, switch to an old commit (from > approximately the time when everything worked) and use that one as the > main ports tree. Then you will get all the old versions back. This is a very useful

Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion

Ah, the unlucky 2%. C'est la vie. Such problems are generally always fixable, the equation being time vs benefit... K On 2017-09-16, at 8:38 PM, Ian Wadham wrote: > Hi Ken, > > On 14/09/2017, at 2:43 PM, Ken Cunningham wrote: >> Keeping a 10.7 machine going is always g

bring up a gnome desktop ?

After enjoying quite a few gnome apps over the past year, I'm still not sure if there is a way to bring up the whole gnome desktop, with clickable icons for applications, etc. I run them from the command line, but I suspect I'm missing something to make the experience work as it does on Linux.

Re: port mpkg deliverables for older systems?

You might get this to work by setting the macosx_deployment_target in macports.conf to the minimum system you want to support. See and among others. Not many ports configure their patches based on

Re: Problems with updating macports

I appears that you couldn't connect to the macports rsync server at one point. First thing I would do is try again -- perhaps it was something temporary / transient. If it fails again, then you have to look to see if you're behind a firewall, etc... Ken On 2017-09-21, at 9:04 AM, Rino

Re: ffmpeg fails to configure

Every time openjpeg does a decimal point update, it changes the headers and everything breaks. What a PITA. -- Ken file not found: openjpeg-2.0/openjpeg.h On 2017-10-06, at 12:31 PM, db wrote: > Could anyone please take a look at this log? It seems that ffmpeg 3.3.4 > misses a bunch of

Re: ffmpeg fails to configure

bad > for this very reason. > > A note in the openjpeg Portfile would be helpful. > >> On Oct 6, 2017, at 4:06 PM, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> sure. >> >> we should probably just search the macport

Re: ffmpeg fails to configure

PM, db wrote: > On 6 Oct 2017, at 21:52, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: >> Every time openjpeg does a decimal point update, it changes the headers and >> everything breaks. What a PITA. -- Ken > > Thanks. I pinned ffmpeg 3.3.3 in my loca

Re: curl error:1407742E:SSL

Oct 2017, at 17:30, Ken Cunningham <ken.cunningham.web...@gmail.com> > wrote: >> Please see <https://trac.macports.org/ticket/51516#comment:19> > > No option in config file to avoid recompiling MP? I was thinking about > symlinking to MP's version as a last resort. >

Re: establish installed dependency not in portfile

you (and I) build everthing from source because of our libc++ setting on older systems. I used to think that was bad, but now I think it has led me to learn far more than I otherwise would have. There are buildbots for almost every system running away as we speak. > On Oct 9, 2017, at 7:23

Re: Why won't Firefox die?

On 2017-10-13, at 1:25 PM, Dave Horsfall wrote: > Firefox 55.xx on Sierra. > > Before anyone whinges about this not being a MacPorts bug, I've never > observed it on my Debian box. I'm totally blanking here, Dave. What has this to do with MacPorts? There is no firefox in MacPorts, AFAIK.

Re: running macports along with homebrew

> Besides missing ports and updated versions, what appeals to me from homebrew > is cask (I have to read its documentation though), which could even install > macports. FYI, it's actually not hard to write a portfile to install a binary, and it's useful in some cases. Here's one I wrote

Re: clang and gcc7

see also On 2017-09-06, at 9:44 AM, wrote: > Is there a reason that clang-4.0 +libstdcxx (the default) requires gcc6? I am > switching to gcc7 and would like to not depend gcc6 anymore. The same is true > for

Re: Hi Sierra

I should remind you to follow the proper port migration procedures, or you'll have troubles. https://trac.macports.org/wiki/Migration On 2017-10-01, at 6:41 PM, Ken Cunningham wrote: > Your desires have been answered: > > https://distfiles.macports.org/MacPorts/MacPorts-2.

Re: curl error:1407742E:SSL

It is perfectly possible to do that, and I do it on every machine < 10.9 Please see I should write this up as a wiki page. Ken On 2017-10-03, at 8:22 AM, db wrote: > I'm getting the error below when fetching from pypi. Can I force use of

porting a gtk3 X11 application to gtk3 quartz ...

Many gtk3 applications seem to work nicely with gtk3 +quartz … Would anyone have a few pointers to some resources or a cheat sheet of some kind on how this transition is most efficiently done? I have a feeling a full rewrite of the GUI code is not needed, but as this is the first time I’m

Re: porting a gtk3 X11 application to gtk3 quartz ...

On 2017-08-26, at 10:33 PM, Ken Cunningham wrote: > > Would anyone have a few pointers to some resources or a cheat sheet of some > kind on how this transition is most efficiently done? Ah, thanks for the off-list feedback, and I'm starting to get the idea here. X11 is

Re: smake@1.2.5 fails to build on Snow Leopard

Works for me on 10.6. Sorry. $ port -v installed smake The following ports are currently installed: smake @1.2.3_0 (active) platform='darwin 10' archs='x86_64' date='2017-09-02T11:13:10-0700' $ port -v installed cdrtools The following ports are currently installed: cdrtools @3.00_1 (active)

Re: smake@1.2.5 fails to build on Snow Leopard

tools @3.00_1 (active) platform='darwin 10' archs='x86_64' > date='2017-06-21T15:32:20-0400' > myeye:~ root# port list cdrtools > cdrtools @3.01 sysutils/cdrtools > myeye:~ root# > > @3.01 is what won't install (for me) with smake @1.2.3_0.

Re: smake@1.2.5 fails to build on Snow Leopard

The configure section generates an executable to test some system functions. It is segfaulting, and not finishing writing avoffset.h. The comments at the top of avoffset.h allude to this. No idea why it works for me and not for you, though. Maybe have to ask the smake developer for help here.

Re: smake@1.2.5 fails to build on Snow Leopard

rd system. > > I had to do the same for upgrading cdrtools to succeed. > > >> On Sep 3, 2017, at 13:24, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> The configure section generates an executable to test some system functio

Re: running macports along with homebrew

I think homebrew gets attention for two reasons. 1. a one-line copy & paste install command that is pasted into the terminal (macports could / should do that too, BTW). 2. the fact that it symlinks it's stuff into /usr/local, making it easier to use it's installed products for building other

Re: Lion - All compilers are either blacklisted or unavailable

You have discovered a currently-active problem with cmake on macports, ie bootstrapping older systems is presently broken. See for some workarounds for now, until this is fixed. Best, Ken On 2017-11-28, at 8:27 AM, Franco Vaccari wrote: > Hi, > >

Re: TenFourFox on Intel

> Finally, see this: > https://sourceforge.net/p/leopard-webkit/wiki/Home/ > Just like to make a point of this project. I didn’t think this could actually be done, but in fact, here it is. An updated webkit, updated security settings, updated system root certificates, all wrapped into Safari

Re: MacPorts related questions

I find systems painfully, almost unusably, slow without an SSD. I have retrofit them into almost every system I have (including a Beige G3 tower running MacOS 9.2.2). K > On Nov 14, 2017, at 6:24 AM, William H. Magill wrote: > > > >> On Nov 14, 2017, at 8:31 AM, pagani

Re: texshop3 install - checksum problem

for an immediate fix for yourself, do sudo port -v checksum texshop3 you will be given the proper checksums then sudo vi `port file texshop3` change the checkums to the new ones, and build your port. For the longer general fix, ideally open a ticket for this, or in a perfect world open a

Re: installing binary archives as non-root user

On 2017-11-17, at 3:46 PM, bh wrote: > I use macports as a non-root user, and am trying to find a way to still be > able to install binary archives. > > I got myself write-access to /opt folder, and so I can install many ports. > However, I cannot get access to /Applications folder, and

Re: Octave out of date?

> On Nov 2, 2017, at 10:13 AM, Ray Zimmerman wrote: > > I, for one, would appreciate an up-to-date octave-devel on macports if > someone has the time. In particular, in the current build of the release > version (4.2.1) the GUI still crashes on exit. > > Thanks again, > >

Re: Octave out of date?

> On Nov 2, 2017, at 11:51 AM, Marius Schamschula wrote: > > Hi all, > > I just realized, that I could apply the patch, available from savannah, to > fix the octave GUI freeze on quit issue to octave TIP: > >

Re: clang++-mp-3.9 missing asan_osx_dynamic.dylib

there is an existing trac ticket about this…> the rpath is not set right - needs a minor fix (or a symlink). Jeremy’s too busy to get to it, and open to patches. Ken > On Nov 9, 2017, at 6:50

Re: lame and libuv now using strnlen() which is missing on Snow Leopard and earlier

I fixed both of these last evening with the snowleoparf_fixes portgroup. If you update and try again they should be OK now. K > On Nov 8, 2017, at 1:26 AM, Richard L. Hamilton wrote: > > Due to missing strnlen() which both lame and libuv now use, neither builds on > Snow

Re: MacPorts Meeting 2018

Would be nice to go. My wife is from not too far from there - near Pordenone, Italy. We were there for quite a bit of the summer this year. Very hot August. Realistically, though, not too likely to be able to come to this one. March break here in Canada is usually for desperately heading to

Re: TenFourFox on Intel

I'm very interested. I have a Portfile I started here for TenFourFox: https://github.com/kencu/myports/tree/master/www/tenfourfox It builds to a certain point and then hits an error. Forget what it was just now. But it's a good starting point. At present I use Firefox at present on 10.6.8

Re: libvpx on 10.5 and earlier

The last working version of libvpx for PPC is pegged in my TigerPorts repo, along with many other Tiger-pegged ports in that repo. https://github.com/kencu/TigerPorts/tree/master/multimedia/libvpx Best, Ken On 2017-12-11, at 1:15 PM, Ryan Schmidt wrote: > > On Dec 11, 2017, at 11:35,

Re: error: can't read "result": no such variable

On 2017-12-01, at 2:14 PM, Gideon Simpson wrote: >>> /usr/bin/sw_vers Try running it and see what happens: //usr/bin/sw_vers -productVersion | cut -f1,2 -d.

Re: switching between x11 and quartz

As you probably know, homebrew runs it's entire operation that way, symlinking into /usr/local. > On Oct 30, 2017, at 8:29 AM, Daniel J. Luke wrote: > >> On Oct 27, 2017, at 8:33 PM, Ryan Schmidt wrote: >> I don't know if anything will break if you

Re: how to select gcc7

$ port select --list gcc Available versions for gcc: gcc40 gcc42 (active) llvm-gcc42 mp-gcc5 mp-gcc6 mp-gcc7 none so sudo port select gcc mp-gcc7 should do the trick On 2017-10-25, at 7:06 PM, pagani laurent via macports-users wrote: >

Re: pan copy & paste with [cmd]+[c] / [cmd]+[v]

this might be helpful: https://superuser.com/questions/517878/why-cant-i-paste-into-xterm-xquartz > On Dec 20, 2017, at 1:02 AM, FritzS - gmx wrote: > > Hi, > the only disability with pan I have, copy & paste with [cmd]+[c] / [cmd]+[v] > don’t work. > I must do this

Re: Possible error when building "gstreamer"

you can follow along here https://trac.macports.org/ticket/56481 > On May 14, 2018, at 22:54, Dave Horsfall wrote: > > Whatever "gstreamer" is... Anyway, can anyone translate this gobbledygook > into plain English, so that I can file a bug report if necessary? > > Result

Re: Octave 4.4.0

and octave-devel could be 4.5.0 now, which I have installed, but I (grr) note the previous patch for the crash-on-exit fix no longer seems to apply, and it _still_ did the darned crash on exit thing… Ken > On May 13, 2018, at 5:35 PM, Marius Schamschula wrote: > >

kde help center -- "The file or folder help:/XYZ does not exist

More or less total KDE newbie... Almost every entry in the kde help center fails due to an error like the above. Is this something I have forgotten to install, or is it just non-functional on MacPorts installs at present? Ken

Re: How to launch after a port?

On 2018-05-11, at 12:52 PM, Ryan Schmidt wrote: > At least when Inkscape is installed with the +x11 variant, its Dock icon will > not function the way a normal Mac app's Dock icon would. Its icon will bounce > forever We should start moving ports to the new app PG enhancements so this kind of

gcc5 potential fix

If anyone else can test > and see if it works for them as well, we can commit this fix for gcc5. Ken

MacPorts Tiger Support...

Every once in a while the question of support for Tiger comes up -- it's an old but beloved system. Of course the fun advantage is that it can run MacOSX Classic and still run all the MacOS9 software from days gone by. I just thought I'd give a short update to the status of MacPorts on Tiger as

Re: Help with #!/usr/bin/perl

Easiest: move /usr/bin/perl aside and symlink in the one you want. Safest: reinplace the lot to the version you want. Ken > On Jun 16, 2018, at 15:01, Michael wrote: > > How do I avoid the out of date system Perl,

Re: Odd mpv configure series failure following fresh reinstall

On 10.13, current Xcode, everything up to date in App Store and running the newest MacPorts there is: sudo port -v -N install mpv +audiocd+bundle+caca+dvd+libarchive+network+opengl+osd+python27+rubberband+screenshot+smb+uchardet+zsh installs through to completion without touching a single

Re: gcc49 fails to build

On 2018-06-10, at 8:54 PM, Dave Horsfall wrote: > On Tue, 5 Jun 2018, Christopher Jones wrote: > > [...] > > Sorry for the delay, but I have several disparate systems here to maintain, > along with a bunch of electronics projects. Anyway... > >> Its possible you have a port installed using

Re: MacPorts 2.5.0-beta1 now available for testing

> On May 26, 2018, at 12:27 PM, Ryan Schmidt wrote: > > The error occurs when there is a mismatch between which C++ standard library > a port says it uses (by setting configure.cxx_stdlib, or by leaving it set to > its default value) and which C++ standard library

Re: MacPorts 2.5.0-beta1 now available for testing

> On May 25, 2018, at 12:05 PM, Ryan Schmidt wrote: > > It's "broken" in that it links with libstdc++, even though MacPorts believes > it will link with libc++ on your system. The rev-upgrade code in previous > versions of MacPorts did not check for this kind of

Re: MacPorts 2.5.0-beta1 now available for testing

> On May 26, 2018, at 9:49 AM, Ryan Schmidt <ryandes...@macports.org> wrote: > > > On May 26, 2018, at 11:48, Ken Cunningham wrote: > >> Well I think you did the cmake finaggeling last time Not sure you could >> find a better way, but I wait to see..

Re: issue building libgcc 7.3 on Snow Leopard

If you install libmacho sudo port -v install libmacho you should be good to go. If it works for you as well as it has for me, I'll add it as a build dep for 10.6. Please report back. Best, Ken On 2018-06-03, at 2:46 PM, Riccardo Mottola via macports-users wrote: > Hi, > > I fail to

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

The two sundials ports don't have exactly identical file names, but there is too much overlap to try a simple naming trick for installing them both it appears. If one of the ports you want to install has a bundled copy of sundials that you can statically link in, you might get away with that

Re: possible to enable debug symbols by default?

Well, to do that, you would have to change the default configure.optflags in portconfigure.tcl open /opt/local/libexec/macports/lib/port1.0/portconfigure.tcl and change default configure.optflags {-Os} to something like default configure.optflags {"-O0 -g"} perhaps, or whatever

Re: gcc49 fails to build

On 2018-06-05, at 9:42 AM, Dave Horsfall wrote: > On Mon, 4 Jun 2018, Ryan Schmidt wrote: > >> Here is the bug report corresponding to that problem: >> https://trac.macports.org/ticket/56511 > > Ooh - a utility called "sw_vers"! I wonder what other hidden gems are > lurking, essentially

Re: gcc49 fails to build

On 2018-06-05, at 9:53 AM, Ken Cunningham wrote: > build on 10.16 and 10.17 before I get shot, read this as "darwin 16 and darwin 17" please...

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

Adam, Murray -- This small patch will patch the octave Portfile to make sundials2 support a variant. If you want to install octave without sundials2 support (so you can use openmodelica which needs sundials) this should allow you to do that. The command is: sudo port -v install octave

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

gt; requires the sundials2 port (2.7.0). So, somehow it seems that upgrading > octaves requires downgrading sundials. But, that is not compatible with > openmodelica). > > > --Adam > > > >> On Jun 3, 2018, at 10:17 PM, Ken Cunningham >> wrote:

Re: How reconcile openmodelica-dvel & octave dependencies on sundials vs. sundials2

On 2018-06-04, at 8:22 AM, Adam Dershowitz wrote: >>> The odd thing is that octave 4.2.2 was working fine with sundials (which is >>> version 3.1.0_1) This doesn't seem too likely, unless Octave was ignoring sundials. Why don't you try deleting the sundials dependency in the Octave portfile

Re: Keeping selected ports to a previous version

On 2018-07-02, at 11:07 AM, Ken Cunningham wrote: > Each repository needs to have the proper structure -- a main folder, with > subfolders that match MacPorts' repo structure, and then ports in there. I should say one more thing. Each repository needs a proper structure, but it does no

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

On 2018-04-26, at 7:17 AM, Ken Cunningham wrote: > > On 2018-04-26, at 5:42 AM, Mojca Miklavec wrote: > >>> If you use the_silver_searcher on texlive-bin you will see a flag in >>> autotools build scripts called need_luajit . It looks like many different >>&g

Re: Compiling TeX Live on 10.5 (was: libatomic build failure 10.5/x86)

On 2018-04-26, at 8:24 AM, Ken Cunningham wrote: > > > well disabling luajit just leads to the same error I found when I used > > --with-system-luajit > > One or two more iterations and I we should have this :> Fixed. I'll put something up for a PR later today. Ken

  1   2   3   4   5   6   >