From: Alexandre Oliva <aoliva@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: binutils@sources.redhat.com
Subject: Re: libtool changes for HP-UX IA64 support
Date: Sun, 27 Jan 2002 21:00:00 -0000 [thread overview]
Message-ID: <or7kq3unfk.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: Daniel Jacobowitz's message of "Sun, 27 Jan 2002 21:17:14 -0500"
On Jan 28, 2002, Daniel Jacobowitz <drow@mvista.com> wrote:
> Both I and Alexandre approve of this patch, so it certainly should go
> in. Is there anyone out there more familiar than I with what needs to
> be regenerated to do this?
Only configure files have to be rebuild with autoconf.
> My installed auto* are different enough from the existing ones, and
> even those on sourceware marked as 'right' for this tree take away all
> the nice '\'s in Makefile.in's and produce some attrocious long lines.
I often use an internal-to-Red Hat version of autotools, just because
that's what we use for our internal CVS repository, and it happens to
preserve Makefile.am line breaks in Makefile.in. I think this
particular snapshot may be somewhere out there, but I don't know
where. In this case, you don't have to rebuild the Makefile.ins, so
just touch them (or let them be rebuilt and then revert their changes
instead of checking them in) and you'll be fine.
> If there's a new blessed version, it'd be nice to know what it was.
> I'd even suggest it should be in the tree somewhere!
IMO, we should aim at switching to automake 1.5, autoconf 2.52 and
then the next release of libtool. Unless I'm mistaken, the migration
path is in the order I listed.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2002-01-28 4:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-22 16:44 Steve Ellcey
2002-01-22 18:03 ` Alexandre Oliva
2002-01-23 3:06 ` Daniel Jacobowitz
2002-01-27 20:39 ` Daniel Jacobowitz
2002-01-27 21:00 ` Alexandre Oliva [this message]
2002-01-27 22:11 ` Daniel Jacobowitz
2002-01-27 23:10 ` Daniel Jacobowitz
2002-01-28 1:55 ` Alexandre Oliva
2002-01-23 9:54 Steve Ellcey
2002-01-23 10:59 ` Alexandre Oliva
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=or7kq3unfk.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=drow@mvista.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).