#476 sed not neccessarily in /usr/bin

Cannot reproduce
closed-works-for-me
5
2008-02-28
2006-09-13
No

When attempting to build under gentoo, I had to do:
ln -s /bin/sed /usr/bin/sed
in order for the "make install" to complete. It turns
out libtool assumes sed is found in /usr/bin.

Bill

Discussion

  • Robert Krawitz

    Robert Krawitz - 2006-09-13
    • labels: --> Build/installation
    • assigned_to: nobody --> rleigh
     
  • Robert Krawitz

    Robert Krawitz - 2006-09-13

    Logged In: YES
    user_id=5436

    What OS and what version are you running?

     
  • Robert Krawitz

    Robert Krawitz - 2007-02-10

    Logged In: YES
    user_id=5436
    Originator: NO

    Ah sorry, I notice you listed gentoo.

     
  • Anonymous - 2007-02-10

    Logged In: YES
    user_id=116840
    Originator: NO

    Note that Gentoo is not unique in placing sed in /bin. Debian also used /bin rather than /usr/bin.

    Which libtool assumes sed is found in /usr/bin?

    % grep ^SED /usr/bin/libtool
    SED="/bin/sed"

    When you run configure, you should see:

    checking for a sed that does not truncate output... /bin/sed
    [...]
    configure: creating libtool

    This comes from the LT_AC_PROG_SED macro in configure, which you'll find at the bottom of libtool.m4. If it's finding a /usr/bin/sed, you need to

    1) Look at config.log to see why. Look for all lines containing 'sed'. The value used is in lt_cv_path_SED.
    2) Check if there's a SED environment variable set which might confuse configure.
    3) Check for a config.site containing a predefined SED.
    4) Check for a cache (config.cache) containing an out of date SED.

    As far as I can see, our configure and libtool are working just fine. It's working for me with /bin/sed without problems. As a result, I think it's most likely there's some problem with your setup and/or environment which is causing your problem.

    Regards,
    Roger
    3)

     
  • Robert Krawitz

    Robert Krawitz - 2008-02-27

    Logged In: YES
    user_id=5436
    Originator: NO

    Is this still an issue, or has it been fixed? Or is this a libtool bug?

     
  • Dr Bill C Riemers

    Logged In: YES
    user_id=290784
    Originator: YES

    I can't really say if this is an issue. The life expectancy of a Gentoo system for me is about 3 months. After that, I need to re-install from scratch. I switched to Fedora in 2007, so I haven't needed to compile this package since then.

    If it were me, any bug more than a year old, that the reporting can not still reproduce I would close. If someone still has the problem they can always re-open the report.

     
  • Robert Krawitz

    Robert Krawitz - 2008-02-28

    Logged In: YES
    user_id=5436
    Originator: NO

    Closing as there is no way to reproduce this.

     
  • Robert Krawitz

    Robert Krawitz - 2008-02-28
    • milestone: --> Cannot reproduce
    • status: open --> closed-works-for-me
     

Log in to post a comment.