From: Simon Marchi <simark@simark.ca>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Unify Solaris procfs and largefile handling
Date: Tue, 28 Jul 2020 10:17:22 -0400 [thread overview]
Message-ID: <5aae580e-ab2e-f008-91c6-f3b1c1f757b7@simark.ca> (raw)
In-Reply-To: <yddime74ujs.fsf@CeBiTec.Uni-Bielefeld.DE>
On 2020-07-28 9:51 a.m., Rainer Orth wrote:
> Unfortunately not: <sys/procfs.h> is sometimes used in code shared with
> non-Solaris systems, none of which have <procfs.h>. So we'd have to
> conditionalize on HAVE_PROCFS_H vs. HAVE_SYS_PROCFS_H.
>
> And on older Solaris 11.3, even when using the new procfs interface,
> <sys/procfs.h> errors out when largefile support is enabled.
>
> As I said: it's a royal mess ;-(
>
> Rainer
Ok, I see.
The only part I'm not sure about is the part that adds --enable-gdb to all configure
files. For example we now have this in bfd's configure:
$ ./binutils/configure --help | grep gdb
--enable-gdb[=ARG] build gdb [ARG={yes,no}]
I understand that you want to catch whether the user enabled or disabled building GDB
with --enable-gdb or --disable-gdb, but the result is a bit weird. Is there a way not
to include it in the --help?
Ideally, the top-level configure system would be able to tell which modules are enabled.
I don't know much about it, maybe there's a way.
In your patch, can
: ${enable_largefile="no"}
become just
enable_largefile="no"
?
Simon
next prev parent reply other threads:[~2020-07-28 14:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 15:15 Rainer Orth
2020-07-01 12:46 ` Nick Clifton
2020-07-09 10:50 ` Rainer Orth
2020-07-20 11:28 ` Rainer Orth
2020-07-28 13:03 ` Rainer Orth
2020-07-28 13:47 ` Simon Marchi
2020-07-28 13:51 ` Rainer Orth
2020-07-28 14:17 ` Simon Marchi [this message]
2020-07-29 11:19 ` Rainer Orth
2020-07-29 19:55 ` Simon Marchi
2020-07-30 9:17 ` Rainer Orth
2020-07-30 12:43 ` Simon Marchi
2020-07-30 13:49 ` Rainer Orth
2020-08-07 15:12 ` Joel Brobecker
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=5aae580e-ab2e-f008-91c6-f3b1c1f757b7@simark.ca \
--to=simark@simark.ca \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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