Ticket #3610 (closed bug: fixed)

Opened 4 years ago

Last modified 4 years ago

Installer has hard-coded path /usr/bin/strip

Reported by: YitzGale Owned by:
Priority: high Milestone: 6.12.1
Component: Build System Version: 6.10.4
Keywords: Cc:
Operating System: Unknown/Multiple Architecture: Unknown/Multiple
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

On some systems, strip may not be located in /usr/bin. And even if it is, that might not be the version of strip we need to use, e.g., in a virtual hosting environment.

See, for example,  this blog post about installing GHC on Dreamhost.

It seems that GHC ought to locate strip using $PATH, or some other mechanism that can be configured.

Change History

Changed 4 years ago by YitzGale

To be more clear, the problem described in the blog post occurred while trying to install the binary build of GHC 6.10.4 for x86_64.

Changed 4 years ago by igloo

  • priority changed from normal to high
  • difficulty set to Unknown
  • milestone set to 6.12.1

Ah, I was confused as to where this path was hard coded at first, but it turns out it's in the Cabal setup-config files. I guess we'll have to override this in ghc-cabal.

Changed 4 years ago by duncan

So is the problem that we're configuring on one machine (the bindist builder) and then installing on another (the target)? So paths from the builder end up in the config and do not match on the target.

Strictly speaking that's not a supported mode of operation for Cabal. It supports building an installable image on one machine and installing and registering that on another.

Changed 4 years ago by igloo

  • status changed from new to closed
  • resolution set to fixed

Fixed in HEAD and 6.12 by:

Sun Nov  8 12:02:04 GMT 2009  Ian Lynagh <igloo@earth.li>
  * Tell ghc-cabal what strip program to use
Note: See TracTickets for help on using tickets.