From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] profiles/default/linux: set gl_cv_type_time_t_bits_macro=no
Date: Sat, 18 Dec 2021 10:54:09 -0500 [thread overview]
Message-ID: <CAJ0EP40HJJKk=MjqdoYQi3YMFEh0VMT6PmZ7tMQSym4twJrjjw@mail.gmail.com> (raw)
In-Reply-To: <4291a56ee0d08b3bc1d122487adfebdfdb146b80.camel@gentoo.org>
On Sat, Dec 18, 2021 at 10:35 AM James Le Cuirot <chewi@gentoo.org> wrote:
> What will we do about other build systems? I worry they won't have a
> consistent approach for all projects.
We will have to deal with them as we discover them. I don't see a
magic solution for everything.
I suppose we could add a new profile var (eg. TIME_BITS) that ebuild
maintainers could reference to control this for non-autoconf/gnulib
build systems.
Also, if some common build system like meson adds automagic support,
we could override that in meson.eclass.
prev parent reply other threads:[~2021-12-18 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 14:41 [gentoo-dev] [PATCH] profiles/default/linux: set gl_cv_type_time_t_bits_macro=no Mike Gilbert
2021-12-17 19:29 ` Alec Warner
2021-12-18 15:35 ` James Le Cuirot
2021-12-18 15:54 ` Mike Gilbert [this message]
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='CAJ0EP40HJJKk=MjqdoYQi3YMFEh0VMT6PmZ7tMQSym4twJrjjw@mail.gmail.com' \
--to=floppym@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