From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15634] fluidsynths refers to missing libgomp.so.1
Date: Sun, 25 Jun 2023 15:39:52 +0000 [thread overview]
Message-ID: <bug-15634-163-NLzGqIvHJm@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15634-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15634
Vincent Fazio <vfazio@xes-inc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned@buildroot.uclibc |vfazio@xes-inc.com
|.org |
Status|NEW |ASSIGNED
--- Comment #5 from Vincent Fazio <vfazio@xes-inc.com> ---
I lied, the "easiest" option is probably to use `BR2_TOOLCHAIN_EXTRA_LIBS` to
copy in libgomp.
I've pushed a PR to bootlin to fix one of the root causes:
https://github.com/bootlin/toolchains-builder/pull/61
I'm also working on a series of patches on
https://gitlab.com/vfazio/buildroot/-/commits/vfazio-openmp-packages that will:
1: update known packages that use OpenMP to be sensitive to this issue
2. fix the flags for the bootlin toolchains
3. make our toolchain "supported libraries" check a bit more robust to catch
the reverse condition of "support available but not flagged"
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-25 15:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 16:30 [Buildroot] [Bug 15634] New: fluidsynths refers to missing libgomp.so.1 bugzilla
2023-06-18 19:36 ` [Buildroot] [Bug 15634] " bugzilla
2023-06-18 19:47 ` bugzilla
2023-06-19 12:13 ` bugzilla
2023-06-19 16:05 ` bugzilla
2023-06-25 15:39 ` bugzilla [this message]
2023-08-31 14:43 ` bugzilla
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-15634-163-NLzGqIvHJm@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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