From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/sandbox:stable-2.x commit in: /
Date: Sat, 5 Aug 2023 04:33:03 +0000 (UTC) [thread overview]
Message-ID: <1691209968.fa7aa29903a6dc57fdb5dd3b6b8c4c5a7ad7126f.sam@gentoo> (raw)
commit: fa7aa29903a6dc57fdb5dd3b6b8c4c5a7ad7126f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 21 15:05:56 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Aug 5 04:32:48 2023 +0000
URL: https://gitweb.gentoo.org/proj/sandbox.git/commit/?id=fa7aa299
configure.ac: fix whitespace
Signed-off-by: Sam James <sam <AT> gentoo.org>
(cherry picked from commit 62ce93feaa51f9e3a490ef522e0bad91f666ebe1)
configure.ac | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/configure.ac b/configure.ac
index 847bc4c..ba878ef 100644
--- a/configure.ac
+++ b/configure.ac
@@ -343,7 +343,7 @@ if test x"$have_rtld_next" = xyes ; then
AC_DEFINE([HAVE_RTLD_NEXT], [1], [Have RTLD_NEXT enabled libc])
fi
-dnl we need to handle symbols differently based upon their version,
+dnl we need to handle symbols differently based upon their version,
dnl but we have to know which symbols the libc supports first
AC_MSG_CHECKING([libc path])
echo "int main(void) { return 0; }" > libctest.c
@@ -381,7 +381,7 @@ AC_DEFINE_UNQUOTED([LIBC_PATH], ["$LIBC_PATH"], [Full path to the libc])
AC_MSG_RESULT([$LIBC_PATH])
AC_SUBST([LIBC_PATH])
-dnl when intercepting libc calls, we have to know the name of the
+dnl when intercepting libc calls, we have to know the name of the
dnl libc to load and search with dl*() calls
AC_MSG_CHECKING([libc version])
dnl the sed script at the end here looks funny but it's ok ...
next reply other threads:[~2023-08-05 4:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 4:33 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-08 2:12 [gentoo-commits] proj/sandbox:stable-2.x commit in: / Mike Gilbert
2024-12-22 19:19 Mike Gilbert
2024-12-22 3:49 Mike Gilbert
2024-11-04 19:27 Mike Gilbert
2024-11-04 19:15 Mike Gilbert
2024-06-27 15:25 Mike Gilbert
2023-08-06 0:49 Mike Gilbert
2023-08-05 4:33 Sam James
2023-07-17 13:57 Mike Gilbert
2023-07-10 15:54 Mike Gilbert
2023-07-08 3:08 Mike Gilbert
2023-07-01 23:54 Mike Gilbert
2023-06-30 16:57 Mike Gilbert
2023-06-23 17:25 Mike Gilbert
2023-06-21 14:48 Mike Gilbert
2023-06-13 18:35 Mike Gilbert
2023-05-12 1:39 Sam James
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=1691209968.fa7aa29903a6dc57fdb5dd3b6b8c4c5a7ad7126f.sam@gentoo \
--to=sam@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