problem building gnupod
I'm not sure what the problem is here, expat is installed (subversion, at least, is using it) but p5-xml-parser won't go in because it cannot find it. I've tried exporting EXPATLIBPATH and EXPATINCPATH but still no cookie. (I have synced and cleaned installed too.) What could be wrong? // George geo@fuji:/Users/geo port installed expat The following ports are currently installed: expat @2.0.0_1 expat @2.0.1_0 (active) geo@fuji:/Users/geo sudo port outdated The following installed ports are outdated: gmp 4.2.2_0 < 4.2.2_1 libpcap 0.9.5_1 < 0.9.8_0 R 2.5.1_0 < 2.6.1_0 tcl 8.4.16_0 < 8.5.0_0 urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 vim 7.1.175_0 < 7.1.203_0 xrender 0.9.0_1 < 0.9.0_2 geo@fuji:/Users/geo sudo port install gnupod Password: ---> Configuring p5-xml-parser Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: Note (probably harmless): No library found for -lexpat Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories. You can download expat from: http://sourceforge.net/projects/expat/ If expat is installed, but in a non-standard directory, then use the following options to Makefile.PL: EXPATLIBPATH=... To set the directory in which to find libexpat EXPATINCPATH=... To set the directory in which to find expat.h For example: perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include Note that if you build against a shareable library in a non-standard location you may (on some platforms) also have to set your LD_LIBRARY_PATH environment variable at run time for perl to find the library. Error: The following dependencies failed to build: p5-xml-parser Error: Status 1 encountered during processing. -- George Georgalis, information system scientist <IXOYE><
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found. On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote:
I'm not sure what the problem is here, expat is installed (subversion, at least, is using it) but p5-xml-parser won't go in because it cannot find it. I've tried exporting EXPATLIBPATH and EXPATINCPATH but still no cookie. (I have synced and cleaned installed too.) What could be wrong?
// George
geo@fuji:/Users/geo port installed expat The following ports are currently installed: expat @2.0.0_1 expat @2.0.1_0 (active) geo@fuji:/Users/geo sudo port outdated The following installed ports are outdated: gmp 4.2.2_0 < 4.2.2_1 libpcap 0.9.5_1 < 0.9.8_0 R 2.5.1_0 < 2.6.1_0 tcl 8.4.16_0 < 8.5.0_0 urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 vim 7.1.175_0 < 7.1.203_0 xrender 0.9.0_1 < 0.9.0_2 geo@fuji:/Users/geo sudo port install gnupod Password: ---> Configuring p5-xml-parser Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: Note (probably harmless): No library found for -lexpat
Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories. You can download expat from:
http://sourceforge.net/projects/expat/
If expat is installed, but in a non-standard directory, then use the following options to Makefile.PL:
EXPATLIBPATH=... To set the directory in which to find libexpat
EXPATINCPATH=... To set the directory in which to find expat.h
For example:
perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include
Note that if you build against a shareable library in a non-standard location you may (on some platforms) also have to set your LD_LIBRARY_PATH environment variable at run time for perl to find the library.
Error: The following dependencies failed to build: p5-xml-parser Error: Status 1 encountered during processing.
-- George Georgalis, information system scientist <IXOYE><
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary. I have p5-xml-parser and expat installed. Never seen this problem. The obvious difference I see is that your MacPorts prefix is /usr/ local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake? Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture?
On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote:
I'm not sure what the problem is here, expat is installed (subversion, at least, is using it) but p5-xml-parser won't go in because it cannot find it. I've tried exporting EXPATLIBPATH and EXPATINCPATH but still no cookie. (I have synced and cleaned installed too.) What could be wrong?
// George
geo@fuji:/Users/geo port installed expat The following ports are currently installed: expat @2.0.0_1 expat @2.0.1_0 (active) geo@fuji:/Users/geo sudo port outdated The following installed ports are outdated: gmp 4.2.2_0 < 4.2.2_1 libpcap 0.9.5_1 < 0.9.8_0 R 2.5.1_0 < 2.6.1_0 tcl 8.4.16_0 < 8.5.0_0 urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 vim 7.1.175_0 < 7.1.203_0 xrender 0.9.0_1 < 0.9.0_2 geo@fuji:/Users/geo sudo port install gnupod Password: ---> Configuring p5-xml-parser Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/ _usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_p orts_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/ MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: Note (probably harmless): No library found for - lexpat
Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories. You can download expat from:
http://sourceforge.net/projects/expat/
If expat is installed, but in a non-standard directory, then use the following options to Makefile.PL:
EXPATLIBPATH=... To set the directory in which to find libexpat
EXPATINCPATH=... To set the directory in which to find expat.h
For example:
perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/ me/include
Note that if you build against a shareable library in a non- standard location you may (on some platforms) also have to set your LD_LIBRARY_PATH environment variable at run time for perl to find the library.
Error: The following dependencies failed to build: p5-xml-parser Error: Status 1 encountered during processing.
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
ls: /opt/local: No such file or directory
Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture?
not sure how to determine xcode version maybe this is good enough? + port version Version: 1.600 + system_profiler + grep 'System Version' System Version: Mac OS X 10.4.11 (8S165) + which gcc /usr/bin/gcc + gcc -v Using built-in specs. Target: powerpc-apple-darwin8 Configured with: /private/var/tmp/gcc/gcc-5363.obj~28/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++ --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib --build=powerpc-apple-darwin8 --host=powerpc-apple-darwin8 --target=powerpc-apple-darwin8 Thread model: posix gcc version 4.0.1 (Apple Computer, Inc. build 5363) + ls /Developer/SDKs MacOSX10.3.9.sdk MacOSX10.4u.sdk + uname -p powerpc // George
On Sun, Jan 06, 2008 at 06:30:00PM -0500, George Georgalis wrote:
I'm not sure what the problem is here, expat is installed (subversion, at least, is using it) but p5-xml-parser won't go in because it cannot find it. I've tried exporting EXPATLIBPATH and EXPATINCPATH but still no cookie. (I have synced and cleaned installed too.) What could be wrong?
// George
geo@fuji:/Users/geo port installed expat The following ports are currently installed: expat @2.0.0_1 expat @2.0.1_0 (active) geo@fuji:/Users/geo sudo port outdated The following installed ports are outdated: gmp 4.2.2_0 < 4.2.2_1 libpcap 0.9.5_1 < 0.9.8_0 R 2.5.1_0 < 2.6.1_0 tcl 8.4.16_0 < 8.5.0_0 urw-fonts 1.0.7pre43_0 < 1.0.7pre44_0 vim 7.1.175_0 < 7.1.203_0 xrender 0.9.0_1 < 0.9.0_2 geo@fuji:/Users/geo sudo port install gnupod Password: ---> Configuring p5-xml-parser Error: Target org.macports.configure returned: configure failure: shell command " cd "/usr/local/MacPorts/var/macports/build/_usr_local_MacPorts_var_macports_sources_rsync.macports.org_release_ports_perl_p5-xml-parser/work/XML-Parser-2.36" && /usr/local/MacPorts/bin/perl Makefile.PL INSTALLDIRS=vendor " returned error 2 Command output: Note (probably harmless): No library found for -lexpat
Expat must be installed prior to building XML::Parser and I can't find it in the standard library directories. You can download expat from:
http://sourceforge.net/projects/expat/
If expat is installed, but in a non-standard directory, then use the following options to Makefile.PL:
EXPATLIBPATH=... To set the directory in which to find libexpat
EXPATINCPATH=... To set the directory in which to find expat.h
For example:
perl Makefile.PL EXPATLIBPATH=/home/me/lib EXPATINCPATH=/home/me/include
Note that if you build against a shareable library in a non-standard location you may (on some platforms) also have to set your LD_LIBRARY_PATH environment variable at run time for perl to find the library.
Error: The following dependencies failed to build: p5-xml-parser Error: Status 1 encountered during processing.
-- George Georgalis, information system scientist <IXOYE><
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
ls: /opt/local: No such file or directory
Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture?
not sure how to determine xcode version maybe this is good enough?
Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode.
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
ls: /opt/local: No such file or directory
Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture?
not sure how to determine xcode version maybe this is good enough?
Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode.
okay, Xcode version 2.3 from Aug 11 2006. I guess that's not part of 'Software Update' ...I have no reservations about updating it if that may be the issue. // George -- George Georgalis, information system scientist <IXOYE><
On Jan 7, 2008, at 22:30, George Georgalis wrote:
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 20:10, George Georgalis wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
ls: /opt/local: No such file or directory
Also, can you tell us your version of MacPorts, Mac OS X, Xcode, and your processor architecture?
not sure how to determine xcode version maybe this is good enough?
Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode.
okay, Xcode version 2.3 from Aug 11 2006.
I guess that's not part of 'Software Update'
...I have no reservations about updating it if that may be the issue.
Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, but 2.3 may be too old. It's a big download but I recommend it. http://developer.apple.com/tools/download/
On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 22:30, George Georgalis wrote:
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode.
okay, Xcode version 2.3 from Aug 11 2006.
I guess that's not part of 'Software Update'
...I have no reservations about updating it if that may be the issue.
Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, but 2.3 may be too old. It's a big download but I recommend it.
Okay, downloading, will try tonight. To reduce consumed disk space after it's all in place, should I think about purging /Developer before I start the install? is that even necessary? Is there something else that is better to do? // George -- George Georgalis, information system scientist <IXOYE><
On Jan 8, 2008, at 11:05, George Georgalis wrote:
On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 22:30, George Georgalis wrote:
On Mon, Jan 07, 2008 at 09:46:26PM -0600, Ryan Schmidt wrote:
Get Info on /Developer/Applications/Xcode.app in the Finder to find the installed version of Xcode.
okay, Xcode version 2.3 from Aug 11 2006.
I guess that's not part of 'Software Update'
...I have no reservations about updating it if that may be the issue.
Xcode 2.4.1 ought to work fine, as should the latest which is 2.5, but 2.3 may be too old. It's a big download but I recommend it.
Okay, downloading, will try tonight. To reduce consumed disk space after it's all in place, should I think about purging /Developer before I start the install? is that even necessary? Is there something else that is better to do?
I assume that installing Xcode 2.5 will be smart about removing obsolete parts of Xcode 2.3 first. If you're concerned that it won't be, you could first run the Xcode 2.3 uninstall script. (Xcode installs things in more places than just /Developer.) The uninstall script is probably on the Xcode 2.3 CD or disk image.
Well I get the same missing expat problem, with Xcode 2.5 I'm tempted to make a symlink to /usr/local/MacPorts from /opt/local but I'd really like to get this figured out vs just make it work. below are notes on my Xcode update. What else can I try? // George On Tue, Jan 08, 2008 at 03:03:24PM -0600, Ryan Schmidt wrote:
On Jan 8, 2008, at 11:05, George Georgalis wrote:
On Mon, Jan 07, 2008 at 11:44:59PM -0600, Ryan Schmidt wrote:
Okay, downloading, will try tonight. To reduce consumed disk space after it's all in place, should I think about purging /Developer before I start the install? is that even necessary? Is there something else that is better to do?
I assume that installing Xcode 2.5 will be smart about removing obsolete parts of Xcode 2.3 first. If you're concerned that it won't be, you could first run the Xcode 2.3 uninstall script. (Xcode installs things in more places than just /Developer.) The uninstall script is probably on the Xcode 2.3 CD or disk image.
here's some summary notes I don't have the dmg from my current Xcode install. Version 2.5 says this in the About pdf... Uninstalling Xcode 2.5 developer tools Since multiple versions of the Xcode developer tools can coexist on your system on Mac OS X 10.5, the uninstall-devtools.pl script has been changed to only remove content installed into the Xcode directory. On Mac OS X 10.4.x, the uninstall-devtools script continues to remove all Xcode 2.5 developer tools content from the boot volume. On Mac OS X 10.4.x, type the following in Terminal to remove the Xcode 2.5 developer tools: $ sudo /Developer/Library/uninstall-devtools On Mac OS X 10.5, type the following in Terminal to remove the Xcode 2.5 developer tools: $ sudo <Xcode 2.5 directory>/Library/uninstall-devtools NOTE: The uninstaller that ships with previous versions of Xcode developer tools will not clean everything off of your system properly. You should either use the one on the Xcode 2.5 DVD, or you should use the one installed when you installed the Xcode 2.5 developer tools. NOTE: Running the uninstall script will uninstall any previous installations of Mac OS X Developer Tools or Xcode developer tools releases on Tiger systems. On Leopard systems, the uninstaller will only remove the Xcode developer tools installed on the boot volume outside of the Xcode directory. To remove the remaining Xcode content, drag the Xcode directory to the trash. I used that to discover: geo@fuji:/Users/geo find /Developer/ -iname \*uninstall\* /Developer//ADC Reference Library/documentation/QuickTime/APIREF/qtuninstallnexttaskneededsoonercallback.htm /Developer//Tools/uninstall-devtools.pl and ran it after the df command... geo@fuji:/Users/geo df -h Filesystem Size Used Avail Capacity Mounted on /dev/disk0s3 74G 73G 938M 99% / it freed up a lot of space, /dev/disk0s3 74G 71G 3.6G 95% / and the 2.5 install used a bit more: /dev/disk0s3 74G 74G 626M 99% / -- George Georgalis, information system scientist <IXOYE><
On Jan 9, 2008, at 00:12, George Georgalis wrote:
Well I get the same missing expat problem, with Xcode 2.5 I'm tempted to make a symlink to /usr/local/MacPorts from /opt/local but I'd really like to get this figured out vs just make it work.
I don't know why it happens yet, but I have been able to reproduce your problem so I filed a ticket. http://trac.macosforge.org/projects/macports/ticket/13885
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/ local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
Also note that /usr/local is not a good prefix to use for MacPorts. Some ports have specific instructions to ignore /usr/local as they (would otherwise) automatically search /usr/local and pick up items that users had manually (or otherwise outside of MacPorts) installed, which can result in confusion and later breakage. -eric
On Jan 9, 2008, at 17:49, Eric Hall wrote:
On Mon, Jan 07, 2008 at 02:23:05PM -0600, Ryan Schmidt wrote:
On Jan 7, 2008, at 08:49, George Georgalis wrote:
I have also tried exporting DYLD_LIBRARY_PATH, expat is not found.
That should not be necessary.
I have p5-xml-parser and expat installed. Never seen this problem.
The obvious difference I see is that your MacPorts prefix is /usr/ local/MacPorts instead of the usual /opt/local. Can you check if anything ended up getting installed in the /opt/local by mistake?
Also note that /usr/local is not a good prefix to use for MacPorts. Some ports have specific instructions to ignore /usr/local as they (would otherwise) automatically search /usr/local and pick up items that users had manually (or otherwise outside of MacPorts) installed, which can result in confusion and later breakage.
True, /usr/local is a bad prefix to use for MacPorts. However, George is not using /usr/local as his MacPorts prefix. He's using /usr/local/ MacPorts. And there should be no problem with that.
On Wed, Jan 09, 2008 at 05:07:12PM -0600, Ryan Schmidt wrote:
On Jan 9, 2008, at 00:12, George Georgalis wrote:
Well I get the same missing expat problem, with Xcode 2.5 I'm tempted to make a symlink to /usr/local/MacPorts from /opt/local but I'd really like to get this figured out vs just make it work.
I don't know why it happens yet, but I have been able to reproduce your problem so I filed a ticket.
resolution confirmed, your patch in macports works as expected, thanks! // George -- George Georgalis, information system scientist <IXOYE><
On Jan 12, 2008, at 18:55, George Georgalis wrote:
On Wed, Jan 09, 2008 at 05:07:12PM -0600, Ryan Schmidt wrote:
On Jan 9, 2008, at 00:12, George Georgalis wrote:
Well I get the same missing expat problem, with Xcode 2.5 I'm tempted to make a symlink to /usr/local/MacPorts from /opt/local but I'd really like to get this figured out vs just make it work.
I don't know why it happens yet, but I have been able to reproduce your problem so I filed a ticket.
resolution confirmed, your patch in macports works as expected, thanks!
Great! Thanks for reporting the problem and working through it with us until it was resolved.
participants (3)
-
Eric Hall
-
George Georgalis
-
Ryan Schmidt