From: Joel Sherrill <joel@rtems.org>
To: simon.marchi@polymtl.ca
Cc: gdb@sourceware.org
Subject: Re: How to Run autoconf on sim/erc32 directory
Date: Wed, 24 Oct 2018 21:02:00 -0000 [thread overview]
Message-ID: <CAF9ehCUcz+J7=0XBabkf=ys4YvVovoP60+dwb4r5ngYLSxmYcA@mail.gmail.com> (raw)
In-Reply-To: <29a3af563c47950be0c741dca50c3432@polymtl.ca>
On Wed, Oct 24, 2018 at 3:32 PM Simon Marchi <simon.marchi@polymtl.ca>
wrote:
> On 2018-10-24 14:47, Joel Sherrill wrote:
> > Hi
> >
> > I have a patch I want to try on Cygwin but I don't seem to have the
> > proper
> > auto-fu to generate configure.
> >
> > Help on the auitoconf command appreciated.
> >
> > Thanks.
>
>
> Hi Joel,
>
> I take it you have changed sim/erc32/configure.ac (or another file that
> goes in making sim/erc32/configure) and you want to re-generate
> sim/erc32/configure? In that case, you just need to go in the sim/erc32
> and run "autoconf" ("autoconf -f" may sometimes be useful if autoconf
> doesn't realize some things have changed).
>
> You should use the same version of autoconf as the version that
> generated the current configure. As you can see in the header, this is
> autoconf 2.69:
>
> # Generated by GNU Autoconf 2.69.
>
> Some Linux distributions have local patches to autoconf, which results
> in spurious diffs when re-generating configure. If that happens, try to
> build and use autoconf from upstream.
>
I decided to take a shot that Cygwin was the trouble. I moved the patch to
Linux, ran autoconf and copied the configure back to Cygwin. My change
worked fine.
This only depended on autoconf 2.69 and the RTEMS version has
no patches.
Thank you. Patch coming shortly
>
> Thanks,
>
> Simon
>
prev parent reply other threads:[~2018-10-24 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-24 18:47 Joel Sherrill
2018-10-24 20:32 ` Simon Marchi
2018-10-24 21:02 ` Joel Sherrill [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='CAF9ehCUcz+J7=0XBabkf=ys4YvVovoP60+dwb4r5ngYLSxmYcA@mail.gmail.com' \
--to=joel@rtems.org \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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