[screen-devel] [bug #50089] Screen 4.5.0 doesn't build on SunOS

2017-02-22 Thread Alexander Naumov
Update of bug #50089 (project screen): Open/Closed:Open => Closed ___ Reply to this item at: ___

[screen-devel] [bug #50089] Screen 4.5.0 doesn't build on SunOS

2017-02-13 Thread Alexander Naumov
Update of bug #50089 (project screen): Status:None => Ready For Test Release: 5.0.0 => 4.5.0 Fixed Release:None => 4.5.1 Planned Release:

[screen-devel] [bug #50089] Screen 4.5.0 doesn't build on SunOS

2017-02-02 Thread anonymous
Additional Item Attachment, bug #50089 (project screen): File name: screen_4.5.0_coredump.txt Size:2 KB ___ Reply to this item at: ___ Message

Re: [screen-devel] [bug #50089] Screen 4.5.0 doesn't build on SunOS

2017-01-30 Thread Alex Naumov
On Thu, Jan 19, 2017 at 2:04 PM, Axel Beckert wrote: > > Of course it would be nice if this would be solved in a cleaner way for an > official fix. > Like this? #ifndef PATH_MAX # ifdef _POSIX_PATH_MAX # define PATH_MAX _POSIX_PATH_MAX # endif #endif Does GNU/Hurd know

[screen-devel] [bug #50089] Screen 4.5.0 doesn't build on SunOS

2017-01-19 Thread Axel Beckert
Follow-up Comment #1, bug #50089 (project screen): The same issue shows up in GNU Hurd, which also doesn't know PATH_MAX because it doesn't seem to need it, i.e. doesn't have a limit for a path length. In Debian we apply this clumsy patch for GNU Hurd which sets an arbitrary limit if none is