After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 604493 - gnome-keyring uses MAXPATHLEN unconditionally
gnome-keyring uses MAXPATHLEN unconditionally
Status: RESOLVED FIXED
Product: gnome-keyring
Classification: Core
Component: general
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-12-13 23:21 UTC by Emilio Pozuelo Monfort
Modified: 2010-02-07 19:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Use dynamic allocation rather than MAXPATHLEN buffers (3.85 KB, patch)
2009-12-13 23:21 UTC, Emilio Pozuelo Monfort 		none Details | Review

Description Emilio Pozuelo Monfort 2009-12-13 23:21:14 UTC 
Hi,

gnome-keyring fails to build on GNU/Hurd because it uses MAXPATHLEN unconditionally, which is undefined on Hurd as there's no maximum path limit.

This patch uses dynamic allocation to fix this, please consider accepting it for 2.30.
Comment 1 Emilio Pozuelo Monfort 2009-12-13 23:21:49 UTC 
Created attachment 149660 [details] [review]
Use dynamic allocation rather than MAXPATHLEN buffers
Comment 2 Emilio Pozuelo Monfort 2009-12-21 08:18:06 UTC 
Can somebody have a look at this? Would be nice to get it in for 2.29.4
Comment 3 Stef Walter 2010-02-07 19:00:42 UTC 
Thanks! Committed to master.