[[Adding Libtool List]]
On 8 Jun 2010, at 08:42, Charles Wilson wrote:
> Which is why I don't think even the Peter's long-ready MSVC patches, nor
> my pile of pending patches, are candidates for this extremely shortened
> release cycle.
Regarding these patches, I honestly have paid very little at
On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
[[Adding Libtool List]]
On 8 Jun 2010, at 08:42, Charles Wilson wrote:
Which is why I don't think even the Peter's long-ready MSVC patches, nor
my pile of pending patches, are candidates for this extremely shortened
release cycle.
Regarding these
Hi Gary!
Den 2010-06-08 09:34 skrev Gary V. Vaughan:
[[Adding Libtool List]]
On 8 Jun 2010, at 08:42, Charles Wilson wrote:
Which is why I don't think even the Peter's long-ready MSVC patches, nor
my pile of pending patches, are candidates for this extremely shortened
release cycle.
Regardin
Hi Vincent,
On 8 Jun 2010, at 15:17, Vincent Torri wrote:
> On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
>
>> [[Adding Libtool List]]
>>
>> On 8 Jun 2010, at 08:42, Charles Wilson wrote:
>>> Which is why I don't think even the Peter's long-ready MSVC patches, nor
>>> my pile of pending patches, ar
Den 2010-06-08 10:22 skrev Peter Rosin:
It seems odd both to (a) have entries from 2009 in the (future-to-be) 2010
ChangeLog and (b) to make changes to the 2009 ChangeLog at this point.
I see that for the first merge of master into the branch last year I
updated the dates in the ChangeLog so tha
On 06/08/2010 02:22 AM, Peter Rosin wrote:
> There's already the pr-msvc-support branch, but when I tried to merge
> master into it to make it easy to merge back later, the ChangeLog rotation
> caused conflicts.
Do you have Bruno Haible's git-merge-changelog program installed on your
machine? For
Den 2010-06-08 11:50 skrev Eric Blake:
On 06/08/2010 02:22 AM, Peter Rosin wrote:
There's already the pr-msvc-support branch, but when I tried to merge
master into it to make it easy to merge back later, the ChangeLog rotation
caused conflicts.
Do you have Bruno Haible's git-merge-changelog pr
[adding Bruno, as author of git-merge-changelog]
On 06/08/2010 04:14 AM, Peter Rosin wrote:
>
> I have git-merge-changelog. But my changes on the branch are in ChangeLog,
> and the question was where they should be after the merge, in ChangeLog
> or in ChangeLog.2009. I was not asking how the mer
On Tue, Jun 8, 2010 at 4:22 AM, Peter Rosin wrote:
> Hi Gary!
>
> Den 2010-06-08 09:34 skrev Gary V. Vaughan:
>>
>> [[Adding Libtool List]]
>>
>> On 8 Jun 2010, at 08:42, Charles Wilson wrote:
>>>
>>> Which is why I don't think even the Peter's long-ready MSVC patches, nor
>>> my pile of pending p
On 8 June 2010 09:17, Vincent Torri wrote:
>
> even if you install mingw cross toolchain on linux ? You can even test
> Windows CE with cegcc on linux
FWIW, my experience is that the mingw cross toolchain on linux is not
a close enough approximation of the "real thing" on Windows; the
problems be
On 8 Jun 2010, at 15:22, Peter Rosin wrote:
> Hi Gary!
Hey Peter!
> Den 2010-06-08 09:34 skrev Gary V. Vaughan:
>> [[Adding Libtool List]]
>>
>> On 8 Jun 2010, at 08:42, Charles Wilson wrote:
>>> Which is why I don't think even the Peter's long-ready MSVC patches, nor
>>> my pile of pending patc
Hi Chris,
Forgive my jumping in again here...
On 8 Jun 2010, at 17:47, Christopher Hulbert wrote:
> On Tue, Jun 8, 2010 at 4:22 AM, Peter Rosin wrote:
>> Den 2010-06-08 09:34 skrev Gary V. Vaughan:
>>> On 8 Jun 2010, at 08:42, Charles Wilson wrote:
Which is why I don't think even the Peter'
On 6/8/2010 2:46 AM, Gary V. Vaughan wrote:
> [[Adding Libtool List]]
>
> On 8 Jun 2010, at 08:56, Charles Wilson wrote:
>> What happens if libltdl is
>> used to load (say) libtiff which has an automatic dependency on libjpeg?
>> The initial LoadLibrary from libltdl pulls in libtiff.dll AND
>> lib
On Tue, Jun 8, 2010 at 7:40 AM, Gary V. Vaughan wrote:
> Hi Chris,
>
> Forgive my jumping in again here...
No problem, at least the subject is being talked about.
>
> On 8 Jun 2010, at 17:47, Christopher Hulbert wrote:
>> On Tue, Jun 8, 2010 at 4:22 AM, Peter Rosin wrote:
>>> Den 2010-06-08 09:
Hi Christopher!
Den 2010-06-08 15:06 skrev Christopher Hulbert:
On Tue, Jun 8, 2010 at 7:40 AM, Gary V. Vaughan wrote:
I think it important to merge pr-msvc-support into master one way or
another so that it doesn't get ignored for any longer than it has already.
I would like it to not get ig
On Tue, Jun 8, 2010 at 9:24 AM, Peter Rosin wrote:
> Hi Christopher!
>
> Den 2010-06-08 15:06 skrev Christopher Hulbert:
>>
>> On Tue, Jun 8, 2010 at 7:40 AM, Gary V. Vaughan wrote:
>>>
>>> I think it important to merge pr-msvc-support into master one way or
>>> another so that it doesn't get ign
Hi Chris,
On 8 Jun 2010, at 20:06, Christopher Hulbert wrote:
> On Tue, Jun 8, 2010 at 7:40 AM, Gary V. Vaughan wrote:
>>
>> I think it important to merge pr-msvc-support into master one way or
>> another so that it doesn't get ignored for any longer than it has already.
>
> I would like it to
On 8 Jun 2010, at 19:11, Charles Wilson wrote:
> On 6/8/2010 2:46 AM, Gary V. Vaughan wrote:
>> On 8 Jun 2010, at 08:56, Charles Wilson wrote:
>>> What happens if libltdl is
>>> used to load (say) libtiff which has an automatic dependency on libjpeg?
>>> The initial LoadLibrary from libltdl pulls i
Den 2010-06-08 15:40 skrev Christopher Hulbert:
On Tue, Jun 8, 2010 at 9:24 AM, Peter Rosin wrote:
I've had enough frustration here, methinks.
Sorry for my contribution to your frustration. I would just like to
see windows support in the mainstream to be done right, and the
attitude of "just
On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
More interesting still: I think things might blow up if the .la files
have been removed on a platform that does automatic deplib loading for
runtime linking, say lt_dlopening libpng.dll (which pulls in zlib
through LoadLibrary without libltdl knowing ab
Hi Bob,
On 8 Jun 2010, at 23:04, Bob Friesenhahn wrote:
> On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
>>
>> More interesting still: I think things might blow up if the .la files
>> have been removed on a platform that does automatic deplib loading for
>> runtime linking, say lt_dlopening libpng.dl
On Tue, 8 Jun 2010, Charles Wilson wrote:
If it doesn't, then that's a bug. Libltdl is supposed to keep track
of everything it loads,
But the point here is that Bob is advocating that (in the first half of
the example above) *libltdl* does NOT explicitly load the libjpeg
dependency. However,
On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
Obviously this is already working fine. Windows LoadLibrary() is
smart enough to know what it has already loaded. The unloading
sequence is much more interesting since something could be unloaded
which is still being used.
Looks like another inte
On Tue, Jun 8, 2010 at 11:03 AM, Peter Rosin wrote:
> Den 2010-06-08 15:40 skrev Christopher Hulbert:
>>
>> On Tue, Jun 8, 2010 at 9:24 AM, Peter Rosin wrote:
>>>
>>> I've had enough frustration here, methinks.
>>
>> Sorry for my contribution to your frustration. I would just like to
>> see windo
Hi Gary,
Am 6/4/2010 1:44 PM, schrieb Gary V. Vaughan:
> * Changes in supported systems or compilers:
>
> - Improved support for 64bit Windows (mingw64).
> - Improved support for cegcc (Windows CE/PocketPC).
> - Support for GNU/kOpenSolaris (kopensolaris*-gnu).
> - Initial support for co
On 6/8/2010 6:47 AM, Christopher Hulbert wrote:
> Peter/Charles,
> Do you have a summary of the capabilities added by your
> patches/branch
I'll let Peter speak for himself, but these are the patches in the
cygwin and mingw distributions:
* Pass various runtime library flags to GCC. (-shared-li
Hi Bob,
On 8 Jun 2010, at 23:19, Bob Friesenhahn wrote:
> On Tue, 8 Jun 2010, Gary V. Vaughan wrote:
>>>
>>> Obviously this is already working fine. Windows LoadLibrary() is smart
>>> enough to know what it has already loaded. The unloading sequence is much
>>> more interesting since somethin
27 matches
Mail list logo
