On Wed, Sep 18, 2013 at 10:14:16AM -0400, David Edelsohn wrote:
> Please ensure that you use the correct version of autoconf to
> regenerate the files. I don't think that the same version of autoconf
> is used in all directories.
gcc is OK in this respect. autoconf-2.64 is used throughout. It's
I guess I can't really expect to gain an approval to import the
upstream libtool into gcc. Even *I* don't really trust me, although
having looked at it a little I think I could even update
libjava/libltdl. So how about just continuing the status quo and
applying a libtool patch that is already up
I guess I can't really expect to gain an approval to import the
upstream libtool into gcc. Even *I* don't really trust me, although
having looked at it a little I think I could even update
libjava/libltdl. So how about just continuing the status quo and
applying a libtool patch that is already up
On Fri, Aug 23, 2013 at 10:08:29PM +, Joseph S. Myers wrote:
> On Fri, 23 Aug 2013, Alan Modra wrote:
>
> > I'd like to import upstream libtool into gcc to support powerpc64le,
>
> Has the sysroot semantics issue been resolved in upstream libtool, or do
> you mean "import with 3334f7ed5851ef
On Fri, 23 Aug 2013, Alan Modra wrote:
> I'd like to import upstream libtool into gcc to support powerpc64le,
Has the sysroot semantics issue been resolved in upstream libtool, or do
you mean "import with 3334f7ed5851ef1e96b052f2984c4acdbf39e20c reverted"?
--
Joseph S. Myers
jos...@codesourcer
On Thu, Aug 22, 2013 at 06:09:40PM -0700, Ian Lance Taylor wrote:
> On Thu, Aug 22, 2013 at 5:35 PM, Alan Modra wrote:
> > On Fri, Aug 16, 2013 at 06:18:05PM +0930, Alan Modra wrote:
> >> I'd like to apply the following patch to the gcc repository (well,
> >> excluding the libgo part which I'm hop
On Thu, Aug 22, 2013 at 5:35 PM, Alan Modra wrote:
> On Fri, Aug 16, 2013 at 06:18:05PM +0930, Alan Modra wrote:
>> I'd like to apply the following patch to the gcc repository (well,
>> excluding the libgo part which I'm hoping someone will apply for me to
>> the master go repository). I know the
On Fri, Aug 16, 2013 at 06:18:05PM +0930, Alan Modra wrote:
> I'd like to apply the following patch to the gcc repository (well,
> excluding the libgo part which I'm hoping someone will apply for me to
> the master go repository). I know the normal procedure for autotools
> is to submit upstream t
On Mon, 21 Nov 2011, Andi Kleen wrote:
> It would be good if that could be done for 4.7. Then slim LTO
> bootstrap has a chance to work. Are there any reasons left not to
> update?
That's one reason. The FreeBSD changes (which we now get
separately) another. The GNU/Linux vs Linux fix that RMS
r
Markus Trippelsdorf writes:
>
> I have deleted the tarballs because they don't apply cleanly anymore.
> But this is not rocket science and you can easily update to the new
> libtool yourself by just copying the new version to the gcc root dir
> and running "ACLOCAL='aclocal -I .. -I ../config' aut
On 2011.11.19 at 20:12 +0100, Gerald Pfeifer wrote:
> [ gcc -> gcc-patches ]
>
> On Tue, 15 Nov 2011, Andreas Tobler wrote:
> > With a libtool import we would cover this and some more issues. I
> > think Markus Trippelsdorf prepared a patch for trunk but I do not
> > know its status. I tested both
11 matches
Mail list logo
