From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sandbox:master commit in: libsbutil/gnulib/
Date: Sun, 27 Sep 2015 06:20:53 +0000 (UTC) [thread overview]
Message-ID: <1443310925.e2f06703fe28a3dcc70b847d3b7723bf5c346763.vapier@gentoo> (raw)
commit: e2f06703fe28a3dcc70b847d3b7723bf5c346763
Author: Mike Frysinger <vapier <AT> gentoo <DOT> org>
AuthorDate: Sat Sep 26 23:42:05 2015 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sat Sep 26 23:42:05 2015 +0000
URL: https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=e2f06703
libsbutil: gnulib: mark xgetcwd static inline
Rather than use gnu inline where gcc can create external references
(which we don't provide), just always inline the xgetcwd func. This
fixes building at -O0 optimization levels.
URL: https://bugs.gentoo.org/561342
Reported-by: Pryka <pryka.iluvatar <AT> gmail.com>
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
libsbutil/gnulib/xgetcwd.h | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/libsbutil/gnulib/xgetcwd.h b/libsbutil/gnulib/xgetcwd.h
index 765fab4..fbe0a7c 100644
--- a/libsbutil/gnulib/xgetcwd.h
+++ b/libsbutil/gnulib/xgetcwd.h
@@ -6,16 +6,12 @@
* Licensed under the GPL-2
*/
-_GL_INLINE_HEADER_BEGIN
-
extern char *egetcwd(char *buf, size_t size);
-_GL_INLINE char *xgetcwd(void)
+static inline char *xgetcwd(void)
{
char *ret = egetcwd(NULL, 0);
if (ret == NULL && errno == ENOMEM)
xalloc_die();
return ret;
}
-
-_GL_INLINE_HEADER_END
next reply other threads:[~2015-09-27 6:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-27 6:20 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-20 21:12 [gentoo-commits] proj/sandbox:master commit in: libsbutil/gnulib/ Mike Frysinger
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=1443310925.e2f06703fe28a3dcc70b847d3b7723bf5c346763.vapier@gentoo \
--to=vapier@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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: link
Be 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