public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug remote/30927] gdbsupport/configure does not detect Illumos socketpair
Date: Mon, 02 Oct 2023 22:51:02 +0000	[thread overview]
Message-ID: <bug-30927-4717-BW7mme5Lfo@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30927-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30927

--- Comment #3 from Tom Tromey <tromey at sourceware dot org> ---
(In reply to Paul Floyd from comment #2)
> The patch looks OK for gdbsupport/common.m4 but I don't think that
> gdb/configure.ac needs changing.
> 
> With the test for socketpait in libsocket removed gdb/config.h doesn't get
> HAVE_SOCKETPAIR set which is used by gdb/ser-pipe.c

This is surprising because the patch just moves the check
from gdb to common.m4, which is used by both programs.
Did you do a clean rebuild?  Maybe look in gdb/config.log
to see what has gone wrong.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-10-02 22:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01  9:36 [Bug remote/30927] New: " pjfloyd at wanadoo dot fr
2023-10-01 15:16 ` [Bug remote/30927] " tromey at sourceware dot org
2023-10-02 19:05 ` pjfloyd at wanadoo dot fr
2023-10-02 22:51 ` tromey at sourceware dot org [this message]
2023-10-03  6:38 ` pjfloyd at wanadoo dot fr
2023-10-04 12:06 ` tromey at sourceware dot org
2023-10-04 12:07 ` tromey at sourceware dot org
2023-10-05  8:46 ` pjfloyd at wanadoo dot fr
2023-10-06 15:51 ` tromey at sourceware dot org
2023-10-06 15:51 ` tromey at sourceware dot org
2023-10-13  0:22 ` cvs-commit at gcc dot gnu.org
2023-10-13  0:44 ` cvs-commit at gcc dot gnu.org
2023-10-13  0:45 ` tromey at sourceware dot org

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=bug-30927-4717-BW7mme5Lfo@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).