From: Steve Ellcey <sje@cup.hp.com>
To: toa@pop.agri.ch
Cc: jjohnstn@redhat.com, bonzini@gnu.org,
libtool@cwilson.fastmail.fm, newlib@sourceware.org,
aoliva@redhat.com, gcc-patches@gcc.gnu.org,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: New libtool is in the GCC and Src trees.
Date: Thu, 24 May 2007 20:33:00 -0000 [thread overview]
Message-ID: <200705242032.NAA13355@hpsje.cup.hp.com> (raw)
In-Reply-To: <4655EF30.3080705@pop.agri.ch>
> gcc builds fail on Darwin. Attached a patch which cures the issue.
> Also, I'm analyzing the build failure in libjava, seems you forgot to
> regen the part in classpath.
>
> Ok?
>
> Thanks,
> Andreas
ltmain.sh is part of the new libtool, do you know if the ToT libtool has
this fixed?
I am not sure what happened with libjava. I ran
aclocal -I . -I .. -I ../config;automake;autoconf
in the libjava directory. That regenerated the top level configure
script and the Makefile.in files in the gcj, include, and testsuite
subdirs. I don't know why it didn't do anything to the classpath
subdir.
Steve Ellcey
sje@cup.hp.com
next prev parent reply other threads:[~2007-05-24 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-24 17:35 Steve Ellcey
2007-05-24 18:07 ` Steve Ellcey
2007-05-24 18:46 ` Steve Ellcey
2007-05-24 20:02 ` Andreas Tobler
2007-05-24 20:33 ` Steve Ellcey [this message]
2007-05-24 21:09 ` Andreas Tobler
2007-05-24 21:14 ` libtool
2007-05-24 22:13 ` Mike Stump
2007-05-25 17:38 ` Andreas Tobler
2007-05-25 17:43 ` Paolo Bonzini
2007-05-25 17:50 ` Eric Christopher
2007-05-25 19:33 ` Andreas Tobler
2007-05-25 19:39 ` Eric Christopher
2007-05-24 20:37 ` Mike Stump
2007-05-25 0:12 ` Andrew Pinski
2007-05-28 12:49 ` Andreas Schwab
2007-05-28 19:07 ` Charles Wilson
2007-05-29 1:25 ` Peter O'Gorman
2007-05-28 13:33 ` Andreas Schwab
[not found] <m3irah6d45.fsf@fleche.redhat.com>
2007-05-25 18:21 ` Steve Ellcey
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=200705242032.NAA13355@hpsje.cup.hp.com \
--to=sje@cup.hp.com \
--cc=aoliva@redhat.com \
--cc=binutils@sourceware.org \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jjohnstn@redhat.com \
--cc=libtool@cwilson.fastmail.fm \
--cc=newlib@sourceware.org \
--cc=toa@pop.agri.ch \
/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