From: Matt Rice <ratmice@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/7] Make the gdb.objc tests compile
Date: Tue, 18 Nov 2025 01:12:24 +0000 [thread overview]
Message-ID: <CACTLOFopatMDf1jfgTmhY+X_Amvf8+e=OoRpKYwBBW3diKjq=g@mail.gmail.com> (raw)
In-Reply-To: <87o6p088oe.fsf@tromey.com>
On Tue, Nov 18, 2025 at 12:51 AM Tom Tromey <tom@tromey.com> wrote:
>
> Matt> I guess at the time all this stuff broke I never felt that was an
> Matt> option (and still feel it is terrible, yet better than the status
> Matt> quo)... Since it is likely *most* people running the testsuite
> Matt> won't have gnustep-base installed, nor all its shell script
> Matt> environment variables since it tends to install its header files
> Matt> in weird locations.
>
> Matt> I don't see all those -I and -L flags though, so this seems likely
> Matt> it depends upon a certain installation/configuration of
> Matt> gnustep-base which installs stuff in places the compiler will pick
> Matt> them up (likely a distro's specific configuration which isn't the
> Matt> default to conform to distribution specific installation rules)
>
> Yeah, at least on Fedora, if I "dnf install" the gnustep-base-devel
> package, that is enough.
>
> I personally think it's fine to require gdb developers to install random
> stuff like this, at least if it is pre-packaged.
>
> Anyway if there's a better way to do it, I'm open to that as well.
I guess the only concrete suggestion I'd have is using the
`gnustep-config --base-libs`, and
`gnustep-config --objc-flags`, for the header files/link flags.
The cpp flags aren't really shown in this patch, I think that should
allow it to work for
the case where someone installs gnustep by hand, using the default
configuration as well
as these distro packages.
next prev parent reply other threads:[~2025-11-18 1:13 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 [this message]
2025-12-02 16:20 ` Tom Tromey
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='CACTLOFopatMDf1jfgTmhY+X_Amvf8+e=OoRpKYwBBW3diKjq=g@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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