Ticket #2343 (closed bug: invalid)

Opened 5 years ago

Last modified 5 years ago

Docs are installed to a peculiar location

Reported by: bos Owned by:
Priority: normal Milestone: 6.8.3
Component: Compiler Version: 6.8.2
Keywords: Cc:
Operating System: Linux Architecture: Unknown/Multiple
Type of failure: Difficulty: Unknown
Test Case: Blocked By:
Blocking: Related Tickets:

Description

Working with the ghc-6.8.2.20080603 snapshot, I run into a problem whereby the generated haddocks are installed to the root of the filesystem, instead of the destination I specify.

This is a change in behaviour from 6.8.2.

(By the way, I'm using haddock 0.8, if that has any significance.)

Here is how I am setting up the build:

./configure --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com --mandir=/usr/share/man

After the main build succeeds, I install as follows:

make DESTDIR=/var/tmp/ghc-6.8.2.20080603-1.fc9-root-bos libdir=/usr/lib64/ghc-6.8.2.20080603 install
make DESTDIR=/var/tmp/ghc-6.8.2.20080603-1.fc9-root-bos XMLDocWays=html HADDOCK_DOCS=YES install-docs

The main install target seems to have no problems, but install-docs installs everything to $DESTDIR, not to the docdir subdirectory of $DESTDIR that used to work with 6.8.2.

Attachments

rpmbuild.out.bz2 Download (118.3 KB) - added by bos 5 years ago.
Build log
ghc.spec Download (14.4 KB) - added by bos 5 years ago.
Build instructions

Change History

Changed 5 years ago by igloo

  • difficulty set to Unknown
  • milestone set to 6.8.3

I don't understand what's going on here. Do you have a mk/build.mk? What other commands are you running? Just plain make between configuring and installing? install-docs shouldn't be installing the haddocks, install should be.

Changed 5 years ago by bos

Build log

Changed 5 years ago by bos

Build instructions

Changed 5 years ago by bos

I've attached the build instructions as ghc.spec and the log as rpmbuild.out.bz2. You can see the commands being executed in the log file by searching for lines beginning with "+ ".

The build.mk file is simple:

cat <<HADDOCK_PATH_HACK >> mk/build.mk
docdir  := %{_docdir}/%{name}-%{version}
htmldir := $(docdir)
dvidir  := $(docdir)
pdfdir  := $(docdir)
psdir   := $(docdir)
HADDOCK_PATH_HACK

This hackery was necessary under ghc 6.8.2.

Changed 5 years ago by igloo

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

The problem is that this was generating mk/build.mk containing:

docdir  := /usr/share/doc/ghc-6.8.2.20080603
htmldir := 
dvidir  := 
pdfdir  := 
psdir   := 

Changed 5 years ago by simonmar

  • architecture changed from Unknown to Unknown/Multiple
Note: See TracTickets for help on using tickets.