Skip to content

Problem linking to readline lib on x86(64) Solaris #44680

Closed

Description

@abalkin
BPO 1676121
Nosy @loewis, @jcea, @abalkin, @devdanzin
Superseder
  • bpo-1204: readline configuration for shared libs w/o curses dependencies
  • Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

    Show more details

    GitHub fields:

    assignee = None
    closed_at = <Date 2009-05-12.17:07:48.307>
    created_at = <Date 2007-03-07.22:07:56.000>
    labels = ['type-bug', 'build']
    title = 'Problem linking to readline lib on x86(64) Solaris'
    updated_at = <Date 2011-03-17.12:52:32.827>
    user = 'https://github.com/abalkin'

    bugs.python.org fields:

    activity = <Date 2011-03-17.12:52:32.827>
    actor = 'jcea'
    assignee = 'none'
    closed = True
    closed_date = <Date 2009-05-12.17:07:48.307>
    closer = 'ajaksu2'
    components = ['Build']
    creation = <Date 2007-03-07.22:07:56.000>
    creator = 'belopolsky'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 1676121
    keywords = []
    message_count = 6.0
    messages = ['31465', '31466', '31467', '84677', '84740', '122240']
    nosy_count = 5.0
    nosy_names = ['loewis', 'jcea', 'belopolsky', 'ajaksu2', 'rpetrov']
    pr_nums = []
    priority = 'low'
    resolution = 'duplicate'
    stage = 'resolved'
    status = 'closed'
    superseder = '1204'
    type = 'behavior'
    url = 'https://bugs.python.org/issue1676121'
    versions = ['Python 2.6']

    Activity

    1. abalkin commented on Mar 7, 2007

      @abalkin
      MemberAuthor

      Configuring with

      ./configure --with-gcc="gcc -m64 -L/usr/sfw/lib/64 -R/usr/sfw/lib/64"

      where 64bit libreadline is found in /usr/sfw/lib/64, configure script fails to realize that readline lib is present.

      I was able to fix the problem by editing config script manually as follows:

      $ diff configure~ configure
      20744c20744
      < if test "$ac_cv_have_readline_readline" = no

      if test "$ac_cv_lib_readline_readline" = no
      20747c20747
      < echo "$as_me:$LINENO: checking for readline in -ltermcap" >&5
      ---
      echo "$as_me:$LINENO: checking for readline in -lreadline -ltermcap" >&5
      20753c20753
      < LIBS="-ltermcap $LIBS"
      ---
      LIBS="-lreadline -ltermcap $LIBS"

      A proper fix would be to change configure.in, but I don't know enough about autoconf to submit a proper patch.

    2. loewis commented on Mar 8, 2007

      loewismannequin
      Mannequin

      The right solution in this case is to edit Modules/Setup

    3. abalkin commented on Mar 8, 2007

      @abalkin
      MemberAuthor

      Can you explain how to edit Module/Setup to solve this problem?

      Note that the problem that I see comes before modules are built. In fact it comes even before make.

      In any case, I think the check for $ac_cv_have_readline_readline" = no instead of "$ac_cv_lib_readline_readline" = no looks like a typo in configure.in. And looking for readline in libtermcap does not look like sound logic either.

    4. devdanzin commented on Mar 30, 2009

      devdanzinmannequin
      Mannequin

      The "ac_cv_have_readline" check isn't present in trunk. I'll close this
      unless someone voices opposition.

    5. added
      buildThe build process and cross-build
      type-bugAn unexpected behavior, bug, or error
      on Mar 30, 2009
    6. abalkin commented on Mar 31, 2009

      @abalkin
      MemberAuthor

      I don't have a Solaris box to test at the moment, but I believe the
      following commit fixed this issue:

      ------------------------------------------------------------------------
      r66283 | gregory.p.smith | 2008-09-07 01:15:18 -0400 (Sun, 07 Sep
      2008) | 5 lines

      • Issue bpo-1204: The configure script now tests for additional libraries
        that may be required when linking against readline. This fixes issues
        with x86_64 builds on some platforms (at least a few Linux flavors as
        well as OpenBSD/amd64).

      ------------------------------------------------------------------------

      If it is the case, this issue should be closed as a duplicate of bpo-1204.

    7. rpetrov commented on Nov 23, 2010

      rpetrovmannequin
      Mannequin

      Hmm why you dont use LDFLAGS ?
      It is well documented what to expect during configuration and build phase.

    8. transferred this issue fromon Apr 10, 2022
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      buildThe build process and cross-buildtype-bugAn unexpected behavior, bug, or error

      Projects

      No projects

        Milestone

        No milestone

        Relationships

        None yet

        Development

        No branches or pull requests

        Issue actions