You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./configure --prefix /opt/foo works fine, but --prefix=/opt/foo
is not recognized. This is only a trivial problem for humans,
but it's less trivial for metabuild systems that would like
to pass the same default configure line to all packages.
It wouldn't be too hard to support = across the board, but
because these metabuild systems tend to use only a very small
number of options, they can be pacified with a trivial patch
that adds = support for just the particular options they use.
That's what I did to get me past the problem. Here's the patch I used.
On 2014-01-22 19:02:43 +0000, albert wrote:
Looks like you forgot to attach the patch
On 2014-01-22 19:14:10 +0000, Dan Kegel wrote:
Created attachment 266993
Draft trivial patch
Sorry, had a cable modem outage just as I was posting, and didn't recover well.
On 2014-01-26 08:58:04 +0000, Dimitri van Heesch wrote:
Thanks, I'll include the patch in the next GIT update.
On 2014-04-21 10:09:21 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).
The text was updated successfully, but these errors were encountered:
status RESOLVED severity enhancement in component build for ---
Reported in version 1.8.6-GIT on platform Other
Assigned to: Dimitri van Heesch
Original attachment names and IDs:
On 2014-01-22 18:43:01 +0000, Dan Kegel wrote:
On 2014-01-22 19:02:43 +0000, albert wrote:
On 2014-01-22 19:14:10 +0000, Dan Kegel wrote:
On 2014-01-26 08:58:04 +0000, Dimitri van Heesch wrote:
On 2014-04-21 10:09:21 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: