From: Mark Barton <mbarton98@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 57028@debbugs.gnu.org
Subject: bug#57028: 29.0.50; Build error with configure when brew installed 12.1 libgccjit on macos
Date: Sun, 7 Aug 2022 09:55:10 -0700 [thread overview]
Message-ID: <F24D7B22-BDCC-454F-AC0E-07DD424B4D71@gmail.com> (raw)
In-Reply-To: <83h72oxwtb.fsf@gnu.org>
> On Aug 7, 2022, at 1:49 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Mark Barton <mbarton98@gmail.com>
>> Date: Sun, 7 Aug 2022 00:15:09 -0700
>> Cc: 57028@debbugs.gnu.org
>>
>> On Aug 6, 2022, at 11:29 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> I hope some macOS expert could chime in and clarify the issues enough
>> for us to make the decisions.
>>
>> 57015 has a more precise solution than mine in 57028 since it uses readlink to follow the symbolic link to
>> always get the path to the actual library.
>
> But we then established that 'readlink' cannot be relied upon to exist
> on any random system. So AFAIU, that solution cannot be used.
I forgot about grep having the -m parameter to restrict the number of matches.
Here you see it returns the single directory that would be assigned to the env variable.
(python_training) bartm002@C02FM1E2MD6T ~ % dirname $(brew ls -v libgccjit | grep -m 1 -E 'libgccjit\.(so|dylib)$')
/usr/local/Cellar/libgccjit/12.1.0/lib/gcc/current
Here I show the problem with multiple hits, the dirname result to be assigned is two lines.
(python_training) bartm002@C02FM1E2MD6T ~ % dirname $(brew ls -v libgccjit | grep -m 2 -E 'libgccjit\.(so|dylib)$')
/usr/local/Cellar/libgccjit/12.1.0/lib/gcc/current
/usr/local/Cellar/libgccjit/12.1.0/lib/gcc/12
Either dirname result is good to use, just not both. Adding the "-m 1" to the existing grep would not introduce more dependencies.
prev parent reply other threads:[~2022-08-07 16:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 5:22 bug#57028: 29.0.50; Build error with configure when brew installed 12.1 libgccjit on macos Mark Barton
2022-08-07 6:29 ` Eli Zaretskii
2022-08-07 7:15 ` Mark Barton
2022-08-07 8:49 ` Eli Zaretskii
2022-08-07 16:55 ` Mark Barton [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F24D7B22-BDCC-454F-AC0E-07DD424B4D71@gmail.com \
--to=mbarton98@gmail.com \
--cc=57028@debbugs.gnu.org \
--cc=eliz@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).