From: chrubis@suse.cz
To: Vinson Lee <vlee@twopensource.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] GCC_WARN_OLDSTYLE build error
Date: Mon, 21 Jul 2014 09:27:10 +0200 [thread overview]
Message-ID: <20140721072710.GA14496@rei> (raw)
In-Reply-To: <CAHTgTXVrf6yFoD7_tPmJSO1CZFsx19DyA-stfYTqujpBUUF0sQ@mail.gmail.com>
Hi!
> > That looks like the variable from config.mk.in wasn't substitued
> > correctly.
> >
> > Does it work when you readd the -I m4 to the automake.mk that this patch
> > has removed?
> >
> > Does the 'make autotools' print any warnings for AC_CONFIG_MACRO_DIR?
> >
> > --
> > Cyril Hrubis
> > chrubis@suse.cz
>
> 'make autotools' does not print any warnings.
>
> The build passes if I readd '-I m4' to automake.mk.
I've pushed a patch that readds it to the automake.mk, the problem is
that AC_CONFIG_MACRO_DIR() was broken and works only in recent enough
autotools. See the reply to Joseph for more information.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2014-07-21 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHTgTXWCNZzL+6ptrMgwR5d2UA4dcSka_C=off87axRqsgbm1Q@mail.gmail.com>
2014-07-15 18:54 ` [LTP] GCC_WARN_OLDSTYLE build error chrubis
[not found] ` <CAHTgTXVrf6yFoD7_tPmJSO1CZFsx19DyA-stfYTqujpBUUF0sQ@mail.gmail.com>
2014-07-21 7:27 ` chrubis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140721072710.GA14496@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=vlee@twopensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.