:08 GMT+02:00 Thomas Ruedas <trg...@gmail.com>:
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 you are using.
Also,
Hi Davide,
Am 04.05.17 um 10:09 schrieb Davide Liessi:
2017-05-04 1:39 GMT+02:00 Thomas Ruedas <trg...@gmail.com>:
Your problem is really strange: Frescobaldi simply does 'import sip',
which should result in importing the Python 3.5 sip module, since you
are running Frescobaldi with Pyth
Hi,
I made an upgrade of my ports recently, and today I tried to open
frescobaldi, but it crashed with this error:
Traceback (most recent call last):
File "/opt/local/bin/frescobaldi", line 7, in
import main
File
Am 21.04.16 um 00:18 schrieb Ryan Schmidt:
That log shows the activation phase of the sqlite3, unrelated to
poppler-qt4-mac.
Either you attached the wrong main.log file, or you ran into the bug where
MacPorts
writes the wrong port's log to the file:
https://trac.macports.org/ticket/37093
It
Am 20.04.16 um 05:34 schrieb Ryan Schmidt:
I then cleaned the poppler-qt4-mac installation and tried to reinstall it, but
it still doesn't work, and the logfile doesn't really help either; at least it
doesn't show an actual error message, as it usually does in such cases. So I'm
stuck. Any
Hi,
a few days ago I installed texlive-bibtex-extra, and at some stage of
the installation, there was this message:
---> Scanning binaries for linking errors
---> Found 3 broken file(s), matching files to ports
---> Found 2 broken port(s), determining rebuild order
---> Rebuilding in order
/texbin or
similar as it was pre-10.11), but seems to have been removed.
/usr/texbin is linked to /Library/TeX/texbin/
Russell
On 30/11/15 13:18, Thomas Ruedas wrote:
Hi again,
I am just trying a newly installed texlive installation (latex-extra,
Macports 2.3.4), but it seems that something
Am 30.11.15 um 16:29 schrieb Mojca Miklavec:
On 30 November 2015 at 14:18, Thomas Ruedas <trg...@gmail.com> wrote:
Hi again,
I am just trying a newly installed texlive installation (latex-extra,
Macports 2.3.4), but it seems that something is broken.
...
mktextfm: Running mf-nowin -pr
Hi again,
I am just trying a newly installed texlive installation (latex-extra,
Macports 2.3.4), but it seems that something is broken. When I try to
compile a rather straightforward document with the following header section:
\documentclass[12pt]{article}
\usepackage[utf8]{inputenc}
Hi,
I have just installed Macports 2.3.4 from scratch on a new computer that
runs OS X 10.10.5 and has Xcode 7.1.1 and am now recompiling packages,
among them latex-extra. In the process, poppler fails to configure/build
with the errors shown below (I begin quoting from where it seems to go
Am 30.11.15 um 02:09 schrieb David Evans:
The problem is not with poppler per se but with gawk which is being used in the
configure script. It's complaining that
library /opt/local/lib/libintl.8.dylib, provided by gettext is not built for
the right architecture.
This seems to be an
On 19/8/15 7:12 AM, Ryan Schmidt wrote:
Hmm. Ok, I do see that the llvm-3.4 portfile does blacklist gcc 4.2 build 5577
and older (in other words, the versions of gcc 4.2 in Xcode 3.1.4 and earlier),
so you're right, that won't work here. However, I don't see that same blacklist
in the llvm-3.5
On 18/8/15 3:43 AM, Ryan Schmidt wrote:
I see from the above that you have cctools installed with the llvm33 variant,
which is the default on Leopard, but you could try using a newer version of
llvm with cctools, by running
sudo port install cctools +llvm36
or
sudo port install cctools +llvm35
Hi,
On 17/8/15 2:15 AM, Ryan Schmidt wrote:
One suggestion in that ticket is to make sure you have the latest Xcode. Do you?
The latest Xcode for Leopard is 3.1.4. Even if you already have 3.1.4, it
couldn't hurt to try reinstalling it; perhaps something is corrupt and
reinstalling
would fix
Hi again,
thanks for the pointer concerning the Apple ID. Turns out, I had to use
Safari instead of my ancient Firefox to make the login work.
One suggestion in that ticket is to make sure you have the latest Xcode. Do you?
The latest Xcode for Leopard is 3.1.4. Even if you already have 3.1.4,
Hi,
in the process of trying to upgrade Gnuplot via Macports (v.2.3.3), a
long, long list of other packages needed to be (re)built as well, among
them apple-gcc42. That build fails after some time; the last part of the
logfile, which seems to contain the information pertaining to the
problem
Hi,
I am trying to upgrade my outdated ports with the newest macports
version on a MacBook Pro running OSX 10.5.8. When trying to install
ld64, the build fails, essentially, as it seems, due to this error:
:info:build src/abstraction/MachOFileAbstraction.hpp:36:44: error:
Hi,
On 9/11/14 7:42 PM, Lawrence Velázquez wrote:
There is now. Run selfupdate in half an hour or so to pull down the new port.
thanks for responding so promptly. ld64 has now been built correctly
with the new unwind, but it seems that libunwind is troubling other
ports as well.
The next of my
Hi,
after the Heartbleed problem I decided to upgrade all of my outdated
ports, but here I run into a problem with py27-setuptools. The end of
the log reads as if the tarfile could not be fetched anywhere for some
reason (see bottom of this message). It does try a number of servers,
but the
On 12/4/14 12:29 PM, Ryan Schmidt wrote:
https://trac.macports.org/ticket/43172
Indeed, that's the solution. Specifically, replacing the system curl
certificate bundle with Macports' own as suggested there seems to solve
the problem.
Thanks a lot,
Thomas
Hi,
I am trying to build mono under OS 10.5.8 and get this rather useless error:
--- Computing dependencies for mono
--- Building mono
Error: org.macports.build for port mono returned: command execution failed
To report a bug, follow the instructions in the guide:
On 24/11/13 8:53 PM, Brandon Allbery wrote:
You might put that logfile somewhere where others can look at it (or if
it's small enough, gzip it and attach it to email, but web/dropbox/etc.
is better).
Sorry, I can't post it anywhere, so I'll just have to copypaste it
below; so that's
On 25/11/13 12:20 AM, Brandon Allbery wrote:
That log shows a successful install from a prebuilt package, not a build
failure.
Exactly, that's why I don't understand why the stdout output of the
macports run tells me that the build fails. Below I post a bit more of
the stdout output. The only
23 matches
Mail list logo
