From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105697] gcc -static-libgcc -static-libstdc++ support is broken by libtool for dri drivers
Date: Thu, 22 Mar 2018 20:12:55 +0000 [thread overview]
Message-ID: <bug-105697-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 988 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105697
Bug ID: 105697
Summary: gcc -static-libgcc -static-libstdc++ support is broken
by libtool for dri drivers
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/radeonsi
Assignee: dri-devel@lists.freedesktop.org
Reporter: sylvain.bertrand@gmail.com
QA Contact: dri-devel@lists.freedesktop.org
When building mesa with gcc -static-libgcc -static-libstdc++ options, I noticed
that
libtool is linking in a weird way the dri drivers (gallium and mesa), hence
making them dependent on the shared libstdc++.
I did work around it by hiding the shared libstdc++ while I was building mesa.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2373 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-03-22 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 20:12 bugzilla-daemon [this message]
2018-04-08 17:13 ` [Bug 105697] gcc -static-libgcc -static-libstdc++ support is broken by libtool for dri drivers bugzilla-daemon
2019-09-25 18:03 ` bugzilla-daemon
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-105697-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.