Re: MacPorts 1.4 rc2
prunille:~ locate libreadline.dylib /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libreadline.dylib /opt/local/lib/libreadline.dylib /opt/local/var/db/dports/build/ _Users_vinc17_software_darwinports_dports_devel_readline/work/ destroot/opt/local/lib/libreadline.dylib /opt/local/var/db/dports/software/readline/5.1.004_0/opt/local/lib/ libreadline.dylib /usr/lib/libreadline.dylib But only /opt/local/lib/libreadline.dylib and /usr/lib/ libreadline.dylib should be available. configure (normally?) doesn't look into /opt/local. And the linker didn't use /opt/local/lib, to quote your log excerpt: cc -dynamiclib -L/usr/local/lib -L/usr/lib -lcurl -lssl -lcrypto - lz Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o find.o strcasecmp.o vercomp.o filemap.o sha1cmd.o compat.o curl.o rmd160cmd.o readline.o uid.o -o Pextlib.dylib -L/System/Library/ Frameworks/Tcl.framework/Versions/8.4 -ltclstub8.4 -L/usr/local/ lib -L/usr/lib -lcurl -lssl -lcrypto -lz -lreadline -lcrypto What does locate readline.h print out? Paul ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
Vincent, Basically, you are confusing the behavior of the configure script with C_INCLUDE_PATH and LIBRARY_PATH environment variables. There is not much we can do except unset those variables in the configuration script to prevent this. For your information, the bug I was mentioning is quite different. It happens when there is an installation of readline in /usr/local with headers and no library or with headers and a static library. The reason is that gcc looks into /usr/local/include as part of the system includes (and before /usr/include), while ld does not look into /usr/local/lib and even when told to do so, the -L arguments do not form a simple priority chain as static libraries and dynamic libraries are handled differently. In other words, gcc will take the headers of the newer version of readline in /usr/local while ld will take the library from the system installation of readline. Paul Le 15 mars 07 à 22:37, Vincent Lefevre a écrit : On 2007-03-15 19:03:37 +0900, Paul Guyot wrote: prunille:~ locate libreadline.dylib /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libreadline.dylib /opt/local/lib/libreadline.dylib /opt/local/var/db/dports/build/ _Users_vinc17_software_darwinports_dports_devel_readline/work/ destroot/opt/local/lib/libreadline.dylib /opt/local/var/db/dports/software/readline/5.1.004_0/opt/local/ lib/libreadline.dylib /usr/lib/libreadline.dylib But only /opt/local/lib/libreadline.dylib and /usr/lib/ libreadline.dylib should be available. configure (normally?) doesn't look into /opt/local. It completely depends on the environment variables. To benefit from MacPorts, I have: C_INCLUDE_PATH=/Users/vinc17/include:/opt/local/include LIBRARY_PATH=/Users/vinc17/lib:/opt/local/lib [...] ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
My understanding was that configure generally added directories based on --prefix for include and lib paths, though a recent program I compiled only used it for lib and ignored it for include. On Mar 15, 2007, at 6:03 AM, Paul Guyot wrote: configure (normally?) doesn't look into /opt/local. -- Kevin Ballard http://kevin.sb.org [EMAIL PROTECTED] http://www.tildesoft.com ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
Juan Manuel Palacios wrote: Hello everyone! I just tagged 1.4.0-rc2 and posted corresponding test tarballs and checksums to our downloads directory. Those of you keeping track of svn commits should know about the changes that took place since rc1, those of you that don't please be patient, I'll update the ChangeLog as I get a chance through out the day. In any case, there have been changes to the release_1_4 branch so getting some testing on rc2 would be good! Just the same, if anything comes up please file a ticket in trac and assign it to the MacPorts 1.4 milestone, base component (forwarding the ticket number to this list, thanks!). I'm trying to build 1.4 rc 2 for testing purposes with PortAuthority, and it's not building because it requires a threaded build of Tcl. Is there any way to patch the configure file so that it links against the Tcl in /System/Library directory? How do others handle this? -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
Kevin Walzer wrote: Juan Manuel Palacios wrote: Hello everyone! I just tagged 1.4.0-rc2 and posted corresponding test tarballs and checksums to our downloads directory. Those of you keeping track of svn commits should know about the changes that took place since rc1, those of you that don't please be patient, I'll update the ChangeLog as I get a chance through out the day. In any case, there have been changes to the release_1_4 branch so getting some testing on rc2 would be good! Just the same, if anything comes up please file a ticket in trac and assign it to the MacPorts 1.4 milestone, base component (forwarding the ticket number to this list, thanks!). I'm trying to build 1.4 rc 2 for testing purposes with PortAuthority, and it's not building because it requires a threaded build of Tcl. Is there any way to patch the configure file so that it links against the Tcl in /System/Library directory? How do others handle this? Whoops, please disregard. I just noticed that configure was picking up a non-threaded build of Tcl from my Fink install. I moved /sw out of my path and things are building fine. -- Kevin Walzer Code by Kevin http://www.codebykevin.com ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
On Mar 14, 2007, at 6:00 PM, Kevin Ballard wrote: On Mar 14, 2007, at 5:11 PM, Ryan Schmidt wrote: I didn't try 1.4rc1... How do I try 1.4rc2? If I have a working copy of the release_1_4 branch, do I just configure, make, sudo make install? Yes. You can also either check out from the tags dir in our repo, http://svn.macports.org/repository/macports/tags/release_1_4_0-rc2, or download the equivalent tarball snapshots (.gz or .bz2, which ever you prefer) from the downloads directory, http://svn.macports.org/repository/macports/downloads/MacPorts-1.4 ---snip--- The only real caveat I can think of is if the official 1.4 release is different than 1.4rc2, a `port selfupdate` won't pick it up, since it will think both versions are 1.400. This is certainly an issue for anyone installing from the 1.4 release branch (or its snapshots), as the version number there is already 1.4. When released, selfupdate wont notice any difference, but then again we can presume people installing from svn are savvy enough to know either about forcing the upgrade or how to install from source ;-) Regards,... -jmpp ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Re: MacPorts 1.4 rc2
On 2007-03-15 12:05:03 +0900, Paul Guyot wrote: Please uninstall your other copy of readline and try again. I don't want to do that as ports depend on it: It's not what I meant. You probably have three copies of readline: - System's readline - MP's readline - Another copy. This is the other copy that makes MacPorts choke, because of diverging priorities in /usr/ /usr/local between compilation (/usr/ include, /usr/local/include) and linking (/usr/lib, /usr/local/lib). I'll bet the configure script thinks your system has both old-style readline functions and new-style readline functions. Paul ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
