On Sep 21, 2012, at 22:58, Frank J. R. Hanstick wrote:
On Sep 21, 2012, at 8:19 PM, Ryan Schmidt wrote:
On Sep 21, 2012, at 22:09, Frank J. R. Hanstick wrote:
On Sep 21, 2012, at 5:47 PM, Ryan Schmidt wrote:
On Sep 21, 2012, at 19:08, Frank J. R. Hanstick wrote:
While trying to
Hello,
The only glib I could find is in the list provided to you. I am
wondering if there are too many linking errors and broken ports:
--- Scanning binaries for linking errors: 100.0%
--- Found 4559 broken file(s), matching files to ports
--- Found 95 broken port(s), determining rebuild
On Sep 22, 2012, at 04:21, Frank J. R. Hanstick tro...@comcast.net wrote:
The only glib I could find is in the list provided to you. I am wondering if
there are too many linking errors and broken ports:
--- Scanning binaries for linking errors: 100.0%
--- Found 4559 broken file(s),
Hi,
On 22 Sep 2012, at 10:21am, Frank J. R. Hanstick tro...@comcast.net wrote:
Hello,
The only glib I could find is in the list provided to you. I am
wondering if there are too many linking errors and broken ports:
--- Scanning binaries for linking errors: 100.0%
--- Found 4559
On Sat, Sep 22, 2012 at 03:19:44PM +0100, Chris Jones wrote:
You seem to have an awful lot of inactive ports still lying around. I would
consider uninstalling them.
sudo port list inactive
will list them all, […]
port list inactive doesn't do what you expect it to do. Please read
Hello,
I also encounter the glib problem when trying to fix the broken links.
I believe the rev-update also does not kick in automatically when
when the upgrade kicks out upon detecting an error.
On Sep 22, 2012, at 3:20 AM, Ryan Schmidt wrote:
On Sep 22, 2012, at 04:21, Frank J.
On 22 Sep 2012, at 4:39pm, Clemens Lang c...@macports.org wrote:
On Sat, Sep 22, 2012 at 03:19:44PM +0100, Chris Jones wrote:
You seem to have an awful lot of inactive ports still lying around. I would
consider uninstalling them.
sudo port list inactive
will list them all, […]
port list
While trying to upgrade, the following error occurred during
configuration:
:info:configure checking for GLIB - version = 2.31.0...
:info:configure *** 'pkg-config --modversion glib-2.0' returned
2.32.4, but GLIB (2.28.8)
:info:configure *** was found! If pkg-config was correct, then it is
On Sep 21, 2012, at 19:08, Frank J. R. Hanstick tro...@comcast.net wrote:
While trying to upgrade, the following error occurred during configuration:
:info:configure checking for GLIB - version = 2.31.0...
:info:configure *** 'pkg-config --modversion glib-2.0' returned 2.32.4, but
GLIB
Hello,
glib2 @2.22.2_0+darwin
glib2 @2.22.3_0+darwin
glib2 @2.22.4_0+darwin
glib2 @2.22.4_1+darwin
glib2 @2.22.5_0+darwin
glib2 @2.24.1_0
glib2 @2.24.2_0
glib2 @2.26.0_0
glib2 @2.26.0_1
glib2 @2.26.1_0
glib2 @2.26.1_1
glib2 @2.28.1_0
glib2 @2.28.2_0
glib2 @2.28.4_0
On Sep 21, 2012, at 22:09, Frank J. R. Hanstick wrote:
On Sep 21, 2012, at 5:47 PM, Ryan Schmidt wrote:
On Sep 21, 2012, at 19:08, Frank J. R. Hanstick wrote:
While trying to upgrade, the following error occurred during configuration:
:info:configure checking for GLIB - version =
Hello,
Right where you said it would be:
config.log
Description: Binary data
On Sep 21, 2012, at 8:19 PM, Ryan Schmidt wrote:
On Sep 21, 2012, at 22:09, Frank J. R. Hanstick wrote:
On Sep 21, 2012, at 5:47 PM, Ryan Schmidt wrote:
On Sep 21, 2012, at 19:08, Frank J. R.
12 matches
Mail list logo
