Problem installing readline
Thomas Schober
thomas.schober at gmail.com
Wed Aug 15 04:41:16 PDT 2007
I attached te file already in a mail before in this conversation. Here
it is again :
PortSystem 1.0
name readline-5
set shortname readline
version 5.0.005
distname ${shortname}-5.0
categories devel
maintainers nomaintainer at macports.org
platforms darwin
description Library that provides command line editing
long_description\
The GNU Readline library provides a set of functions \
for use by applications that allow users to edit \
command lines as they are typed in. Both Emacs and vi \
editing modes are available. The Readline library \
includes additional functions to maintain a list of \
previously-entered command lines, to recall and perhaps \
reedit those lines, and perform csh-like history \
expansion on previous commands. \
\
This version provides limited functionality. It is \
intended to be used by ports that require version \
5.0. Only the dynamic library is installed, and the \
include files are kept in PREFIX/include/readline5.
homepage http://cnswww.cns.cwru.edu/~chet/readline/rltop.html
master_sites gnu:${shortname} \
ftp://ftp.cwru.edu/pub/bash/:${shortname}
patch_sites ftp://ftp.cwru.edu/pub/bash/readline-5.0-patches/
patchfiles readline50-001 \
readline50-002 \
readline50-003 \
readline50-004 \
readline50-005
platform darwin 8 { patchfiles-append patch-shobj-conf }
checksums ${distname}${extract.suffix} md5
9a39d15f1ed592883f8c6671e8c13120 \
readline50-001 md5 5b47ed61b6b8413746750127c70e843d \
readline50-002 md5 9f803005e7e4c7d675146a9a805acbf1 \
readline50-003 md5 05d59c91f80fa99ab177783229b0f769 \
readline50-004 md5 aa1f6343e47f8e024488c63281d77809 \
readline50-005 md5 1dc2654e0161f2e7b4f536b12e1d54b7
configure.args --mandir=${prefix}/share/man \
--infodir=${prefix}/share/info
post-destroot { file delete -force ${destroot}${prefix}/share
file delete ${destroot}${prefix}/lib/libhistory.a
file delete ${destroot}${prefix}/lib/libhistory.dylib
file delete ${destroot}${prefix}/lib/libhistory.5.dylib
file delete ${destroot}${prefix}/lib/libreadline.a
file delete ${destroot}${prefix}/lib/libreadline.dylib
file delete ${destroot}${prefix}/lib/libreadline.5.dylib
file rename ${destroot}${prefix}/include/readline
${destroot}${prefix}/include/readline5
}
2007/8/15, Ryan Schmidt <ryandesign at macports.org>:
> On Aug 15, 2007, at 04:14, Thomas Schober wrote:
>
> > 2007/8/15, Ryan Schmidt:
> >
> >> On Aug 14, 2007, at 10:59, Thomas Schober wrote:
> >>
> >>> 2007/8/14, Thomas Schober:
> >>>
> >>>> 2007/8/14, Ryan Schmidt:
> >>>>
> >>>>> On Aug 14, 2007, at 02:57, Thomas Schober wrote:
> >>>>>
> >>>>>> No i am trying to install subversion and readline is a dependency
> >>>>>> of it. I don't know if i need 5.2, the only thig i did is :
> >>>>>>
> >>>>>> sudo port install readline
> >>>>>>
> >>>>>> I don't really care which version of readline i get. But thats
> >>>>>> all
> >>>>>> automatic by MacPorts.
> >>>>>
> >>>>> Ah yes, subversion depends on apr-util, which depends on sqlite3,
> >>>>> which depends on readline. It does not depend on readline-5, and
> >>>>> readline-5 would not satisfy the readline dependency. So we're
> >>>>> back
> >>>>> to my previous suggestions regarding potential changes to the
> >>>>> readline port you could try:
> >>>>>
> >>>>> http://lists.macosforge.org/pipermail/macports-users/2007-August/
> >>>>> 005009.html
> >>>>
> >>>> The Problem is, that this line :
> >>>>
> >>>> delete ${destroot}${prefix}/share/info/dir
> >>>>
> >>>> is not in the portfile. there is a generall line inside, which
> >>>> goes over all
> >>>> /share/info/*.
> >>>>
> >>>> I tried to delete this line, but the same problem as before.
> >>
> >> Either you are looking at the wrong portfile, or your portfiles are
> >> months out of date. The relevant line has been that way since
> >> February 2007, as per this changeset:
> >>
> >> http://trac.macosforge.org/projects/macports/changeset/22017
> >>
> >> This is the file we're talking about:
> >>
> >> http://trac.macosforge.org/projects/macports/browser/trunk/dports/
> >> devel/readline/Portfile?rev=26187
> >>
> >> It is located at the path devel/readline/Portfile within your ports
> >> tree.
> >>
> >> Line 41.
> >>
> >> What is the first line of your readline portfile -- what is the
> >> output of this command?
> >>
> >> port file readline | xargs head -n 1
> >>
> >> On my system, it is as follows:
> >>
> >> # $Id: Portfile 26187 2007-06-15 10:36:51Z ryandesign at macports.org $
> >>
> >> And this is what you should see, too, if your ports tree is up to
> >> date.
> >>
> >>
> >>> ok, i fixed the problem:
> >>>
> >>> i just created
> >>>
> >>> /opt/local/var/macports/build/
> >>> _opt_local_var_macports_sources_rsync.macports.org_release_ports_dev
> >>> el
> >>> _readline/work/destroot/opt/local/share/info/dir
> >>>
> >>> this directory was missing
> >>
> >> It sounds like you worked around the problem, rather than fixing it.
> >> You may have succeeded in installing the port today, but if you ever
> >> need to reinstall it, I see no reason why the same problem would not
> >> occur again. It would be beneficial to discover why the problem
> >> occurred in the first place. Maybe a change needs to be made to the
> >> portfile. We won't know until someone who's experiencing the problem
> >> (you) tries out the changes suggested above to see if they help or
> >> not.
> >>
> >> Another possibility would be to explicitly write the code so that the
> >> file is only deleted if it exists, similar to this:
> >>
> >> http://trac.macosforge.org/projects/macports/changeset/27782
> >
> > I already tried this solution, but the line :
> >
> >>> delete ${destroot}${prefix}/share/info/dir
> >
> > is not in the portfile.
>
> Then you are not looking at the same portfile I'm looking at, because
> that line is present in the readline portfile I have. I copied the
> line directly from there.
>
> > There is a loop, which deletes a bunch of
> > files and directories. They seem to be created dynamically. So when i
> > remove the line, nothing is deleted anymore.
> > It seems that you have to insert a delete command, which ignores
> > errors.
>
> Perhaps you could attach the complete file you're looking at. Maybe
> that would help us converge on a solution.
>
>
More information about the macports-users
mailing list