Strange gump warning for ./configure

[Graham Leggett <mi...@sharp.fm>]

Hi all,

While trying to build a C/C++ package using ./configure; make; make
install, I have the configure step defined like so:

  <!-- C/C++ build -->
  <project name="monaco-xml-configure">
    <configure>
      <arg name="--prefix" path="dest-@@DATE@@"/>
      <arg name="--enable-libxml2"/>
    </configure>
    <home nested="dest-@@DATE@@"/>
    <license name="LICENSE.txt" />
    <nag to="svn_fo_monaco@xxx.co.za" from="SVN FO Monaco
&lt;svn_fo_monaco@xxx.co.za&gt;" />
  </project>

This configure step seems to work fine, the command line is reported as:

 Command Line: /udd001/hoops/gump/monaco-xml/configure
 --enable-libxml2
 --prefix=/udd001/hoops/gump/monaco-xml/dest-08072005

However, an email gets sent out as a warning with the following in it:

 Project monaco-xml-configure contains errors.
 The current state of this project is 'Success'.

 Full details are available at:
    /monaco-xml/monaco-xml-configure/index.html

 That said, some information snippets are provided here.

 The following annotations (debug/informational/warning/error
 messages) were provided:
  -ERROR- Unhandled Property: --enable-libxml2 on: Configure
  on Project:monaco-xml-configure

It seems that gump is not happy with the --enable-libxml2 option to
configure, although it does work.

Am I doing something incorrectly, or is the warning being sent in error?

Regards,
Graham
--


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: Strange gump warning for ./configure

["Adam R. B. Jack" <aj...@apache.org>]

>  The following annotations (debug/informational/warning/error
>  messages) were provided:
>   -ERROR- Unhandled Property: --enable-libxml2 on: Configure
>   on Project:monaco-xml-configure
>
> It seems that gump is not happy with the --enable-libxml2 option to
> configure, although it does work.

Reading your use case and this:

    http://gump.apache.org/metadata/builder.html#property%2Farg

it sure seems like a bug in Gump. We were trying to help out folks who had
(say) mistakenly typo'd the attribute name & ended up disallowing an
optional/missing field. See if the change I just commit fixes it.

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org