Re: GitHub migration complete

> On Oct 31, 2016, at 1:16 PM, Thibaut Paumard wrote: > > Le 31/10/2016 à 17:23, Lawrence Velázquez a écrit : >>> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote: >>> >>>> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit : >>>>>

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 (including developers and mainta

Re: GitHub migration complete

> On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > Our Subversion repository has been split into several repositories on > GitHub. Please note that Ryan ran the svn2git conversion several times this weekend, so any clones made previously will have nothing in common with the final repositorie

Re: command line tools for Xcode 8.1?

> On Oct 28, 2016, at 3:34 PM, Murray Eisenberg > wrote: > > Under OS X 10.11.6, I just updated Xcode to version 8.1 via App Store. > > Release notes for Xcode 8.1 say: > > Known Issues > • There are no Command Line Tools (OS X 10.11) for Xcode 8.1. > Xcode 8.1 contains SDKs

Re: Servers down?

> On Oct 22, 2016, at 5:11 PM, Fielding, Eric J (329A) > wrote: > > I am guessing that the lack of access to MacPorts yesterday (Friday) > may have been related to the massive DDoS attack on the Dyn DNS > servers. This seems unlikely to me, as our unplanned downtime began (I think) on Thursday

Re: Moving to GitHub: Status Update, Action Required

> On Oct 22, 2016, at 9:40 AM, Marko Käning wrote: > >> On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote: >> >> as well as the "hub" command line program in the "hub" port. > > Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on the > wiki page. I've added several tools to the l

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote: > >> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote: >> >>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven >>> wrote: >>> >>> Also, is the consensus that a graphical user interfa

Re: Moving to GitHub: Status Update, Action Required

> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote: > > However, would it be possible to add a tangible example of updating > a port to that page? > > I know a little bit about Subversion and less about Git. I would like > to see a soup-to-nuts example of cloning the ports tree, updating >

Re: Servers down?

> On Oct 21, 2016, at 5:30 PM, Carlo Tambuatco wrote: > > I can't even get to the migration page on macports.org... Yes, {svn,trac}.macports.org is still down, and probably others. vq ___ macports-users mailing list macports-users@lists.macosforge.or

Re: webkit-gtk2: Will it ever be fixed?

> On Oct 17, 2016, at 9:07 PM, Bachsau wrote: > > Am 18.10.16 um 02:35 schrieb Lawrence Velázquez: >> You probably want webkit2-gtk. > > Yes, this is what I tried to install and fails, sorry. Do one of these correspond to the problem you're seeing? If not, please

Re: webkit-gtk2: Will it ever be fixed?

> On Oct 17, 2016, at 8:19 PM, Bachsau wrote: > > Am 18.10.2016 um 01:19 schrieb Lawrence Velázquez: >> Are you talking about webkit-gtk-2.0? > > I think so. Whats the alternative? You probably want webkit2-gtk. % port echo 'webkit*' webkit-gtk webkit-gtk-2

Re: webkit-getk2: Will it ever be fixed?

> On Oct 17, 2016, at 7:13 PM, Bachsau wrote: > > Since my upgrade to macOS sierra I tried compiling and installing webkit-gtk2 > for weeks, again and again. Even though I got a new version every time, it > still fails to build. > > Will it ever be fixed? I find it so disturbing that I always

Re: python, port select and group

Hello, > On Oct 13, 2016, at 7:30 AM, Björn Raupach wrote: > > At first I assumed it sets the default symlink for the command in > /usr/bin MacPorts almost never touches /usr. The "port select" command creates symlinks under $prefix, according to rules specified by the relevant *_select port.

Re: OpenSSL 1.0.2j won't connect to Google

> On Oct 4, 2016, at 12:48 AM, S P Arif Sahari Wibowo > wrote: > > Macports upgraded my OpenSSL to 1.0.2j and now it cannot connect to Google > servers. Other than updating to the latest releases, we have not made any significant changes to the openssl port since 1.0.2h. https://trac.macports

Re: Please : unsubscribe my account

> On Oct 3, 2016, at 11:43 AM, Abdulrahman Alshammari > wrote: > > Thanks. You can unsubscribe using the Mailman page linked at the bottom of every macports-users email. vq ___ macports-users mailing list macports-users@lists.macosforge.org https://

Re: Address of nonexistent hosts...?

> On Sep 29, 2016, at 6:04 PM, Carlo Tambuatco > wrote: > > Just installed a port and got this message: > > Warning: Your DNS servers incorrectly claim to know the address of > nonexistent hosts. This may cause checksum mismatches for some ports. > See this page for more information: >

Re: Sierra transition: qt5-base upgrade failing

> On Sep 26, 2016, at 12:13 PM, Joseph C Slater, PhD, PE > wrote: > > Many of the packages I use have dependencies on qt5-base, as I've discovered > trying to rebuild/upgrade. > > However, it fails to build, according to the log, reporting: > :info:configureXcode not set up properly. You

Re: LibCxxOnOlderSystems - and more software that is pushing for gcc

> On Sep 25, 2016, at 11:24 AM, Ken Cunningham > wrote: > > And although the fortran compiler is written in C and C++ (according > to the gcc fortran website) it does not in the end actually link it's > output binaries to libstdc++ (as you've just demonstrated) so there is > no worry about letti

Re: LibCxxOnOlderSystems - and more software that is pushing for gcc

> On Sep 25, 2016, at 8:29 AM, Ken Cunningham > wrote: > > What is happening exactly on my MacPros running 10.11, I wonder? > Software installed by macports on 10.11 is using clang++ (mostly) and > g++ (sometimes). What MacPorts-provided software is using g++? It should not be doing that. > cl

Re: LibCxxOnOlderSystems - and more software that is pushing for gcc

> On Sep 25, 2016, at 9:49 AM, Yongwei Wu wrote: > > I actually do not think this is normally an issue. If the dynamic > libraries manage the lifetime of their own object, i.e. do not do > something like creating an object in a library but not providing > a function to destroy it (so that the app

Re: LibCxxOnOlderSystems - and more software that is pushing for gcc

> On Sep 24, 2016, at 10:12 PM, Ken Cunningham > wrote: > > I realize I asked this a bit ago about qemu, and received a very > reasonable big caution regarding any attempt to combine gcc of any > version on a system set up with LibCxxOnOlderSystems... > > but I just thought I'd mention that a fe

Re: Starting gimp2

> On Sep 24, 2016, at 4:35 PM, Jeffrey Singleton > wrote: > > You run it from command line You probably need to install "xorg-server" first. This is basically equivalent to installing XQuartz. > or you can install the latest from Gimp.org which does not require > X11 anymore. This might be wha

Re: macOS Sierra / 10.12 support - where are we?

> On Sep 21, 2016, at 3:14 PM, Brandon Allbery wrote: > >> On Wed, Sep 21, 2016 at 3:09 PM, Lawrence Velázquez >> wrote: >> >> I don't believe anyone has set off a build for the express purpose of >> creating Sierra archives, but the Sierra worker

Re: macOS Sierra / 10.12 support - where are we?

> On Sep 21, 2016, at 2:54 PM, Richard L. Hamilton wrote: > > Are the build-bots building binary packages for Sierra yet I don't believe anyone has set off a build for the express purpose of creating Sierra archives, but the Sierra worker is nonetheless quite busy. https://build.macports.org/b

Re: macOS Sierra / 10.12 support - where are we?

> On Sep 20, 2016, at 7:53 PM, Brandon Allbery wrote: > >> On Tue, Sep 20, 2016 at 7:45 PM, Arno Hautala wrote: >> >> Is an installer coming soon? > > /topic on IRC: > https://sourceforge.net/projects/macports/files/MacPorts/2.3.4/MacPorts-2.3.4-10.12-Sierra.pkg/download > - Read: https://tr

Re: MacPorts missing links

> On Sep 13, 2016, at 3:06 AM, David Epstein > wrote: > > One thing that seems to be brought out (by the erroneous answer by “port > provides ligpng.la") It's not erroneous, in the sense that libpng.la really does exist and belong to the libpng port. The problem, as Ryan had already noted, is

Re: MacPorts missing links

> On Sep 12, 2016, at 11:02 PM, Al Varnell wrote: > > Perhaps the Wiki page needs to state more clearly that this only needs to be > done for major OS X/macOS upgrades, that is from 10.11.x to 10.12, for > instance. I don't think this a problem, at all. The wiki can't get much clearer on the

Re: MacPorts missing links

> On Sep 12, 2016, at 7:25 AM, David Epstein > wrote: > > When I now run >> sudo find -L /opt/local -type l -exec port provides {} + > > I get >> /opt/local/lib/libpng.la is provided by: libpng >> /opt/local/libexec/qt4/include/QtCLucene is provided by: qt4-mac >> /opt/local/libexec/qt4/include

Re: MacPorts missing links

> On Sep 11, 2016, at 7:59 PM, David Epstein > wrote: > > In view of all my moans and groans, I would like to make it clear that I > think MacPorts is great, and it adds greatly to my productivity. I use it all > the time, and tend to regard it as “Just there and working perfectly” usually >

Re: qemu, and using gcc45+ compilers on systems set up with LibCxxOnOlderSystems and libc++

> On Sep 11, 2016, at 11:25 PM, Ken Cunningham > wrote: > > I am not totally sure how to use gcc* versions, building cxx code, when my > system has been set up for LibCxxOnOlderSystems, and all the installed ports > to date link against libc++. > > I _think_ I can just > > sudo port install

Re: MacPorts missing links

> On Sep 11, 2016, at 6:33 PM, Ryan Schmidt wrote: > >> On Sep 11, 2016, at 5:22 PM, Ryan Schmidt wrote: >> >>> On Sep 11, 2016, at 4:57 PM, David Epstein >>> wrote: >>> >>> I do not understand the issues involved and their ramifications, so I may >>> be saying something stupid, but it seem

Re: MacPorts missing links

> On Sep 11, 2016, at 5:57 PM, David Epstein > wrote: > > I’m not sure if I am allowed to put my name on some kind of cc list for the > ticket, since I’m not intending to work on the problem, but only want to know > when it has gone away. Feel free to Cc yourself on the ticket Mojca linked ea

Re: MacPorts missing links

> On Sep 11, 2016, at 6:29 PM, Ryan Schmidt wrote: > >> On Sep 11, 2016, at 5:24 PM, Brandon Allbery wrote: >>> On Sun, Sep 11, 2016 at 6:22 PM, Ryan Schmidt wrote: >>> >>> On my system I see the contents of that directory are provided by the >>> following ports: >> >> I think they're complain

Re: MacPorts missing links

> On Sep 11, 2016, at 2:41 AM, David Epstein > wrote: > > I ran the suggested find command and double checked that all the entries are > broken symlinks. Ideally I would like to get rid of all of them, but safely. > From my point of view, the danger is that these filenames occur in some > dif

Re: MacPorts missing links

> On Sep 11, 2016, at 6:24 AM, David Epstein > wrote: > > I hope that I’m believed when I say that I’m extremely careful never to > operate on /opt/local except via port. I do use programs like unix find and > unix ls that are not supposed to change anything. No, it's very clear that you have

Re: MacPorts missing links

> On Sep 11, 2016, at 4:13 AM, David Epstein > wrote: > > For those few interested in this thread, and who have not followed so far, > the relevant line of output from > “port select —summary” was >> llvm none mp-llvm-3.5 none > > I think that this is a either a bug in “port select

Re: MacPorts missing links

> On Sep 11, 2016, at 3:40 AM, David Epstein > wrote: > >> On 10 Sep 2016, at 23:10, Lawrence Velázquez wrote: > > … snip … > >>>> Did you uninstall python27? >>> >>> I think so. The ls -l command above does not find /opt/local/bin/

Re: MacPorts missing links

> On Sep 10, 2016, at 5:51 PM, David Epstein > wrote: > > I do not want to rely on my memory of which of these I have uninstalled. I > need to be told by a reliable program. Run this: find -L /opt/local -type l This will print any broken symlinks in your MacPorts prefix. Email the ou

Re: MacPorts missing links

> On Sep 10, 2016, at 5:51 PM, David Epstein > wrote: > >> On 10 Sep 2016, at 19:38, Lawrence Velázquez wrote: >> >> Did you uninstall python27? > > I think so. The ls -l command above does not find /opt/local/bin/python*, > except for symbolic links.

Re: MacPorts missing links

> On Sep 10, 2016, at 1:42 PM, David Epstein > wrote: > > I gave the command: > > ls -l /opt/local/bin/py* > and the system replied: > >> lrwxr-xr-x 1 root wheel 23 9 Jun 19:13 /opt/local/bin/pydoc@ -> >> /opt/local/bin/pydoc2.7 >> lrwxr-xr-x 1 root wheel 23 9 Jun 17:19 /opt/local/bin

Re: Can't upgrade gtk3 as part of a "upgrade outdated", Segmentation fault?

> On Aug 26, 2016, at 12:01 PM, [ftp83plus] wrote: > > This log is truncated because Pastebin doesn't accept its large size for free > users. How would I post that? https://trac.macports.org/newticket vq ___ macports-users mailing list macports-users

Re: sea.us.rsync.macports.org mirror

> On Aug 22, 2016, at 3:41 PM, Jonathan Stickel wrote: > > OK, thanks. Maybe put a note on the wiki until resolved? Done: https://trac.macports.org/wiki/Mirrors?action=diff&version=85 vq ___ macports-users mailing list macports-users@lists.macosforge.

Re: sea.us.rsync.macports.org mirror

> On Aug 22, 2016, at 3:22 PM, Jonathan Stickel wrote: > > I recently started using the sources mirror at sea.us.rsync.macports.org. I > noticed today that it looks stuck, with nothing changed since 8/5/16. I sent > an email to mir...@pnnl.gov (as suggested by the message during syncing), I >

Re: Fail to execute a custom local portfile

> On Aug 21, 2016, at 10:14 AM, Rainer Müller wrote: > >> On 2016-08-21 15:37, Giovanni Grieco wrote: >> >> But I can’t install my package via ‘port install’ because MacPorts >> throws me the following error: >> >> “Unable to execute port: Could not open file: >> /Users/…/Documents/macports/… /

Re: Idea: Port Checks for Disk Space Before Compiling?

> On Aug 11, 2016, at 12:14 PM, Ryan Schmidt wrote: > > On Aug 11, 2016, at 11:08, Jean-François Caron wrote: >> >> On Aug 11, 2016, at 09:55 , Lawrence Velázquez wrote: >> >>> The +analyzer variant is already enabled by default. Which clang port a

Re: Idea: Port Checks for Disk Space Before Compiling?

> On Aug 11, 2016, at 9:05 AM, Jean-François Caron wrote: > > I’m glad my idea wasn’t as silly as I had thought. Maybe this will go > somewhere. > > I needed to build clang locally because I use the +analyzer variant. Maybe > this variant could be made default, since it has no performance

Re: Idea: Port Checks for Disk Space Before Compiling?

> On Aug 10, 2016, at 9:04 PM, Ryan Schmidt wrote: > >> On Aug 10, 2016, at 5:15 PM, Mojca Miklavec wrote: >> >> The major problem is that there is basically no way to predict how >> much space an installation of a port from source might need (one might >> be able to do some heuristics based on

Re: how to install an earlier version?

On Aug 10, 2016, at 8:30 PM, Jim DeLaHunt wrote: > I have the current version of a port installed. I have never had an > earlier version installed. But I would like to install an earlier > version now. How can I do this? https://trac.macports.org/wiki/howto/InstallingOlderPort vq _

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 30, 2016, at 7:24 PM, [ftp83plus] wrote: > > Should I simply let step 2 as it was, not > sudo port -v install libcxx +universal > > but > > sudo port -v install libcxx > > like I did when it failed the first time? I doubt that has anything to do with the Python crash. vq __

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 30, 2016, at 1:57 PM, [ftp83plus] wrote: > Python 27 fails to build: http://pastebin.com/zJZM4vM8 and log: > http://pastebin.com/0L1rTQZP > > What is the issue this time? https://trac.macports.org/ticket/51891 vq ___ macports-users mailing li

Re: clang 3.4 can't be configured (part of a selfupdate)

On Jul 30, 2016, at 8:58 AM, [ftp83plus] wrote: > So should I rebuild libcxx +universal variant first before performing > Step 4 of the LibcxxOnOlderSystems? Yes, unless you can figure out why libomp is being installed +universal and prevent that. vq

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 1:35 AM, Ken Cunningham > wrote: > > Hi, > > There are many here smarter than me, but it would see your error is > here: > >> /opt/local/bin/clang++-mp-3.3 -pipe -Os -stdlib=libc++ -arch i386 >> -mmacosx-version-min=10.6 -Wl,-search_paths_first >> -Wl,-headerpad_max_

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 4:05 PM, Ken Cunningham > wrote: > > I believe macports automatically sets build_arch to the proper value > depending on your hardware . > > > > Don't forget,

Re: clang 3.4 can't be configured (part of a selfupdate)

> On Jul 29, 2016, at 10:57 AM, [ftp83plus] wrote: > > And why would it use clang-3.3 when it's explicitly told to use clang 3.4? The build failure is in libomp, which has the following compiler whitelist: # According to documentation builds with clang >= 3.3 compiler.whitelist cla

Re: New Mac OS Forge administrator

On Nov 19, 2015, at 9:49 PM, Ryan Schmidt wrote: > I'm pleased finally to be able to tell you that I have been hired to be your > new Mac OS Forge administrator. wait what WHAT vq ___ macports-users mailing list macports-users@lists.macosforge.org h

Fwd: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

o > fail during configuration. > Date: June 25, 2015 at 12:40:12 AM EDT > To: Lawrence Velázquez > Cc: Ryan Schmidt , > "macports-users@lists.macosforge.org" > > > > On Wednesday, June 24, 2015, Lawrence Velázquez <mailto:lar...@macports.org>>

Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

On Jun 24, 2015, at 8:02 PM, Ryan Schmidt wrote: > On Jun 24, 2015, at 5:10 PM, Christopher Ramos wrote: > >> Perhaps it would be feasible to employ an agent or daemon that logs >> all changes to a user's installation. That way, if it's ever bungled >> by an "outside force," the user could do so

Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

On Jun 24, 2015, at 2:31 PM, Christopher Ramos wrote: > "You can systematically avoid it by letting the operating system's > security do its thing: Don't use superuser privileges to build > software, and don't use them to install unless you know what it's > going to do." > > Wow, you know, wow.

Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

On Jun 23, 2015, at 11:03 PM, Christopher D. Ramos wrote: > That said, I don't think it's merely incidental. I assure you that it is. > After all, git is, in a sense, part of the Macports ecosystem by > virtue of a version of it being hosted by Macports. Is there not > a policy about hosting po

Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

On Jun 23, 2015, at 5:20 PM, Christopher David Ramos wrote: > Please forgive me if what I'm suggesting is not feasible. That said, it was > my understanding that makefiles include instructions on what and where > libraries should be built. More or less. > If there were a special Macports ver

Re: How to fix faulty symlink in XCode 3.2.6, issue 14018?

On Jun 20, 2015, at 8:49 PM, semaphor...@yahoo.com wrote: > I get the same error in the main.log from the gnuradio port: >> :info:configure CMake Warning at >> /opt/local/share/cmake-3.2/Modules/Platform/Darwin.cmake:182 (message): >> :info:configure The SDK Library/Frameworks path >> :info:con

Re: [MacPorts] #47755: Broken symlink left by select code when selected port is deactivated causes poppler and other ports using aclocal to fail during configuration.

Moving this to macports-users, as it's quite off-topic for the ticket. You may have to subscribe to the list to respond. https://trac.macports.org/wiki/MailingLists On Jun 19, 2015, at 3:59 PM, MacPorts wrote: > #47755: Broken symlink left by select code when selected port is > deactivated cau

Re: ipython notebook problem

On Jun 19, 2015, at 1:39 PM, Sean Farley wrote: > Peter Danecek writes: > >> Any news on this? >> Or should I have a look at it? > > Ack, I completely forgot about this. If you can do it, that'd be great. I've created a port for functools32. https://trac.macports.org/browser/trunk/dports/pyt

Re: Error installing py-virtualenvwrapper

On Jun 16, 2015, at 11:47 PM, Yang Zhang wrote: > Ran into the below error—not sure what the next steps are as this > doesn't necessarily seem like an issue with MacPorts itself, but I'm > not sure. Below is the log > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.or

Re: Error installing py-virtualenvwrapper

On Jun 16, 2015, at 11:53 PM, Brandon Allbery wrote: > On Tue, Jun 16, 2015 at 11:47 PM, Yang Zhang wrote: >> :info:build Download error on https://pypi.python.org/simple/pbr/ : [SSL: >> CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) -- Some >> packages may not be found! >

Re: ipython notebook problem

On Jun 15, 2015, at 3:07 PM, Brandon Allbery wrote: > On Mon, Jun 15, 2015 at 3:01 PM, Gideon Simpson > wrote: > >> ImportError: No module named functools32 >> >> IPython notebook format depends on the jsonschema package: > > I think the bottom part is boilerplate; functools32 is not par

Re: ipython notebook problem

On Jun 15, 2015, at 3:01 PM, Gideon Simpson wrote: > When I try launching ipython notebook, I get the error: > > > ImportError: No module named functools32 > > IPython notebook format depends on the jsonschema package: > > https://pypi.python.org/pypi/jsonschema > > P

Re: [MacPorts] #47790: pstree: update to 2.39 2.39)

On Jun 8, 2015, at 8:32 AM, Jan Stary wrote: > Are the ports that install no libraries supposed to say so? Yes. This prevents MacPorts from rebuilding them as +universal if a dependent's architecture doesn't match. > From the top of my head, there are many ports that don't. Those ports are wro

Re: accelerated zlib experiment (and parallel afsctool)

On Jun 5, 2015, at 4:17 PM, René J.V. Bertin wrote: > Rather as a different port I think, or simply as an update to the existing > port, but only if there's demand. There's no difference. The point is that we don't want to become a de facto upstream. vq ___

Re: zlib acceleration?

On May 29, 2015, at 8:52 AM, Rainer Müller wrote: > Even if this CloudFlare patch offers any performance improvements, the > authors did not bother to implement it the sane way respecting licenses > for further distribution. In this form, it will never be included > upstream and we should not do

Re: "`port -pf upgrade outdated` is incredibly unsafe" ??

On May 28, 2015, at 2:47 PM, René J.V. Bertin wrote: > It should be safe to build ports that do not depend directly on a failed > port, but it seems not impossible that the ABI-changing effect of the update > of an indirect dependency permeates to a direct dependency. I would consider this a b

Re: "`port -pf upgrade outdated` is incredibly unsafe" ??

On May 28, 2015, at 1:09 PM, Kurt Pfeifle wrote: > Ok then: which one of the two switches is the unsafe one? I guess the -f? Or > has the combination of the two even more damage potential? They're both unsafe. "-f" does different things depending on the build phase, but all of them amount to

Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?

On May 28, 2015, at 1:01 PM, René J.V. Bertin wrote: > On Thursday May 28 2015 12:42:20 Lawrence Velázquez wrote: > >> So the OP is trying to build ImageMagick x86_64. > > Are there ways to that other than requesting a +universal build of it, or of > another port which h

Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?

On May 28, 2015, at 11:22 AM, René J.V. Bertin wrote: > Was he doing a universal build? ImageMagick doesn't have +universal as a > default variant, so I don't see why one would need universal_archs if one > just wants or needs to build the entire tree in 32bit mode ... MacPorts tries to remedy

Re: yosemite and 2008/9 macbookpro compatability, macports install settings for older architecture?

On May 28, 2015, at 9:16 AM, ^. .^ wrote: > when running macports to install software i get the following error > > > Error: Cannot install ImageMagick for the arch(s) 'x86_64' because > Error: its dependency libtool is only installed for the arch 'i386' > Error: and the configured univers

Re: Zathura (0.3.3_0) fails to upgrade

On May 27, 2015, at 4:37 PM, Kurt Pfeifle wrote: > > $ sudo port -pf upgrade zathura > ---> Computing dependencies for zathura > ---> Building zathura > Error: org.macports.build for port zathura returned: command execution failed > Please see the log file for port zathura for details: >

Re: zlib acceleration?

On May 27, 2015, at 3:50 PM, René J.V. Bertin wrote: > The link to the zlib ML on that page has gone stale, so I can't check whether > those Intel patches ever made it into zlib Probably not, given that the latest upstream release occurred months prior. > Does anyone know what the status is on

Re: Backing up MacPorts directories

On May 26, 2015, at 7:11 AM, Steve Holden wrote: > Is it recommended to omit any of the directories under > ‘/opt/local/var/macports’ from backups (e.g. ‘distfiles’, ‘sources’)? > https://guide.macports.org/#internals.hierarchy > > Whilst I’d like a fully-functioning MacPorts installation if I h

Re: libjpeg vs. libjpeg-turbo

On May 25, 2015, at 10:23 AM, René J.V. Bertin wrote: > I did discover one obstacle to swapping libjpeg.8.dylib from port:jpeg and > port:libjpeg-turbo: the former sets compatibility version 13.0.0, the latter > version 9.0.0 . BTW, libjpeg.9.dylib has compat. version 11.0.0 ... so I'm > not s

Re: libjpeg vs. libjpeg-turbo

On May 24, 2015, at 10:52 PM, Ryan Schmidt wrote: > ...I assumed it was also about performance. If we object to changes > IJG is making to jpeg, we can also just stop updating jpeg past 9, or > we can downgrade it to 8. I suppose I should have said that *my* interest in this discussion is about

Re: libjpeg vs. libjpeg-turbo

On May 24, 2015, at 9:00 PM, Ryan Schmidt wrote: > On May 24, 2015, at 9:43 AM, René J.V. Bertin wrote: > >> I think I made it clear that I have this requirement, but I suppose I'll >> just keep extending my own port repository. > > No, sorry, I missed that you have this requirement. Why do yo

Re: libjpeg vs. libjpeg-turbo

On May 23, 2015, at 9:04 PM, Ryan Schmidt wrote: > I do wish to do at least some basic functionality testing of a libjpeg > replacement on Tiger and Leopard. I do not want to be the cause of much of > MacPorts ceasing to function properly for users of those systems, if it can > be reasonably a

Re: libjpeg vs. libjpeg-turbo

On May 22, 2015, at 10:06 AM, Daniel J. Luke wrote: >> On May 21, 2015, at 11:11 PM, Mihai Moldovan wrote: >>> This would involve verifying that libjpeg-turbo works (or at least builds) >>> correctly on PowerPC and Intel Macs running 10.4 and up. >> >> This could become an issue on PPC and olde

Re: libjpeg vs. libjpeg-turbo

On May 22, 2015, at 10:06 AM, Daniel J. Luke wrote: > On May 21, 2015, at 11:11 PM, Mihai Moldovan wrote: > >> This could become an issue on PPC and older versions. Who can test, whether >> current libjpeg-turbo builds? > > also, that’s ridiculous since we only officially support the current a

Re: libjpeg vs. libjpeg-turbo

On May 20, 2015, at 6:31 AM, René J.V. Bertin wrote: > As a related question: libjpeg-turbo depends on port:nasm, but I cannot get > it NOT to insist on reinstalling nasm+universal, not even using a > path:${prefix}/bin/nasm style dependency. How to get around that? Evidently > there is no poi

Re: migration question

On Apr 11, 2015, at 8:46 AM, René J.V. Bertin wrote: > On Saturday April 11 2015 06:27:21 Ryan Schmidt wrote: > >> Unless you plan to meticulously analyze each port's build script, you won't >> know whether that build script makes > > It's not like it's difficult to search for os.platform and/

Re: Changing PATH and downloading mpich-default

On Apr 5, 2015, at 12:58 PM, Evan Phillips wrote: > Mihai - here it is: > http://pastebin.com/tp8LjW2U Neither of these logs is complete. DEBUG: Executing org.macports.main (llvm-3.5) DEBUG: Privilege de-escalation not attempted as not running as root. DEBUG: Skipping completed org.

Re: about Qt 5.x and OS X 10.6

> On Mar 20, 2015, at 4:46 PM, René J.V. Bertin wrote: > > So I am now exploring an option that may be a bit unusual: OS-specific port > versions. Nothing as fancy as it seems: for OS X 10.6 users > port:qt5-mac-devel will appear to be at 5.3.2 and for all other users it will > appear to be at

Trac is back (eom)

___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Announce: OpenSSH 6.8 released (fwd)

On Mar 18, 2015, at 4:46 PM, Dave Horsfall wrote: > Someone might want to take a look at this; both the BSD people and the > Penguins are all over it. https://trac.macports.org/ticket/47190 vq ___ macports-users mailing list macports-users@lists.maco

Re: /Library/Frameworks no longer a default location?

On Mar 12, 2015, at 9:44 AM, René J.V. Bertin wrote: > Not really MacPorts-related, but is it true that /Library/Frameworks > is no longer searched automatically by the compiler and linker, as > suggested by https://codereview.qt-project.org/108400 ? Not sure how you're concluding that; that bug

Re: handbrake?

On Jan 26, 2015, at 11:15 AM, Lawrence Velázquez wrote: > I have been working on this for the past couple of weeks I'm done. http://trac.macports.org/log/?rev=132828&stop_rev=132815 Here's the meat. http://trac.macports.org/cha

Re: /etc/paths

On Feb 6, 2015, at 1:49 PM, Michael wrote: > On 2015-02-06, at 10:25 AM, Luc Bourhis wrote: > >> Not launchd, no. It's for the shell and it helps with MANPATH too. "man >> path_helper" for the details. > > Interesting. I'm surprised MacPorts doesn't stuff something in there. (1) We consider

Re: [git] fatal: HTML documentation is not provided by this distribution of git

On Feb 5, 2015, at 8:11 AM, Luc J. Bourhis wrote: > "git help -w" returns > > fatal: HTML documentation is not provided by this distribution of git > > even though /opt/local/share/doc/git-doc has the HTML doc files and "port > variants" list "[+]doc". It must be weird as Google did not return

Re: [git] fatal: HTML documentation is not provided by this distribution of git

On Feb 5, 2015, at 4:43 AM, Luc J. Bourhis wrote: > The HTML documentation is installed: > > > > but "git help" refuses to serve it: Does `git help -w` work? I have git @2.2.2_0+credential_osxkeychain+doc+pcre+perl5_16+python27+svn installed, and `git help -w` works just fine. `git help` al

Using Xcode toolchain internals (Was: apple clang vs macports clang performance)

On Jan 28, 2015, at 5:58 PM, René J.V. Bertin wrote: > Really now, even if that's true for the other stuff in there, it > shouldn't be for libclang Says who? Apple can reserve that particular library for internal use if it wants. (This doesn't mean that you *cannot* use it, it means that it's a

Re: handbrake?

On Jan 25, 2015, at 2:39 PM, Ludwig wrote: > Is any work being done on the broken Handbrake port? It's been over a year > since the last revision. I'll see what I can do with it, but I don't want to > step on toes or duplicate effort. I have been working on this for the past couple of weeks; i

Re: pulseaudio 5.0 fails to build

On Jan 23, 2015, at 5:00 AM, René J.V. Bertin wrote: > On Friday January 23 2015 01:26:20 Ryan Schmidt wrote: > >> Point and Rect are Carbon types. Carbon is obsolete and should no longer be >> used. > > Go tell that to the FOSS maintainers who use out of courtesy to us... I know > it shouldn

Re: hypermail port problem

On Jan 23, 2015, at 3:28 AM, jerome schatten wrote: > I did, Ryan and I installed it again, It took about 10 minutes -- and it > returned Software Installed at the end of the process. But command line tools > as such does not seem to appear anywhere. In the gui if you go to > Applications ->

Re: hypermail port problem

On Jan 23, 2015, at 1:31 AM, jerome schatten wrote: > *S*ystem: MacMini -- late 2014 - Yosemite 10.10.1; Xcode installed. > > I've installed macports 2.3.3 with no problems; I've installed port hypermail > with no 'apparent' problem. I've followed the MacPorts Guide every step of > the way. F

  1   2   3   4   5   6   >