This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project GNU Libtool.
The branch, lto has been created
at 327f014068d2f709f0e38282d6b36725573a45c7 (commit)
- Log
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project GNU Libtool.
The branch, master has been updated
via 0f052db3b89835904b95d8336b2491e7b8eef8f7 (commit)
via
Den 2010-09-01 23:30 skrev Ralf Wildenhues:
* Peter Rosin wrote on Wed, Sep 01, 2010 at 10:33:59PM CEST:
From 16232cc7ddfc4bab981a2fa2d87757c68832b32e Mon Sep 17 00:00:00 2001
From: Peter Rosin p...@lysator.liu.se
Date: Sun, 29 Aug 2010 18:26:16 +0200
Subject: [PATCH 4/7] Use
On 2 Sep 2010, at 12:40, Charles Wilson wrote:
'Course, I notice that I screwed up the date in the ChangeLog. Could
the next person to commit a change to that file, please fix it?
-2010-09-31 ...
+2010-09-01 ...
Might be unnecessary...
In my use-gnulib branch, I'm wondering whether to
Den 2010-09-01 22:30 skrev Peter Rosin:
Hi!
I was going to hold off this until after I had run the testsuite one more
time with the latest fixes, but the recent message from Gary made me post
right away. By the Lay of Murphy, I'm sure I'll regret it...
This series is a rebased and updated
On 9/2/2010 9:06 AM, Peter Rosin wrote:
However, my previous suggestion with a naive_slashify instead of
naive_backslashify doesn't work either since MSYS turns @c:/foobar into
@c;c:\msys\1.0\foobar (or something similar, that was from memory) which
we must avoid at all cost. cygpath -m
Den 2010-09-02 16:02 skrev Charles Wilson:
On 9/2/2010 9:06 AM, Peter Rosin wrote:
However, my previous suggestion with a naive_slashify instead of
naive_backslashify doesn't work either since MSYS turns @c:/foobar into
@c;c:\msys\1.0\foobar (or something similar, that was from memory) which
Hi!
[Automakers, this is from the libtool-patches list...]
Den 2010-09-02 15:06 skrev Peter Rosin:
112: Test 24 33 34 45 47 99 100 are new failures with low max_cmd_len
and I think the reason is that the file name conversion adds escapes for
the backslashes. I.e. .libs/a1.obj - .libs\\a1.obj
Den 2010-09-02 16:08 skrev Peter Rosin:
Den 2010-09-02 16:02 skrev Charles Wilson:
On 9/2/2010 9:06 AM, Peter Rosin wrote:
However, my previous suggestion with a naive_slashify instead of
naive_backslashify doesn't work either since MSYS turns @c:/foobar into
@c;c:\msys\1.0\foobar (or
* Peter Rosin wrote on Thu, Sep 02, 2010 at 09:00:13AM CEST:
Den 2010-09-01 23:30 skrev Ralf Wildenhues:
* libltdl/m4/libtool.m4 (_LT_LINKER_SHLIBS) [cygwin,mingw,pw32]
[cegcc]: Drop fix_srcfile_path.
Please ask google codesearch whether fix_srcfile_path is used by third
party packages
http://autobuild.josefsson.org/libtool/log-201008291316534087000.txt
| ../../libtool/tests/help.at:164: $orig_LIBTOOL --mode=install cp liba.la
libb.la $libdir
| stderr:
| cp: cannot create
/tmp/lt/build-hppa2.0w-hp-hpux11.11/tests/testsuite.dir/023/inst/lib/liba.sl.0.0:
Permission denied
|
On 9/2/2010 3:05 AM, Gary V. Vaughan wrote:
On 2 Sep 2010, at 12:40, Charles Wilson wrote:
'Course, I notice that I screwed up the date in the ChangeLog. Could
the next person to commit a change to that file, please fix it?
-2010-09-31 ...
+2010-09-01 ...
Might be unnecessary...
Well,
[adding bug-gnulib]
On 09/02/2010 03:00 PM, Charles Wilson wrote:
IF we want to use gitlog to create the ChangeLog, then either of these
is fine with me. However, see below.
iii) fix the gitlog entries -- if that's even viable?
I don't think (iii) will work. You can play all sorts
On 9/2/2010 5:08 PM, Eric Blake wrote:
On 09/02/2010 03:00 PM, Charles Wilson wrote:
Two people worked on a single patch, or someone submitted it, and then
one of the people with commit access modified the patch slightly. The
GCS says you should do this, in the ChangeLog:
On 09/02/2010 03:16 PM, Charles Wilson wrote:
On 9/2/2010 5:08 PM, Eric Blake wrote:
On 09/02/2010 03:00 PM, Charles Wilson wrote:
Two people worked on a single patch, or someone submitted it, and then
one of the people with commit access modified the patch slightly. The
GCS says you should
On 2 Sep 2010, at 03:50, Ralf Wildenhues wrote:
* Gary V. Vaughan wrote on Wed, Sep 01, 2010 at 10:39:18PM CEST:
I don't have time either until Sunday at the earliest.
I don't either. So please let's move this a week or two off.
Peter and Charles have several remaining patches too.
Okay,
On Wed, 1 Sep 2010, Ralf Wildenhues wrote:
Hello Gary,
* Gary V. Vaughan wrote on Wed, Sep 01, 2010 at 10:00:20PM CEST:
Unless there are any unmerged patches or unresolved issues to bring to
my attention, I'll make a new libtool release from the HEAD of master
branch this coming weekend
Hi Bob,
* Bob Friesenhahn wrote on Thu, Sep 02, 2010 at 08:45:02PM CEST:
On Wed, 1 Sep 2010, Ralf Wildenhues wrote:
* Gary V. Vaughan wrote on Wed, Sep 01, 2010 at 10:00:20PM CEST:
Unless there are any unmerged patches or unresolved issues to bring to
my attention, I'll make a new libtool
On Thu, 2 Sep 2010, Ralf Wildenhues wrote:
While I doubt that I am qualified to review the patch, I am
definitely interested in seeing autotools fully support LTO.
Can you try out the patch series, ideally on something other than
GNU/Linux? If it helps you, I can push the branch I have it
* Bob Friesenhahn wrote on Thu, Sep 02, 2010 at 08:59:25PM CEST:
On Thu, 2 Sep 2010, Ralf Wildenhues wrote:
Can you try out the patch series, ideally on something other than
GNU/Linux? If it helps you, I can push the branch I have it on.
First I would need to build a GCC which properly
Hey
Any news about the problem ?
Vincent Torri
On Wed, 25 Aug 2010, Vincent Torri wrote:
On Wed, 25 Aug 2010, Ralf Wildenhues wrote:
* Vincent Torri wrote on Wed, Aug 25, 2010 at 06:46:31AM CEST:
I checked out libtool git 2 days ago and try to compile a library
that uses libole32 or
21 matches
Mail list logo
