Re: gd2 configuration fails on Leopard

2008-07-26 Thread Michael J. I. Jackson
Hmm...total weirdness. I just tried again (after 4 or 5 previous,  
identical attempts) and it works now. I don't need to know why, I'm  
just glad it does. ;)

Cheers.

On Jul 26, 2008, at 10:37 PM, Michael J. I. Jackson wrote:

> On a fresh Leopard install, gd2 is failing to configure properly. I  
> encountered the error while trying to install the php5 port. Here's  
> the output:
>
> $ sudo port install gd2
> --->  Fetching gd2
> --->  Verifying checksum(s) for gd2
> --->  Extracting gd2
> --->  Applying patches to gd2
> --->  Configuring gd2
> Error: Target org.macports.configure returned: shell command "cd / 
> opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync 
> .macports.org_release_ports_graphics_gd2/work/gd-2.0.35 &&  
> autoreconf" returned error 1
> Command output: configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id,  
> must contain _cv_ to be cached
> ../../lib/autoconf/general.m4:1973: AC_CACHE_VAL is expanded from...
> ../../lib/autoconf/general.m4:1993: AC_CACHE_CHECK is expanded from...
> aclocal.m4:626: AC_LIBTOOL_COMPILER_OPTION is expanded from...
> aclocal.m4:4814: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
> aclocal.m4:2662: _LT_AC_LANG_C_CONFIG is expanded from...
> aclocal.m4:2661: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
> aclocal.m4:91: AC_LIBTOOL_SETUP is expanded from...
> aclocal.m4:71: _AC_PROG_LIBTOOL is expanded from...
> aclocal.m4:36: AC_PROG_LIBTOOL is expanded from...
> configure.ac:46: the top level
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache- 
> id, must contain _cv_ to be cached
> aclocal.m4:671: AC_LIBTOOL_LINKER_OPTION is expanded from...
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, ...): suspicious cache- 
> id, must contain _cv_ to be cached
> aclocal.m4:2739: _LT_AC_LANG_CXX_CONFIG is expanded from...
> aclocal.m4:2738: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
> aclocal.m4:1798: _LT_AC_TAGCONFIG is expanded from...
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_static_works_CXX, ...): suspicious  
> cache-id, must contain _cv_ to be cached
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_pic_works_F77, ...): suspicious cache- 
> id, must contain _cv_ to be cached
> aclocal.m4:3902: _LT_AC_LANG_F77_CONFIG is expanded from...
> aclocal.m4:3901: AC_LIBTOOL_LANG_F77_CONFIG is expanded from...
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_static_works_F77, ...): suspicious  
> cache-id, must contain _cv_ to be cached
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_pic_works_GCJ, ...): suspicious cache- 
> id, must contain _cv_ to be cached
> aclocal.m4:4004: _LT_AC_LANG_GCJ_CONFIG is expanded from...
> aclocal.m4:4003: AC_LIBTOOL_LANG_GCJ_CONFIG is expanded from...
> configure.ac:46: warning:  
> AC_CACHE_VAL(lt_prog_compiler_static_works_GCJ, ...): suspicious  
> cache-id, must contain _cv_ to be cached
> configure.ac:64: error: possibly undefined macro: AM_ICONV
>  If this token and others are legitimate, please use  
> m4_pattern_allow.
>  See the Autoconf documentation.
> autoreconf: /opt/local/bin/autoconf failed with exit status: 1
>
> Error: Status 1 encountered during processing.
>
>
> Any help would be greatly appreciated!

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


gd2 configuration fails on Leopard

2008-07-26 Thread Michael J . I . Jackson
On a fresh Leopard install, gd2 is failing to configure properly. I  
encountered the error while trying to install the php5 port. Here's  
the output:

$ sudo port install gd2
--->  Fetching gd2
--->  Verifying checksum(s) for gd2
--->  Extracting gd2
--->  Applying patches to gd2
--->  Configuring gd2
Error: Target org.macports.configure returned: shell command "cd /opt/ 
local/var/macports/build/ 
_opt_local_var_macports_sources_rsync 
.macports.org_release_ports_graphics_gd2/work/gd-2.0.35 && autoreconf"  
returned error 1
Command output: configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_pic_works, ...): suspicious cache-id,  
must contain _cv_ to be cached
../../lib/autoconf/general.m4:1973: AC_CACHE_VAL is expanded from...
../../lib/autoconf/general.m4:1993: AC_CACHE_CHECK is expanded from...
aclocal.m4:626: AC_LIBTOOL_COMPILER_OPTION is expanded from...
aclocal.m4:4814: AC_LIBTOOL_PROG_COMPILER_PIC is expanded from...
aclocal.m4:2662: _LT_AC_LANG_C_CONFIG is expanded from...
aclocal.m4:2661: AC_LIBTOOL_LANG_C_CONFIG is expanded from...
aclocal.m4:91: AC_LIBTOOL_SETUP is expanded from...
aclocal.m4:71: _AC_PROG_LIBTOOL is expanded from...
aclocal.m4:36: AC_PROG_LIBTOOL is expanded from...
configure.ac:46: the top level
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_static_works, ...): suspicious cache-id,  
must contain _cv_ to be cached
aclocal.m4:671: AC_LIBTOOL_LINKER_OPTION is expanded from...
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_pic_works_CXX, ...): suspicious cache- 
id, must contain _cv_ to be cached
aclocal.m4:2739: _LT_AC_LANG_CXX_CONFIG is expanded from...
aclocal.m4:2738: AC_LIBTOOL_LANG_CXX_CONFIG is expanded from...
aclocal.m4:1798: _LT_AC_TAGCONFIG is expanded from...
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_static_works_CXX, ...): suspicious cache- 
id, must contain _cv_ to be cached
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_pic_works_F77, ...): suspicious cache- 
id, must contain _cv_ to be cached
aclocal.m4:3902: _LT_AC_LANG_F77_CONFIG is expanded from...
aclocal.m4:3901: AC_LIBTOOL_LANG_F77_CONFIG is expanded from...
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_static_works_F77, ...): suspicious cache- 
id, must contain _cv_ to be cached
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_pic_works_GCJ, ...): suspicious cache- 
id, must contain _cv_ to be cached
aclocal.m4:4004: _LT_AC_LANG_GCJ_CONFIG is expanded from...
aclocal.m4:4003: AC_LIBTOOL_LANG_GCJ_CONFIG is expanded from...
configure.ac:46: warning:  
AC_CACHE_VAL(lt_prog_compiler_static_works_GCJ, ...): suspicious cache- 
id, must contain _cv_ to be cached
configure.ac:64: error: possibly undefined macro: AM_ICONV
   If this token and others are legitimate, please use  
m4_pattern_allow.
   See the Autoconf documentation.
autoreconf: /opt/local/bin/autoconf failed with exit status: 1

Error: Status 1 encountered during processing.


Any help would be greatly appreciated!
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: more woes with php 5.2.6

2008-07-26 Thread Ryan Schmidt

On Jul 26, 2008, at 04:34, Mark Hattam wrote:

>> What got put into /opt/local/man? There should be no destroot
>> violation in this port. What does "port contents libxml2" say?
>>
>> Your system seems to be building libxml2 very differently from mine.
>> And I don't yet know why.
>>
>> Do you have anything in /usr/local or /sw which might be
>> interfering? Have you set the DYLD_LIBRARY_PATH or
>> DYLD_FALLBACK_LIBRARY_PATH variables to some value? (When you do
>> "echo $DYLD_LIBRARY_PATH" or "echo $DYLD_FALLBACK_LIBRARY_PATH" is
>> it non-empty?)
>>
>> Try uninstalling and rebuilding, this time capturing the debug info
>> and the config.log and sending those to me. Do:
>>
>> sudo port -f uninstall libxml2 @2.6.32_1
>> sudo port -d destroot libxml2 2>&1 | tee ~/Desktop/libxml2.txt
>> cp `port dir libxml2`/work/libxml2-2.6.32/config.log ~/Desktop
>> sudo port install libxml2
>>
>> Then send me config.log and libxml2.txt from your Desktop. I can
>> compare these with what my system produces and hopefully spot the
>> problem.
>
>
> Looking at /opt/local/man, the items with a Jun26 02:04 timestamp  
> seem to be
> drwxr-xr-x199 root  admin   6766 Jul 26 02:04 man1
> drwxr-xr-x   1894 root  admin  64396 Jul 26 02:04 man3
> drwxr-xr-x 12 root  admin408 Jun 28 02:04 man5
>
> man1 seems to have these
> -r--r--r-- 2 root  admin625 Jun 28 02:04 svn.1.gz
> -r--r--r-- 2 root  admin645 Jun 28 02:04 svnadmin.1.gz
> -r--r--r-- 2 root  admin648 Jun 28 02:04 svndumpfilter. 
> 1.gz
> -r--r--r-- 2 root  admin642 Jun 28 02:04 svnlook.1.gz
> -r--r--r-- 2 root  admin644 Jun 28 02:04 svnsync.1.gz
> -r--r--r-- 2 root  admin652 Jun 28 02:04 svnversion.1.gz

svn should not be installing things into /opt/local/man either. Both  
of these ports install manpages into /opt/local/share/man on my  
system like they should.

On your system is /opt/local/man a symlink pointing to /opt/local/ 
share/man
Or is /opt/local/share/man a symlink pointing to /opt/local/man
Or are both of these regular directories?


> the -d destroot log and the config.log I'll send to you personally
> rather than bog down the list.

Since 2.6.32_1, libxml2 runs autoreconf to regenerate the configure  
script. I see on your system this was done with autoconf 2.59 but on  
mine it was done with autoconf 2.62. I don't even know how that's  
possible; after deactivating the autoconf port libxml2 won't even  
begin running autoconf, complaining about items in ${prefix}/share/ 
aclocal, and if I move those aside, then it still says "error:  
Autoconf version 2.60 or higher is required".

So either you have not installed the autoconf port or you have  
installed an older version of the autoconf port or your autoconf port  
is deactivated. I would expect the autoconf port to be installed on  
your system, since libxml2 declares a build dependency on libtool  
which has a build dependency on automake which has a build dependency  
on autoconf.

Do you have the autoconf port installed? If not, install it (sudo  
port install autoconf)
Is the autoconf port active? If not, activate it (sudo port activate  
autoconf)
Is the autoconf port at version 2.62? If not, upgrade it (sudo port  
sync && sudo port upgrade autoconf) and also upgrade any other ports  
shown by "port outdated"

Then "sudo port clean --work libxml2" and "sudo port install libxml2"  
and see if we're better. If so, then adding a build dependency on  
autoconf to the libxml2 port and incrementing its revision will be  
the solution.

http://trac.macports.org/ticket/15750

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


Re: jed needs slang upgrade

2008-07-26 Thread William Davis

On Jul 26, 2008, at 7:36 PM, Ryan Schmidt wrote:

>>>
>>
>> right on the money! uninstalled slang2, and jed compiles with no  
>> problems.
>> thanks, Ryan. (btw way they were both shown as active.)
>
> Did you force the activation of either slang or slang2? MacPorts  
> should have complained when you tried to activate the second of the  
> two because they both install the file ${prefix}/include/slang.h.
>
>

I dont remember doing that, I dont normally use -f with port install,  
but I could have done.

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.4 Darwin 9.4.0
XQuartz 2.3.0 (xorg-server 1.4.2-apple5)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

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


Re: jed needs slang upgrade

2008-07-26 Thread Ryan Schmidt
On Jul 26, 2008, at 18:32, William Davis wrote:

> On Jul 26, 2008, at 6:17 PM, Ryan Schmidt wrote:
>
>> On Jul 26, 2008, at 10:40, William Davis wrote:
>>
>>> the version of jed offered by macports seems to need an upgraded
>>> version of slang to compile:
>>> **
>>> slang.h (version=10409) does not match the slang library version  
>>> (20103)
>>> Did you install slang as a shared library?  Did you run ldconfig?
>>> Perhaps you need to set the RPATH variable in the Makefile.
>>> You have an installation problem and you will need to check the  
>>> SLANG
>>> variables in the Makefile and properly set them.
>>> Also try: make clean; make
>>> **
>>
>> I updated jed to 0.99-18 in http://trac.macports.org/ticket/14872
>>
>> I did not and still do not have any trouble installing it with  
>> slang 1.4.9.
>>
>> However I see there is also a slang2 port which provides version  
>> 2.1.3. Have you somehow installed both slang and slang2? It should  
>> not be possible since both of these ports install ${prefix}/ 
>> include/slang.h.
>
> right on the money! uninstalled slang2, and jed compiles with no  
> problems.
> thanks, Ryan. (btw way they were both shown as active.)

Did you force the activation of either slang or slang2? MacPorts  
should have complained when you tried to activate the second of the  
two because they both install the file ${prefix}/include/slang.h.


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


Re: jed needs slang upgrade

2008-07-26 Thread William Davis

On Jul 26, 2008, at 6:17 PM, Ryan Schmidt wrote:

> On Jul 26, 2008, at 10:40, William Davis wrote:
>
>> the version of jed offered by macports seems to need an upgraded
>> version of slang to compile:
>> **
>> slang.h (version=10409) does not match the slang library version  
>> (20103)
>> Did you install slang as a shared library?  Did you run ldconfig?
>> Perhaps you need to set the RPATH variable in the Makefile.
>> You have an installation problem and you will need to check the SLANG
>> variables in the Makefile and properly set them.
>> Also try: make clean; make
>> **
>
> I updated jed to 0.99-18 in http://trac.macports.org/ticket/14872
>
> I did not and still do not have any trouble installing it with slang  
> 1.4.9.
>
> However I see there is also a slang2 port which provides version  
> 2.1.3. Have you somehow installed both slang and slang2? It should  
> not be possible since both of these ports install ${prefix}/include/ 
> slang.h.
>

right on the money! uninstalled slang2, and jed compiles with no  
problems.
thanks, Ryan. (btw way they were both shown as active.)

William Davis
frstanATbellsouthDOTnet
Mac OS X.5.4 Darwin 9.4.0
XQuartz 2.3.0 (xorg-server 1.4.2-apple5)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

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


Re: jed needs slang upgrade

2008-07-26 Thread Ryan Schmidt
On Jul 26, 2008, at 10:40, William Davis wrote:

> the version of jed offered by macports seems to need an upgraded
> version of slang to compile:
> **
> slang.h (version=10409) does not match the slang library version  
> (20103)
> Did you install slang as a shared library?  Did you run ldconfig?
> Perhaps you need to set the RPATH variable in the Makefile.
> You have an installation problem and you will need to check the SLANG
> variables in the Makefile and properly set them.
> Also try: make clean; make
> **

I updated jed to 0.99-18 in http://trac.macports.org/ticket/14872

I did not and still do not have any trouble installing it with slang  
1.4.9.

However I see there is also a slang2 port which provides version  
2.1.3. Have you somehow installed both slang and slang2? It should  
not be possible since both of these ports install ${prefix}/include/ 
slang.h.

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


Re: more woes with php 5.2.6

2008-07-26 Thread Mark Hattam
At 20:12 +0200 26/7/08, Rainer Müller wrote:
>Mark Hattam wrote:
>>Powerbook:~ $ sudo port clean --all
>>Can't map the URL 'file://.' to a port 
>>description file ("Could not find Portfile in 
>>/Users/markh").
>>Please verify that the directory and portfile syntax are correct.
>>To use the current port, you must be in a port's directory.
>>(you might also see this message if a pseudo-port such as
>>outdated or installed expands to no ports).
>>Error: Unable to open port: Could not find Portfile in /Users/markh
>
>You should run
>$ sudo port clean --all libxml2
>
>Rainer

OK ... doing this ...

modem-3364:~ $ sudo port clean --all libxml2
--->  Cleaning libxml2

modem-3364:~ $ sudo port -f uninstall libxml2 @2.6.32_1
--->  Unable to uninstall libxml2 2.6.32_1, the following ports depend on it:
--->libxslt
--->libxslt
Warning: Uninstall forced.  Proceeding despite dependencies.
--->  Deactivating libxml2 2.6.32_1
--->  Uninstalling libxml2 2.6.32_1

modem-3364:~ markhattam$ sudo port install libxml2
--->  Fetching libxml2
--->  Attempting to fetch libxml2-2.6.32.tar.gz 
from ftp://fr.rpmfind.net/pub/libxml/
--->  Verifying checksum(s) for libxml2
--->  Extracting libxml2
--->  Configuring libxml2
--->  Building libxml2 with target all
--->  Staging libxml2 into destroot
Warning: violation by /opt/local/man
Warning: libxml2 violates the layout of the ports-filesystems!
Warning: Please fix or indicate this misbehavior 
(if it is intended), it will be an error in 
future releases!
--->  Installing libxml2 2.6.32_1
--->  Activating libxml2 2.6.32_1
--->  Cleaning libxml2

modem-3364:~ markhattam$ cd /opt/local/lib
modem-3364:/opt/local/lib markhattam$ ls -la

lrwxr-xr-x 1 root  admin9 Jul 26 22:38 libxml2 -> libxml2.2
-rwxr-xr-x 2 root  admin  1319504 Jul 26 22:38 libxml2.2
lrwxr-xr-x 1 root  admin9 Jul 26 
22:38 libxml2.2.6.32 -> libxml2.2
-rwxr-xr-x 2 root  admin  835 Jul 26 22:38 libxml2.la


which still perpetuates the problem ...

Mark

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


Re: How do I replace system perl with MacPorts perl?

2008-07-26 Thread Rainer Müller
Erik Norgaard wrote:
[about using /usr/local as ${prefix}]
> I found no information on the current site that this is a bad idea - in 
> fact, the ${prefix} variable is the only one mentioned for those who 
> compile macports from source.

See 


Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: more woes with php 5.2.6

2008-07-26 Thread Rainer Müller
Mark Hattam wrote:
> Powerbook:~ $ sudo port clean --all
> Can't map the URL 'file://.' to a port description file ("Could not 
> find Portfile in /Users/markh").
> Please verify that the directory and portfile syntax are correct.
> To use the current port, you must be in a port's directory.
> (you might also see this message if a pseudo-port such as
> outdated or installed expands to no ports).
> Error: Unable to open port: Could not find Portfile in /Users/markh

You should run
$ sudo port clean --all libxml2

Rainer

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


Re: more woes with php 5.2.6

2008-07-26 Thread Mark Hattam
At 11:14 -0400 26/7/08, Daniel J. Luke wrote:
>On Jul 26, 2008, at 5:34 AM, Mark Hattam wrote:
>>The install
>>
>>modem-612:/usr $ sudo port install libxml2
>>--->  Installing libxml2 2.6.32_1
>>--->  Activating libxml2 2.6.32_1
>>--->  Cleaning libxml2
>>
>>again puts the same things into /opt/local/lib/
>
>
>did you do a port clean --all first?
>
>You may have an archive of the 'bad' build that is just being 
>repeatedly installed.
>--
>Daniel J. Luke



Powerbook:~ $ sudo port clean --all
Can't map the URL 'file://.' to a port description file ("Could not 
find Portfile in /Users/markh").
Please verify that the directory and portfile syntax are correct.
To use the current port, you must be in a port's directory.
(you might also see this message if a pseudo-port such as
outdated or installed expands to no ports).
Error: Unable to open port: Could not find Portfile in /Users/markh


That doesn't seem to work at all ... anyway the installation says 
it's "cleaning".

Mark

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


Re: How do I replace system perl with MacPorts perl?

2008-07-26 Thread Daniel J. Luke

On Jul 26, 2008, at 11:40 AM, Erik Norgaard wrote:
OK, I thought that was a problem with darwinports that had been  
resolved. I come from FreeBSD and like to have the same paths to my  
binaries.


/usr/local is a 'special' location for the preprocessor and linker

I ran darwinports (I switched to a 'normal' prefix some time before  
the darwinports->MacPorts transition) for a long time with ${prefix}  
set to /usr/local, but it can cause problems, so we don't recommend it.


I found no information on the current site that this is a bad idea -  
in fact, the ${prefix} variable is the only one mentioned for those  
who compile macports from source.


You should be able to set ${prefix} to just about anything and things  
will just work. The only exception is /usr/local where things will  
mostly just work but you could end up with 'strange' problems.


I find it's also nice to be able to have self-built things in their  
'normal' place (/usr/local) while keeping the macports stuff separate.


You don't want to do that (for one thing, Apple's next  
softwareupdate  may upgrade the system perl and overwrite whatever  
changes you make).
One thing you can do is change your $PATH so that just typing  
'perl'  at the command prompt runs the macports perl. You can  
change the #!  line in your perl scripts to either call the  
macports perl or to look  up perl in the environment (#! env perl)


This is problematic. Tons of scripts, my own and third party, and  
all documentation refers to the /usr/bin/perl path.


if only there were a scripting language that was good at finding and  
replacing strings of text.


The subject has been discussed thoroughly on the FreeBSD lists for  
that very reason.


The generally accepted solution AFAIK is to install perl binary as  
say /usr/local/bin/perl5.8.8 and link to it...



perl has been through a big transition before (perl4->perl5) where the  
system supplied perl may not have been the one you wanted to use, so  
it's surprising to me that you haven't seen more reference to changing  
the #! or $PATH to select the appropriate interpreter.


No one is going to stop you from overwriting the apple-supplied perl  
in /usr/bin/, but you could be breaking things (ie. any installer  
packages that have a postflight script written in perl that expect the  
apple-supplied perl), and you will break yourself on OS updates (since  
they will feel free to overwrite things in /usr/bin).


--
Daniel J. Luke
++
| * [EMAIL PROTECTED] * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: How do I replace system perl with MacPorts perl?

2008-07-26 Thread Erik Norgaard
Daniel J. Luke wrote:
> On Jul 26, 2008, at 10:50 AM, Erik Norgaard wrote:
>> This ought to be straight forward - well, maybe it is:
>>
>> I have installed macports and perl5.8 into /usr/local/bin,
> 
> We recommend that you do not set your macports ${prefix} to /usr/local  
> as it can result in some strangeness.

OK, I thought that was a problem with darwinports that had been 
resolved. I come from FreeBSD and like to have the same paths to my 
binaries.

I found no information on the current site that this is a bad idea - in 
fact, the ${prefix} variable is the only one mentioned for those who 
compile macports from source.

>> while the
>> system perl remains in /usr/bin - most manuals and scripts expect to
>> find perl in /usr/bin so they continue to use the system perl, and
>> further this has different @INC so the modules installed with macports
>> are not found.
> 
> Right, the macports perl is separate from the system perl.
> 
>> What is the recommended way of replacing the system perl (leopard)  
>> with
>> the perl of macports?
> 
> You don't want to do that (for one thing, Apple's next softwareupdate  
> may upgrade the system perl and overwrite whatever changes you make).
> 
> One thing you can do is change your $PATH so that just typing 'perl'  
> at the command prompt runs the macports perl. You can change the #!  
> line in your perl scripts to either call the macports perl or to look  
> up perl in the environment (#! env perl)

This is problematic. Tons of scripts, my own and third party, and all 
documentation refers to the /usr/bin/perl path. The subject has been 
discussed thoroughly on the FreeBSD lists for that very reason.

The generally accepted solution AFAIK is to install perl binary as say 
/usr/local/bin/perl5.8.8 and link to it...

BR, Erik

-- 
Erik Nørgaard
Ph: +34.666334818/+34.915211157  http://www.locolomo.org
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


jed needs slang upgrade

2008-07-26 Thread William Davis
the version of jed offered by macports seems to need an upgraded  
version of slang to compile:
**
slang.h (version=10409) does not match the slang library version (20103)
Did you install slang as a shared library?  Did you run ldconfig?
Perhaps you need to set the RPATH variable in the Makefile.
You have an installation problem and you will need to check the SLANG
variables in the Makefile and properly set them.
Also try: make clean; make
**



William Davis
frstanATbellsouthDOTnet
Mac OS X.5.4 Darwin 9.4.0
XQuartz 2.3.0 (xorg-server 1.4.2-apple5)
Mac Mini Intel Duo @ 1.86 GHz

Mundus vult decepi, ego non

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


Re: How do I replace system perl with MacPorts perl?

2008-07-26 Thread Daniel J. Luke

On Jul 26, 2008, at 10:50 AM, Erik Norgaard wrote:

This ought to be straight forward - well, maybe it is:

I have installed macports and perl5.8 into /usr/local/bin,


We recommend that you do not set your macports ${prefix} to /usr/local  
as it can result in some strangeness.



while the
system perl remains in /usr/bin - most manuals and scripts expect to
find perl in /usr/bin so they continue to use the system perl, and
further this has different @INC so the modules installed with macports
are not found.


Right, the macports perl is separate from the system perl.

What is the recommended way of replacing the system perl (leopard)  
with

the perl of macports?



You don't want to do that (for one thing, Apple's next softwareupdate  
may upgrade the system perl and overwrite whatever changes you make).


One thing you can do is change your $PATH so that just typing 'perl'  
at the command prompt runs the macports perl. You can change the #!  
line in your perl scripts to either call the macports perl or to look  
up perl in the environment (#! env perl)


--
Daniel J. Luke
++
| * [EMAIL PROTECTED] * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: more woes with php 5.2.6

2008-07-26 Thread Daniel J. Luke

On Jul 26, 2008, at 5:34 AM, Mark Hattam wrote:

The install

modem-612:/usr $ sudo port install libxml2
--->  Installing libxml2 2.6.32_1
--->  Activating libxml2 2.6.32_1
--->  Cleaning libxml2

again puts the same things into /opt/local/lib/



did you do a port clean --all first?

You may have an archive of the 'bad' build that is just being  
repeatedly installed.

--
Daniel J. Luke
++
| * [EMAIL PROTECTED] * |
| *-- http://www.geeklair.net -* |
++
|   Opinions expressed are mine and do not necessarily   |
|  reflect the opinions of my employer.  |
++





PGP.sig
Description: This is a digitally signed message part
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


How do I replace system perl with MacPorts perl?

2008-07-26 Thread Erik Norgaard
Hi:

This ought to be straight forward - well, maybe it is:

I have installed macports and perl5.8 into /usr/local/bin, while the 
system perl remains in /usr/bin - most manuals and scripts expect to 
find perl in /usr/bin so they continue to use the system perl, and 
further this has different @INC so the modules installed with macports 
are not found.

What is the recommended way of replacing the system perl (leopard) with 
the perl of macports?

Thanks, Erik
-- 
Erik Nørgaard
Ph: +34.666334818/+34.915211157  http://www.locolomo.org
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users


Re: more woes with php 5.2.6

2008-07-26 Thread Mark Hattam
At 23:00 -0500 25/7/08, Ryan Schmidt wrote:
>On Jul 25, 2008, at 20:09, Mark Hattam wrote:
>
>>At 17:05 -0500 25/7/08, Ryan Schmidt wrote:
>>
>>>On Jul 25, 2008, at 16:40, Mark Hattam wrote:
>>>
At 17:30 -0500 24/7/08, Ryan Schmidt wrote:

>On Jul 24, 2008, at 16:30, Mark Hattam wrote:
>
>>>On Jul 22, 2008, at 14:08, Mark Hattam wrote:
>>>
After a shutdown & restart, the Powerbook (10.4.11) wouldn't run up
Apache/php5 ... so tried uninstalling and re-installing ... Apache by
itself seems OK, but php5 won't install. Obviously it had previously,
when 5.2.6_1 first worked, but now it wont. I'm up to date on port
sync (selfupdate).


Powerbook:~ $ sudo port install  php5
@5.2.6_1+apache2+macosx+mysql5+sqlite

--->  Building php5 with target all
Error: Target org.macports.build returned: shell command " cd
"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_www_php5/work/php-5.2.6"
&& make all " returned error 2
>>>
>>>[snip]
>>>
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: warning can't open
dynamic library: /opt/local/lib/libxml2.2.dylib referenced from:
/opt/local/lib/libexslt.dylib (checking for undefined symbols may be
affected) (No such file or directory, errno = 2)
/usr/libexec/gcc/powerpc-apple-darwin8/4.0.1/ld: Undefined symbols:
_xmlTextReaderSchemaValidate
_xmlTextReaderSetup
collect2: ld returned 1 exit status
make: *** [libs/libphp5.bundle] Error 1

Error: Status 1 encountered during processing.
>>>
>>>It seems you do not have /opt/local/lib/libxml2.2.dylib
>>>I wonder why not.
>>>On my system, that is a symlink to libxml2.2.6.32.dylib and it's
>>>provided by the libxml2 port.
>>>What version of the libxml2 port do you have installed?
>>>Try "port installed libxml2"
>>
>>Yes, that's pretty much what I thought ... how has it gone? I
>>usually only do reboots on the PowerBook after Apple updates. But
>>on Saturday I shut it down and restarted it in the evening. On
>>restart I found Apache2 wouldn't run, which is a rather big blow.
>>
>>Welcome to Darwin!
>>modem-645:~ $ sudo port installed libxml2
>>The following ports are currently installed:
>>   libxml2 @2.6.31_0
>>   libxml2 @2.6.32_0
>>   libxml2 @2.6.32_1 (active)
>
>
>Try
>
>sudo port deactivate libxml2 @2.6.32_1
>sudo port activate libxml2 @2.6.32_1
>
>Does that bring back the /opt/local/lib/libxml2.2.dylib symlink?


modem-3637:~ $ sudo port deactivate libxml2 @2.6.32_1
--->  Deactivating libxml2 2.6.32_1

modem-3637:~ $ sudo port activate libxml2 @2.6.32_1
--->  Activating libxml2 2.6.32_1

modem-3637:~ $ cd /opt/local/lib/
modem-3637:/opt/local/lib $ ls -la
lrwxr-xr-x 1 root  admin9 Jul 25 22:33 libxml2 -> libxml2.2
-rwxr-xr-x 2 root  admin  1319504 Jul  4 01:53 libxml2.2
lrwxr-xr-x 1 root  admin9 Jul 25 22:33
libxml2.2.6.32 -> libxml2.2
-rwxr-xr-x 2 root  admin  835 Jul  4 01:53 libxml2.la


Doesn't seem to have (re-)added a link here. And trying to install
php5 still results in the same error.
>>>
>>>On my system I see:
>>>
>>>$ ls -l *xml*
>>>-rwxr-xr-x   2 rschmidt  admin  1179072 Jul  4 00:15 libxml2.2.6.32.dylib
>>>lrwxr-xr-x   1 rschmidt  admin   20 Jul  4 00:16 libxml2.2.dylib
>>>-> libxml2.2.6.32.dylib
>>>lrwxr-xr-x   1 rschmidt  admin   20 Jul  4 00:16 libxml2.dylib
>>>-> libxml2.2.6.32.dylib
>>>-rwxr-xr-x   2 rschmidt  admin  838 Jul  4 00:15 libxml2.la
>>>-rw-r--r--   2 rschmidt  admin  214 Jul  4 00:15 xml2Conf.sh
>>>
>>>So there are a number of curious differences.
>>>1. Why do your files not have the .dylib extension?
>>>2. Why are your symlinks pointing to libxml2.2 instead of to libxml2.2.6.32?
>>>3. Why are your libxml2.2 and libxml2.la untouched since July 4,
>>>implying they are not a part of the libxml2 port?
>>>
>>>I'd also like to know what version of Xcode you have. Go to
>>>/Developer/Applications and get info on Xcode. If the version is
>>>less than 2.4.1, please upgrade to 2.4.1 or 2.5.
>>>
>>>Then please do:
>>>
>>>sudo port -f uninstall libxml2 @2.6.32_1
>>>
>>>Then look in /opt/local/lib and see if libxml2.2 and libxml2.la
>>>remain. If so, delete them manually. In fact, after you uninstall
>>>libxml2, make sure all of the following are absent, and if they're
>>>present, delete them:
>>>
>>>/opt/local/bin/xml2-config
>>>/opt/local/bin/xmlcatalog
>>>/opt/local/bin/xmllint
>>>/opt/local/include/libxml2/*
>>>/opt/local/lib/libxml2*
>>>/opt/local/lib/pkgconfig/libxml-2.0.pc
>>>/opt/local/lib/xml2Conf.sh
>>>/opt/local/share/aclocal/libxml.m4
>>>/opt/local/share/doc/libxml2-2.6.32/*
>>>/opt