Going to the website referred to in the error message,
gives this information:
“Starting with Automake 1.8, aclocal will warn about
all underquoted calls to AC_DEFUN. We realize this
will annoy a lot of people, because aclocal was not so
strict in the past and many third party macros are
underquoted; and we have to apologize for this
temporary inconvenience.” (…more info follows)
I am running Ubuntu GNU/Linux 6.10 on a HP Pavillion
8665C, with has an Intel P3 cpu running at 600 MHz.
Is there something that I am doing wrong? Any info
would be greatly appreciated.
Mike G.berg
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
Is there something that I am doing wrong? Any info
would be greatly appreciated.
These messages are almost always harmless. It looks like bootstrap is
finishing ok otherwise–have you gone ahead and tried finishing the
install/compile?
If it really bothers you, you can edit the /usr/share/aclocal/jmax.m4
file (as root). You’ll see near the top an AC_DEFUN(xxx, …) where
‘xxx’ is a macro name and ‘…’ is all the rest of the line before the
final parens. Just put make this ‘[xxx]’ by adding the brackets (don’t
put in the single quotes). This change, however, will get overwritten
the next time that package gets updated, until the author of the package
fixes it.
On Wed, Jan 03, 2007 at 07:52:26PM -0800, Johnathan C. wrote:
would be greatly appreciated.
These messages are almost always harmless. It looks like bootstrap is
finishing ok otherwise–have you gone ahead and tried finishing the
install/compile?
Until the deprecated feature breaks
This one in particular is not one of ours, and shouldn’t cause a
problem.
If it really bothers you, you can edit the /usr/share/aclocal/jmax.m4
file (as root). You’ll see near the top an AC_DEFUN(xxx, …) where
‘xxx’ is a macro name and ‘…’ is all the rest of the line before the
final parens. Just put make this ‘[xxx]’ by adding the brackets (don’t
put in the single quotes). This change, however, will get overwritten
the next time that package gets updated, until the author of the package
fixes it.
The right answer is to submit a patch upstream to whomever maintains
jmax.m4. I assume is has something to do with “jmax”, whatever that
is
Eric
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.