Armagetron Advanced

Uninstall script involves DESTDIR

Bug #579638 reported by Luke-Jr on 2010-05-12

This bug report is a duplicate of: Bug #536677: uninstall scrip magic broken for newer automake versions. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Armagetron Advanced	Triaged	Medium	Unassigned	Armagetron Advanced 0.4.0 "Cronus"

Bug Description

"Prepending the variable DESTDIR to each target in this way provides for staged installs, where the installed files are not placed directly into their expected location but are instead copied into a temporary location (DESTDIR). However, installed files maintain their relative directory structure and any embedded file names will not be modified."

The installed 'uninstall' script tries to do weird stuff with DESTDIR. It shouldn't change based on this variable's value.

Revision history for this message

flea (1337flea) wrote on 2010-11-21:

config.log Edit (29.1 KiB, text/plain)

attached is make install output (fail because of same bug)

(gentoo stable x86)

Revision history for this message

flea (1337flea) wrote on 2010-11-21:

make install Edit (9.2 KiB, text/plain)

well, thats the config.log oops..

heres the make install out put.

Revision history for this message

Manuel Moos (z-man) wrote on 2010-11-22:

It's not actually doing anything with DESTDIR, the precise purpose of the 'weird stuff' is to make sure the uninstall script works even AFTER it has been moved away from DESTDIR. It just fails for current automake versions with no easy fix in sight. Just use --disable-uninstall.

Changed in armagetronad:
status:	New → Invalid

Revision history for this message

Luke-Jr (luke-jr) wrote on 2010-11-22:

I disagree that this bug is invalid. It breaks the standard configure,make,make install process. At the very least, we should disable uninstall by default.