error during installation of macport
hi :-) i have a script to install macport which makes : rsync -azv rsync://rsync.macports.org/release/base/ my-directory cd my-directory ./configure --prefix=my-directory --with-install-user=`id -un` --with- install-group=`id -gn` make it ends with : cc -dynamiclib -L/usr/local/lib Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o fs-traverse.o strcasecmp.o vercomp.o filemap.o sha1cmd.o compat.o curl.o rmd160cmd.o readline.o uid.o tracelib.o -o Pextlib.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/8.4 -ltclstub8.4 -L/usr/local/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lcurl -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lz -lcrypto ld: Undefined symbols: _add_history _completion_matches _filename_completion_function _read_history _readline _rl_attempted_completion_function _rl_line_buffer _rl_readline_name _stifle_history _unstifle_history _username_completion_function _using_history _write_history /usr/bin/libtool: internal link edit command failed make[2]: *** [Pextlib.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 what's wrong ? -- j'agis contre l'assistanat, je travaille dans une SCOP !
Le 10 mars 08 à 01:08, Thomas De Contes a écrit :
hi :-)
i have a script to install macport which makes :
rsync -azv rsync://rsync.macports.org/release/base/ my-directory cd my-directory ./configure --prefix=my-directory --with-install-user=`id -un` --with- install-group=`id -gn` make
it ends with :
cc -dynamiclib -L/usr/local/lib Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o fs-traverse.o strcasecmp.o vercomp.o filemap.o sha1cmd.o compat.o curl.o rmd160cmd.o readline.o uid.o tracelib.o -o Pextlib.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/8.4 -ltclstub8.4 -L/usr/local/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lcurl -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lz -lcrypto ld: Undefined symbols: _add_history _completion_matches _filename_completion_function _read_history _readline _rl_attempted_completion_function _rl_line_buffer _rl_readline_name _stifle_history _unstifle_history _username_completion_function _using_history _write_history /usr/bin/libtool: internal link edit command failed make[2]: *** [Pextlib.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
sorry, i forgot to give some infos : PPC mac os x 10.4.11 what do you need else ?
what's wrong ?
-- j'agis contre l'assistanat, je travaille dans une SCOP !
On Sun, Mar 9, 2008 at 8:08 PM, Thomas De Contes <d.l.tDeContes@free.fr> wrote:
cc -dynamiclib -L/usr/local/lib Pextlib.o strsed.o fgetln.o md5cmd.o setmode.o xinstall.o fs-traverse.o strcasecmp.o vercomp.o filemap.o sha1cmd.o compat.o curl.o rmd160cmd.o readline.o uid.o tracelib.o -o Pextlib.dylib -L/System/Library/Frameworks/Tcl.framework/Versions/8.4 -ltclstub8.4 -L/usr/local/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lcurl -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -L/Users/thomas/Documents/prgm/bin/ autoinstall/macports/lib -lz -lcrypto ld: Undefined symbols: _add_history _completion_matches _filename_completion_function _read_history _readline _rl_attempted_completion_function _rl_line_buffer _rl_readline_name _stifle_history _unstifle_history _username_completion_function _using_history _write_history /usr/bin/libtool: internal link edit command failed make[2]: *** [Pextlib.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1
what's wrong ?
Looks like a readline issue, do you happen to have a local readline installed in /usr/local or somewhere else? Try adding --enable-readline to the configure call. Cheers Adam
Le 10 mars 08 à 01:17, Adam Mercer a écrit :
Looks like a readline issue, do you happen to have a local readline installed in /usr/local or somewhere else?
you're right :-) $ locate readline /usr/include/readline /usr/include/readline/history.h /usr/include/readline/readline.h /usr/lib/libreadline.dylib
Try adding --enable-readline to the configure call.
thank you, it works :-) but, it's not noticed in http://www.macports.org/install.php#source what could install readline ? a mac os x update ? approximately 6 months ago, i installed macports on the same computer without problem will i need "--enable-readline" for any computer, or only for a few cases ? -- j'agis contre l'assistanat, je travaille dans une SCOP !
On Mar 11, 2008, at 22:14, Thomas De Contes wrote:
Le 10 mars 08 à 01:17, Adam Mercer a écrit :
Looks like a readline issue, do you happen to have a local readline installed in /usr/local or somewhere else?
you're right :-)
$ locate readline /usr/include/readline /usr/include/readline/history.h /usr/include/readline/readline.h /usr/lib/libreadline.dylib
Those are a normal part of the OS and should be fine. Adam was talking about different and possibly old or incompatible versions of readline that some people end up with in /usr/local.
Try adding --enable-readline to the configure call.
thank you, it works :-)
Strange.
but, it's not noticed in http://www.macports.org/install.php#source
But it says: To customize your installation you should read the output of "./configure --help | more"
what could install readline ? a mac os x update ?
approximately 6 months ago, i installed macports on the same computer without problem
will i need "--enable-readline" for any computer, or only for a few cases ?
6 months ago, there was no --enable-readline switch in MacPorts, and it always enabled readline. The default was changed to not enable readline support, and only do it at a user's request. See r31139, r31140, r31161. Ironically, this was supposed to *eliminate* readline- related problems, not cause them. So something must've gone wrong. Without --enable-readline, MacPorts should not be looking for any kind of readline files.
Le 12 mars 08 à 22:07, Ryan Schmidt a écrit :
On Mar 11, 2008, at 22:14, Thomas De Contes wrote:
Le 10 mars 08 à 01:17, Adam Mercer a écrit :
Looks like a readline issue, do you happen to have a local readline installed in /usr/local or somewhere else?
you're right :-)
$ locate readline /usr/include/readline /usr/include/readline/history.h /usr/include/readline/readline.h /usr/lib/libreadline.dylib
Those are a normal part of the OS and should be fine. Adam was talking about different and possibly old or incompatible versions of readline that some people end up with in /usr/local.
no, nothing in /usr/local, but, i just think, i had readline already installed by macports, can it be the cause ? here is my script : http://dl.free.fr/gKF9RMNwH/installer-macports i tried to make a script which is able both to install or to update macports, without the need for the user to tell what to do i think i succeeded, except that it is economist neither in time nor in disk space
Try adding --enable-readline to the configure call.
thank you, it works :-)
Strange.
but, it's not noticed in http://www.macports.org/install.php#source
But it says: To customize your installation you should read the output of "./configure --help | more"
i use --prefix, --with-install-user and --with-install-group, but i think i needn't anything else moreover, 6 months ago it worked fine do you thing i may need someting without knowing that ? (i'm searching wheather i could find all of that myself)
what could install readline ? a mac os x update ?
approximately 6 months ago, i installed macports on the same computer without problem
will i need "--enable-readline" for any computer, or only for a few cases ?
6 months ago, there was no --enable-readline switch in MacPorts, and it always enabled readline. The default was changed to not enable readline support, and only do it at a user's request. See r31139, r31140, r31161. Ironically, this was supposed to *eliminate* readline-related problems, not cause them. So something must've gone wrong. Without --enable-readline, MacPorts should not be looking for any kind of readline files.
curious, in the ./configure phase i got : checking readline/readline.h usability... yes checking readline/readline.h presence... yes checking for readline/readline.h... yes checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes i have a computer to test MacPorts before put it on my working computer, so if you need ... -- j'agis contre l'assistanat, je travaille dans une SCOP !
participants (3)
-
Adam Mercer
-
Ryan Schmidt
-
Thomas De Contes