trouble installing readline

Create issue
Issue #1938 closed
anonymous created an issue

I have been only able to configure and install part of readline. I get message back need to run ldconfig. I could only find an ld program with -help it is a shared library control program. I do not understand how to use it to get Cactus running. Thanks

David Rosenberg drdnrosenberg@gmail.com.

Keyword:

Comments (8)

  1. Frank Löffler

    Hi David

    Thank you for your bug report. I am not quite sure what is wrong here, and would need more information. A message about needing to run ldconfig is quite normal at the end of the installation of a library. It only means that usually (not here) you need to run 'ldconfig' to make the new library 'known to the system'. This is not the case here. Cactus specifies all paths to libraries 'by hand'. ldconfig is likely not your problem.

    Could you please, within the 'Cactus' directory, run 'VERBOSE=yes sim build', capture the output and attach it to this ticket? This should help is a lot more to find the cause of the problem. You should be able to do that with one command:

    VERBOSE=yes sim build 2>&1 | tee build.log

    This will create a file 'build.log' which is what we would like to see. You still get the output to your screen (and it will be more than usual, don't be alarmed).

    Also: you tagged the ticket with ET_2015_05. Did you mean ET_2016_05 (the latest release), or really the release from about a year ago?

  2. Frank Löffler
    • removed comment

    Replying to [comment:2 sbrandt]:

    I'm confused. Why is readline needed for Cactus? I don't compile it.

    ExternalLibraries/libreadline is not in the Einstein Toolkit. It is needed by ExternalLibraries/Lua. If not brought in by that, I could only imagine some other library depending on it without us explicitly requiring it. A full build log should show all that.

  3. Steven R. Brandt
    • removed comment

    Ah, now I understand. Lua does not actually need readline however. It can be compiled without it.

  4. Frank Löffler
    • removed version
    • marked as
    • removed milestone
    • removed comment

    Removing milestone, since not part of the ET.

  5. Roland Haas
    • changed status to resolved
    • removed comment

    no more input was provided and since the thorn is not part of the ET there is nothing to do.

  6. Log in to comment