public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@sig21.net>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: crossgcc@sourceware.org, "Chris Morgan" <chmorgan@gmail.com>,
	"Benoît Thébaudeau" <benoit.thebaudeau@advansee.com>
Subject: Re: CLooG build error
Date: Sun, 29 Jan 2012 10:10:00 -0000	[thread overview]
Message-ID: <20120129101030.GA1363@sig21.net> (raw)
In-Reply-To: <201201290007.12267.yann.morin.1998@free.fr>

Hi Yann,

On Sun, Jan 29, 2012 at 12:07:12AM +0100, Yann E. MORIN wrote:
> On Thursday 26 January 2012 16:40:59 Johannes Stezenbach wrote:
> > diff -r 188d58cfe7cf configure.ac
> > --- a/configure.ac	Mon Jan 16 23:45:16 2012 +0100
> > +++ b/configure.ac	Thu Jan 26 16:38:57 2012 +0100
> > @@ -203,7 +203,7 @@
> >                         [Specify the full PATH to GNU libtoolize >= 1.5.26]),
> >          [ac_cv_path_LIBTOOLIZE=$withval])])
> >  AC_CACHE_CHECK([for GNU libtoolize >= 1.5.26], [ac_cv_path_LIBTOOLIZE],
> > -    [AC_PATH_PROGS_FEATURE_CHECK([LIBTOOLIZE], [libtool],
> > +    [AC_PATH_PROGS_FEATURE_CHECK([LIBTOOLIZE], [libtoolize],
> >          [[LIBTOOLIZE_ver=$($ac_path_LIBTOOLIZE --version 2>&1 \
> >                          |$EGREP '\(GNU libtool.*\) (2[[:digit:]]*\.|1\.6[[:digit:]]*\.|1\.5\.[2-9][[:digit:]]+)')
> >            test -n "$LIBTOOLIZE_ver" && ac_cv_path_LIBTOOLIZE=$ac_path_LIBTOOLIZE ac_path_LIBTOOLIZE_found=:]],
> 
> Indeed, nice cactch.
> 
> Can you reply with your SoB [*] line? No need to resend the patch, I'll add it
> to the commit message.

of course:

Signed-off-by: Johannes Stezenbach <js@sig21.net>


Thank you
Johannes

--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2012-01-29 10:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAAPegz3+cnkhtdzA1MO8caoH-MXAT6GjPDd6g7cUQ5Moetk2kg@mail.gmail.com>
     [not found] ` <CAAPegz20kka=E=vZ11UB9F8JNFyWpX6NDyzo38K7G1SnVo9a+g@mail.gmail.com>
2012-01-25 22:07   ` Chris Morgan
2012-01-26 15:41     ` Johannes Stezenbach
2012-01-26 15:46       ` Chris Morgan
2012-01-26 16:28         ` Johannes Stezenbach
2012-01-26 21:24           ` Chris Morgan
2012-01-27  0:03             ` Benoît Thébaudeau
2012-01-27 10:56               ` Johannes Stezenbach
2012-01-27 12:02                 ` Benoît Thébaudeau
2012-01-27 17:18                   ` Chris Morgan
2012-01-27 20:10                     ` Benoît Thébaudeau
2012-01-27 20:06                   ` Chris Morgan
2012-01-27 20:11                     ` Benoît Thébaudeau
2012-01-27 20:15                       ` Chris Morgan
2012-01-27 17:15                 ` Chris Morgan
2012-01-28 23:07       ` Yann E. MORIN
2012-01-29 10:10         ` Johannes Stezenbach [this message]
2012-01-29 10:53           ` Yann E. MORIN
2012-01-30 21:16             ` Chris Morgan
     [not found] <5c2d9079-5714-4600-829c-08365856a158@zose-store-12>
2012-01-28 22:41 ` Benoît Thébaudeau

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=20120129101030.GA1363@sig21.net \
    --to=js@sig21.net \
    --cc=benoit.thebaudeau@advansee.com \
    --cc=chmorgan@gmail.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@free.fr \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).