New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix non-POSIX usage of "echo -n" in configure script (Origin: bugzilla #673218) #4650

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component build for ---
Reported in version 1.8.0 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-03-31 02:44:59 +0000, Ryan Schmidt wrote:

Created attachment 211012
proposed patch

On OS X Snow Leopard and up, the configure script has output like this:

-n Checking for platform macosx-c++...
-n Checking for GNU make tool...
using /opt/local/bin/gmake
-n Checking for GNU install tool...
using /opt/local/bin/ginstall
-n Checking for dot (part of GraphViz)...
using /opt/local/bin/dot
-n Checking for perl...
using /opt/local/bin/perl
-n Checking for flex...
using /opt/local/bin/flex
-n Checking for bison...
using /opt/local/bin/bison

This patch fixes it by replacing "echo -n" with "printf".

On 2012-05-01 12:25:22 +0000, André Klapper wrote:

Comment on attachment 211012
proposed patch

[Fixing wrong mime type and set "patch" flag so it can be queried for.]

On 2013-02-14 00:40:21 +0000, Eric Gallager wrote:

MacPorts has recently started applying a similar patch (it might even be the exact same one, idk):

The MacPorts issue that led to the project adding the patch can be found at:

On 2013-02-14 01:25:09 +0000, Ryan Schmidt wrote:

It's the same patch, defuzzed (line numbers updated).

On 2013-03-04 19:45:35 +0000, Dimitri van Heesch wrote:

Thanks, I'll include it in the next subversion update.

On 2013-05-19 12:36:28 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment