public inbox for libc-ports@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@mips.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>, <libc-ports@sourceware.org>
Subject: Re: [patch, mips] Fix stubs files for hard float vs. soft float
Date: Wed, 24 Oct 2012 16:19:00 -0000	[thread overview]
Message-ID: <1351095503.15035.45.camel@ubuntu-sellcey> (raw)
In-Reply-To: <20121023224821.DA5B52C09F@topped-with-meat.com>

On Tue, 2012-10-23 at 15:48 -0700, Roland McGrath wrote:

> > I guess I could put it in ports/sysdeps/unix/sysv/linux/mips/configure.in
> > instead since the Makefile that includes the generated Makefile is in
> > ports/sysdeps/unix/sysv/linux/mips.  Would that be better?
> 
> Yes, that's the correct place.
> 
> 
> Thanks,
> Roland

Is there a 'trick' to modifying this configure.in file?  If I change
configure.in, remove all autom4te.cache directories from my source
directory, and do a configure/build, the configure file in this
directory does not seem to get automatically updated by autoconf.  If I
try to regenerate configure by running autoconf by hand in that
directory I wind up with an empty configure file (even with no changes
in configure.in).  I thought that the glibc configure/make process was
doing the autoconf automatically, but it doesn't seem to be working for
me now.

What is the right way to regenerate
ports/sysdeps/unix/sysv/linux/mips/configure from
ports/sysdeps/unix/sysv/linux/mips/configure.in?

Steve Ellcey
sellcey@mips.com

  reply	other threads:[~2012-10-24 16:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15 20:15 Steve Ellcey 
2012-10-15 21:15 ` Andreas Schwab
2012-10-15 21:23   ` Andreas Schwab
2012-10-15 22:08 ` Joseph S. Myers
2012-10-15 23:06   ` Steve Ellcey
2012-10-15 23:31     ` Joseph S. Myers
2012-10-22 23:31       ` Steve Ellcey
2012-10-22 23:38         ` Joseph S. Myers
2012-10-23 20:20           ` Steve Ellcey
2012-10-23 21:32             ` Roland McGrath
2012-10-23 22:14               ` Steve Ellcey
2012-10-23 22:48                 ` Roland McGrath
2012-10-24 16:19                   ` Steve Ellcey [this message]
2012-10-24 16:37                     ` Andreas Schwab
2012-10-24 17:13                       ` Steve Ellcey
2012-10-24 17:25                         ` Roland McGrath
2012-10-25  0:00                           ` Steve Ellcey
2012-10-25 12:41                             ` Joseph S. Myers
2012-10-25 20:36                               ` Steve Ellcey
2012-10-26 21:06                               ` Steve Ellcey
2012-10-26 22:11                                 ` Joseph S. Myers
2012-10-26 23:00                                   ` Roland McGrath
2012-10-24 16:41                     ` Joseph S. Myers
2012-10-24  0:05             ` Joseph S. Myers

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=1351095503.15035.45.camel@ubuntu-sellcey \
    --to=sellcey@mips.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-ports@sourceware.org \
    --cc=roland@hack.frob.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 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).