From: Tom Tromey <tom@tromey.com>
To: Matt Rice <ratmice@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] Make the gdb.objc tests compile
Date: Tue, 02 Dec 2025 09:20:38 -0700 [thread overview]
Message-ID: <87345sam95.fsf@tromey.com> (raw)
In-Reply-To: <CACTLOFopatMDf1jfgTmhY+X_Amvf8+e=OoRpKYwBBW3diKjq=g@mail.gmail.com> (Matt Rice's message of "Tue, 18 Nov 2025 01:12:24 +0000")
>>>>> "Matt" == Matt Rice <ratmice@gmail.com> writes:
>> Anyway if there's a better way to do it, I'm open to that as well.
Matt> I guess the only concrete suggestion I'd have is using the
Matt> `gnustep-config --base-libs`, and
Matt> `gnustep-config --objc-flags`, for the header files/link flags.
I tried this, and at least on Fedora 40, it doesn't work directly. The
issue is that apparently some RPM-specific stuff snuck into these files.
So, trying to use them gives me an error about RPM_ARCH not being
defined.
Since my patches are a less invasive change, and help the situation
somewhat, I'm going to go ahead and check them in. I'll file a bug
about switching to gnustep-config in the future.
Tom
next prev parent reply other threads:[~2025-12-02 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 1:26 [PATCH 0/7] Objective-C fixes Tom Tromey
2025-11-17 1:27 ` [PATCH 1/7] Reformat gdb.objc tests Tom Tromey
2025-11-17 1:27 ` [PATCH 2/7] Make the gdb.objc tests compile Tom Tromey
2025-11-17 10:09 ` Matt Rice
2025-11-18 0:51 ` Tom Tromey
2025-11-18 1:12 ` Matt Rice
2025-12-02 16:20 ` Tom Tromey [this message]
2025-12-03 15:24 ` Matt Rice
2025-11-17 1:27 ` [PATCH 3/7] Minor fixes to make gdb.objc tests pass Tom Tromey
2025-11-17 1:27 ` [PATCH 4/7] Rename lookup_struct_typedef Tom Tromey
2025-11-17 1:27 ` [PATCH 5/7] Remove a couple Objective-C expression helpers Tom Tromey
2025-11-17 1:27 ` [PATCH 6/7] Avoid crash with "NSString" literals Tom Tromey
2025-11-17 1:27 ` [PATCH 7/7] Rewrite the @selector code Tom Tromey
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=87345sam95.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=ratmice@gmail.com \
/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