Opened 13 years ago
Closed 13 years ago
#465 closed defect (invalid)
Fix whizard-config and omega-config for installations into default prefix
Reported by: | Christian Speckner | Owned by: | Christian Speckner |
---|---|---|---|
Priority: | P4 | Milestone: | v2.0.7 |
Component: | core | Version: | 2.0.6 |
Severity: | minor | Keywords: | |
Cc: |
Description
All said in description, looks like it is using the wrong autoconf variable.
Change History (5)
comment:1 Changed 13 years ago by
Status: | new → assigned |
---|
comment:2 Changed 13 years ago by
comment:3 Changed 13 years ago by
We were using the 2.0.5. release. Autoconf was 2.68, automake 1.11.1
comment:4 Changed 13 years ago by
Ah, got it. I already fixed this in @3581, which means that the fix is in the current 2.0.6 release. Closing as invalid.
comment:5 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Turns out that I cannot reproduce this on my system with neither the current trunk and autoconf 2.68 nor with the 2.0.6 release tarball. Plain configure gives me valid whizard-config and omega-config scripts with the correct entries for the prefix. JR / Daniel, can you give me more information on how to reproduce this?