Opened 15 years ago

Closed 15 years ago

#22612 closed defect (invalid)

Stumbling blocks : working towards install of MacPorts xorg-server, quartz and more

Reported by: aszy@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.8.1
Keywords: Cc:
Port:

Description (last modified by jmroot (Joshua Root))

Have decided to begin the process to upgrade everything that is installed and then add the MP ports that I want to use. Started with simply trying to upgrade existing: Second item on list is babl, following is output from "sudo port upgrade babl"

Gulliver:~ aszy$ sudo port upgrade babl
Password:
Warning: Skipping upgrade since boehmgc 7.1_0 >= boehmgc 7.1_0, even though installed variants "" do not match "+darwin_10". Use 'upgrade --enforce-variants' to switch to the requested variants.
Warning: Skipping upgrade since ncursesw 5.7_0 >= ncursesw 5.7_0, even though installed variants "" do not match "+darwin_10". Use 'upgrade --enforce-variants' to switch to the requested variants.
Warning: Skipping upgrade since ncurses 5.7_0 >= ncurses 5.7_0, even though installed variants "" do not match "+darwin_10". Use 'upgrade --enforce-variants' to switch to the requested variants.
--->  Computing dependencies for glib2
--->  Configuring glib2
Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_glib2/work/glib-2.22.2" && ./configure --prefix=/opt/local --enable-static " returned error 1
Command output: checking for /usr/bin/gcc-4.2 option to accept ISO C89... (cached) none needed
checking dependency style of /usr/bin/gcc-4.2... (cached) gcc3
checking how to run the C preprocessor... /usr/bin/gcc-4.2 -E
checking for c++... /usr/bin/g++-4.2
checking whether we are using the GNU C++ compiler... yes
checking whether /usr/bin/g++-4.2 accepts -g... yes
checking dependency style of /usr/bin/g++-4.2... gcc3
checking for gcc... (cached) /usr/bin/gcc-4.2
checking whether we are using the GNU C compiler... (cached) yes
checking whether /usr/bin/gcc-4.2 accepts -g... (cached) yes
checking for /usr/bin/gcc-4.2 option to accept ISO C89... (cached) none needed
checking dependency style of /usr/bin/gcc-4.2... (cached) gcc3
checking whether /usr/bin/gcc-4.2 and cc understand -c and -o together... yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... no
checking for pkg-config... /opt/local/bin/pkg-config
checking for gawk... (cached) awk
checking for perl5... /opt/local/bin/perl
checking for indent... indent
checking for /opt/local/bin/perl... /opt/local/bin/perl
checking for a Python interpreter with version >= 2.4... python
checking for python... /opt/local/bin/python
checking for python version... 2.5
checking for python platform... darwin
checking for python script directory... ${prefix}/lib/python2.5/site-packages
checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages
checking for iconv_open... no
checking for libiconv_open in -liconv... no
checking for iconv_open in -liconv... no
configure: error: *** No iconv() implementation found in C library or libiconv

Error: Unable to upgrade port: 1

Subsequently I performed the following:

Gulliver:~ aszy$ port search libiconv
libiconv @1.13 (textproc)
    Character set conversion library

php5-iconv @5.3.0 (php, textproc)
    a PHP interface to the libiconv character encoding conversion functions

Found 2 ports.

then


Gulliver:~ aszy$ sudo port install libiconv
--->  Computing dependencies for libiconv
--->  Cleaning libiconv
Gulliver:~ aszy$ 

and ran the upgrade again, with complaints about libiconv, iconv_open

I am getting increasingly frustrated that at every step to get a MacPort up and running, I am getting a roadblock. I appreciate the nature of the MacPort system, and I really don't think that I am doing anything unique. I have at least 30 more upgrades to go before I actually start on the dependencies tree for the actual applications that I want to run. More than anything, I would like guidance as to how to a) recognize what is going wrong, and b) how to solve these without having to post a ticket every time. I cannot imagine that you all ( thanks to you all by the way ) really want to spend your time tracking these "bugs" any more than I do. Running MacBook Pro, Snow Leopard, latest Xcode, latest MacPorts listing. Thanks, Al

Change History (1)

comment:1 Changed 15 years ago by jmroot (Joshua Root)

Description: modified (diff)
Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.