From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 11686] New: fbdev_drv.so: undefined symbol: shadowUpdatePackedWeak, xinit: giving up
Date: Fri, 22 Feb 2019 08:35:35 +0000 [thread overview]
Message-ID: <bug-11686-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=11686
Bug ID: 11686
Summary: fbdev_drv.so: undefined symbol:
shadowUpdatePackedWeak, xinit: giving up
Product: buildroot
Version: 2018.11.2
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: pete.luuri at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
fbdev_drv.so: undefined symbol: shadowUpdatePackedWeak, xinit: giving up
raspberrypi3_defconfig
Cant Startx
Bug reported https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900613
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2019-02-22 8:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-22 8:35 bugzilla at busybox.net [this message]
2019-02-22 10:33 ` [Buildroot] [Bug 11686] fbdev_drv.so: undefined symbol: shadowUpdatePackedWeak, xinit: giving up bugzilla at busybox.net
2019-08-21 15:55 ` bugzilla at busybox.net
2019-08-21 20:54 ` bugzilla at busybox.net
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-11686-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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