Reuben Thomas wrote:
> On Mon, 6 Apr 2009, Jim Meyering wrote:
>
>> Ok by me. Though I don't like the use of $(C_SOURCES), as I
>> mentioned. I do understand you're trying to do this gradually. I'd
>> be inclined to make bigger changes ;-) It's only "make
>> syntax-check", after all.
>
> OK, I'm
Bruno Haible writes:
> Ben Pfaff wrote:
>> Here is a gnulib commit that I am proposing. It (cross)compiles
>> on Mingw, but I am waiting to hear back from my Windows tester to
>> find out whether it actually solves the problem for him.
>
> How does MoveFileEx with MOVEFILE_REPLACE_EXISTING behav
The 'int' type is signed - except in bit fields, where it is platform dependent
whether 'int x : 7' defines a signed or unsigned bit field. Solaris cc,
AIX xlc, and OSF/1 cc all interpret it as unsigned.
The workaround is to always use the keyword 'signed' or 'unsigned' in
bit-fields.
2009-04-06
On Mon, 6 Apr 2009, Jim Meyering wrote:
Ok by me. Though I don't like the use of $(C_SOURCES), as I mentioned.
I do understand you're trying to do this gradually. I'd be inclined to
make bigger changes ;-) It's only "make syntax-check", after all.
OK, I'm just trying to make changes that I
Reuben Thomas wrote:
> On Sat, 4 Apr 2009, Jim Meyering wrote:
>> Reuben Thomas wrote:
>>> On Sat, 4 Apr 2009, Jim Meyering wrote:
>>>
Those buglets were from coreutils' maint.mk.
>>>
>>> Just to be clear, the buglets were from coreutils' maint.mk, but the
>>> patch I sent was a patch to gnuli
Ralf Wildenhues asked:
> Are we committing to a stable API and ABI now?
No, it's still the responsibility of the distributor of a shared library
package to ensure that its API is maintained (if the library uses libtool
versioning).
For restricting the exported symbols, there's
- the approach wi
