From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7B86F385DDC2; Mon, 10 Jun 2024 21:23:26 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7B86F385DDC2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1718054606; bh=hu0FQXwZBeJnk8IbYHM1kTzGeEIy41X6LfGdhbRly5Q=; h=From:To:Subject:Date:In-Reply-To:References:From; b=MyoUajM53AGBmkny6nm0mpV1TkeuzoFlVTB7JGm7f09Gj3jxNhIBPiX+kve7HKW3i jMdXXLlWNSQQdumFTxn97aBMm+H5ZtgzHffFupY2QzEy3nv0ZSN44SX3PsIP7H7kwo S8+abB0rYTBo0LJsC70/lsV6BTJ+PuwdUYJM5QZo= From: "vries at gcc dot gnu.org" To: gdb-prs@sourceware.org Subject: [Bug build/31875] [gdb/build, python] gdb requires long long, while python-internal.h contains support for !HAVE_LONG_LONG Date: Mon, 10 Jun 2024 21:23:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: build X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: vries at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D31875 --- Comment #2 from Tom de Vries --- (In reply to Tom Tromey from comment #1) > Without looking at the older python configury, I guess > it's possible in theory that the platform compiler has > long long but somehow python was built without it? I suppose it's possible, indeed, but I'm not sure either whether that situa= tion is properly supported in gdb now. That is, if python doesn't define HAVE_LONG_LONG in pyport.h, but config.h does, I think it's still defined in python files, forcing the use of PY_LONG_LONG in python-internal.h, which will be undefined, which then shou= ld cause a compilation failure. Either way, the situation looks like an exception, so even if it would work somehow, I'm not sure it's worth bothering with. --=20 You are receiving this mail because: You are on the CC list for the bug.=