All of lore.kernel.org
 help / color / mirror / Atom feed
From: psykose <alice@ayaya.dev>
To: linux-bluetooth@vger.kernel.org
Cc: alice@ayaya.dev
Subject: [PATCH BlueZ 1/3] build: set _FILE_OFFSET_BITS and _TIME_BITS to 64 universally
Date: Thu, 11 May 2023 02:22:50 +0200	[thread overview]
Message-ID: <20230511002252.30868-1-alice@ayaya.dev> (raw)

these are required to make glibc set off_t and time_t to 64-bit wide
types on 32-bit platforms, for large-file-support and 2k38 proofing.

Signed-off-by: psykose <alice@ayaya.dev>
---
 Makefile.am    | 1 +
 Makefile.obexd | 1 -
 2 files changed, 1 insertion(+), 1 deletion(-)

diff --git a/Makefile.am b/Makefile.am
index 48f0cefa7..97825a720 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -27,6 +27,7 @@ pkginclude_HEADERS =
 AM_CFLAGS = $(MISC_CFLAGS) $(WARNING_CFLAGS) $(UDEV_CFLAGS) $(LIBEBOOK_CFLAGS) \
 				$(LIBEDATASERVER_CFLAGS) $(ell_cflags)
 AM_LDFLAGS = $(MISC_LDFLAGS)
+AM_CPPFLAGS += -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64
 
 confdir = $(sysconfdir)/bluetooth
 statedir = $(localstatedir)/lib/bluetooth
diff --git a/Makefile.obexd b/Makefile.obexd
index 5d1a4ff65..f4abbb3e5 100644
--- a/Makefile.obexd
+++ b/Makefile.obexd
@@ -91,7 +91,6 @@ obexd_src_obexd_LDFLAGS = $(AM_LDFLAGS) -Wl,--export-dynamic
 obexd_src_obexd_CPPFLAGS = $(AM_CPPFLAGS) $(GLIB_CFLAGS) $(DBUS_CFLAGS) \
 				$(ICAL_CFLAGS) -DOBEX_PLUGIN_BUILTIN \
 				-DPLUGINDIR=\""$(obex_plugindir)"\" \
-				-D_FILE_OFFSET_BITS=64 \
 				-I$(builddir)/lib -I$(builddir)/obexd/src
 
 obexd_src_obexd_CFLAGS = $(AM_CFLAGS) -fPIC
-- 
2.40.1


             reply	other threads:[~2023-05-11  0:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  0:22 psykose [this message]
2023-05-11  0:22 ` [PATCH BlueZ 2/3] client/player: use long long for off_t print psykose
2023-05-15 19:17   ` Luiz Augusto von Dentz
2023-05-11  0:22 ` [PATCH BlueZ 3/3] tools/parser: use long long for time_t print psykose
2023-05-11  1:42 ` [BlueZ,1/3] build: set _FILE_OFFSET_BITS and _TIME_BITS to 64 universally bluez.test.bot
2023-05-11  2:14   ` alice

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=20230511002252.30868-1-alice@ayaya.dev \
    --to=alice@ayaya.dev \
    --cc=linux-bluetooth@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.