[Pkg-e-devel] Bug#535768: Bug#535768: Bug#535768: evas: plop

[Manuel Menal]

On Sun, July 5, 2009 1:41 pm, Joachim Breitner wrote:
> Hi,

Hello,

> Am Sonntag, den 05.07.2009, 12:27 +0200 schrieb Albin Tonnerre:
>> On Sat, Jul 04, 2009 at 10:38:45PM +0200, Manuel Menal wrote :
>> > evas uses the PATH_MAX constant, which is optional on POSIX and
>> undefined on GNU/Hurd.
>>
>> Does Hurd enjoy not defining widely-used constants just because they're
>> optional, or are there actual technical reasons for this ? If so, I'd
>> like to
>> know what they are.

> The reason is, IIRC, that there is no maximal path length in hurd – so
> what could possibly be the value of such a constant?

True. GNU/Hurd does not have a global maximal path length. The actual
maximal path length depends on the underlying filesystems, and could be
obtained using pathconf(), but that may not be suitable for memory
allocation (it could be very, very big).

Using dynamic allocation seems the best way to cope with this AFAICS,
although it's not always easy when GNU extensions like asnprintf() or
getcwd(NULL, n) aren't available.

Cheers,

-- 
Manuel Menal