On Aug 14, 2013, at 10:21 PM, Bob M wrote:
> I have an MB air with internal (smallish) SSD. I need some of the programs
> provided by MacPorts at all times, but I'm happy to do all builds while
> connected to a large-ish external HD. I just hit a crisis when the /opt
> directories hit 27GB. So
On Aug 14, 2013, at 21:21, Bob M wrote:
> Hi all; I have an MB air with internal (smallish) SSD. I need some of
> the programs provided by MacPorts at all times, but I'm happy to do
> all builds while connected to a large-ish external HD. I just hit a
> crisis when the /opt directories hit 27GB.
Bob,
You could use the command
port contents
to see which files your desired port(s) really install (and presumably are
needed for those desired ports to function).
-Sterling
On Aug 14, 2013, at 7:21PM, Bob M wrote:
> Hi all; I have an MB air with internal (smallish) SSD. I need some of
> t
Hi all; I have an MB air with internal (smallish) SSD. I need some of
the programs provided by MacPorts at all times, but I'm happy to do
all builds while connected to a large-ish external HD. I just hit a
crisis when the /opt directories hit 27GB. So what I want to do is to
put as much as possible
On Aug 14, 2013, at 20:10, Wes James wrote:
> I did a seflupdate then port upgrade outdated. All went fine until git...
> This is from the log:
>
> :info:extract /usr/bin/gnutar: git-1.8.3.4/xdiff/xutils.h: Cannot open: No
> such file or directory
> :info:extract /usr/bin/gnutar: git-1.8.3.4
On Aug 14, 2013, at 9:10 PM, Wes James wrote:
> :info:extract Command failed: cd
> "/opt/local/var/macports/build/_Volumes_qlRAID_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_git-core/git-core/work"
https://trac.macports.org/ticket/39850
vq
__
I did a seflupdate then port upgrade outdated. All went fine until git...
This is from the log:
:info:extract /usr/bin/gnutar: git-1.8.3.4/xdiff/xutils.h: Cannot open: No
such file or directory
:info:extract /usr/bin/gnutar: git-1.8.3.4/zlib.c: Cannot open: No such
file or directory
:info:extract
On Aug 14, 2013, at 09:18, j. van den hoff wrote:
> On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery wrote:
>
>> The openmpi variant used to incorrectly allow that, but openmpi is itself a
>> (wrapper around a) compiler so you must either consistently use it
>> everywhere or risk odd build iss
On Aug 14, 2013, at 14:18, Phil Dobbin wrote:
> `Unable to uninstall py27-distribute @0.6.43_0, the following ports
> depend on it:
You may force the uninstallation of py27-distribute. It has been superseded by
py27-setuptools.
sudo port -f uninstall py27-distribute
On Aug 14, 2013, at 07:54, Kurt Pfeifle wrote:
> Yes, downgrading lua worked for me.
>
> Now, is there a way to shield the lua version from upgrades, so that I can
> still run "port upgrade outdated" and lua remains as-is? Otherwise I'll have
> to run all other upgrades individually…
Yes: kee
Hi, all.
On trying to run `port uninstall inactive' I'm getting:
`Unable to uninstall py27-distribute @0.6.43_0, the following ports
depend on it:
--->py27-altgraph @0.10.2_0
--->py27-dateutil @1.5_1
--->py27-nose @1.2.1_1
--->py27-pygments @1.6_0
--->py27-pyobjc @2.5.1_0
--->
On Aug 14, 2013, at 2:21 PM, Dan Aldrich wrote:
> Attempting to build gnuradio. I get the warning:
>
> WARNING: GNU Radio's VOLK component (which handles vector optimized
> instructions and routines) compiles best when using GCC. The selected
> compiler is CLANG, which will result in a fully
On Wed, Aug 14, 2013 at 2:21 PM, Dan Aldrich wrote:
> Attempting to build gnuradio. I get the warning:
>
> WARNING: GNU Radio's VOLK component (which handles vector optimized
> instructions and routines) compiles best when using GCC. The selected
> compiler is CLANG, which will result in a fully
Attempting to build gnuradio. I get the warning:
WARNING: GNU Radio's VOLK component (which handles vector optimized
instructions and routines) compiles best when using GCC. The selected compiler
is CLANG, which will result in a fully functioning GNU Radio install but the
VOLK component will n
On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery
wrote:
On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
wrote:
---> Cleaning apr-util
Error: arpack: Variant openmpi conflicts with gcc43
Error: Unable to open port: Error evaluating variants
To report a bug, follow the instructions in th
On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
wrote:
> ---> Cleaning apr-util
> Error: arpack: Variant openmpi conflicts with gcc43
> Error: Unable to open port: Error evaluating variants
> To report a bug, follow the instructions in the guide:
>
> http://guide.macports.org/#**project.tic
Thanks, Ryan, for the tip.
Yes, downgrading lua worked for me.
Now, is there a way to shield the lua version from upgrades, so that I can
still run "port upgrade outdated" and lua remains as-is? Otherwise I'll
have to run all other upgrades individually...
On Tue, Aug 13, 2013 at 10:33 PM, Ryan
not sure whether this should be reported via the ticket system:
I just tried to `upgrade outdated' after a `selfupdate' and this failed
with:
sudo port upgrade outdated
---> Fetching archive for apr
---> Attempting to fetch apr-1.4.8_0.darwin_12.x86_64.tbz2 from
http://lil.fr.packages.mac
18 matches
Mail list logo
