public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ams at gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/21823] New: MAXPATHLEN usage in [gcc]/fixincludes Date: Mon, 30 May 2005 15:10:00 -0000 [thread overview] Message-ID: <20050530150903.21823.ams@gnu.org> (raw) The way MAXPATHLEN is used in fixincludes (server.c and fixincl.c) is wrong, instead of defining a bogus value on platforms that do not have MAXPATHLEN defined (i.e. GNU) one should try and use getcwd as follows: char *dir = getcwd (NULL, 0); instead of passing a buffer and a size. This will only work on systems that use the GNU C Library. -- Summary: MAXPATHLEN usage in [gcc]/fixincludes Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ams at gnu dot org CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: i686-pc-gnu0.3 GCC host triplet: i686-pc-gnu0.3 GCC target triplet: i686-pc-gnu0.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21823
next reply other threads:[~2005-05-30 15:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-30 15:10 ams at gnu dot org [this message] 2005-05-30 15:10 ` [Bug other/21823] " pinskia at gcc dot gnu dot org 2005-05-30 15:17 ` pinskia at gcc dot gnu dot org 2005-06-19 14:01 ` pinskia at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050530150903.21823.ams@gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).