From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001595]: DirectFB detects host installed /usr/bin/libvncserver-config instead checking only in staging dir
Date: Fri, 16 Nov 2007 08:11:20 -0800 [thread overview]
Message-ID: <5f69f3b20ca49daf86b0702b0785537d@busybox.net> (raw)
The following issue has been CLOSED
======================================================================
http://busybox.net/bugs/view.php?id=1595
======================================================================
Reported By: vanokuten
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1595
Category: Architecture Specific
Reproducibility: always
Severity: minor
Priority: normal
Status: closed
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 11-16-2007 05:08 PST
Last Modified: 11-16-2007 08:11 PST
======================================================================
Summary: DirectFB detects host installed
/usr/bin/libvncserver-config instead checking only in staging dir
Description:
DirectFB incorrectly detects libvncserver support from host PC instead
checking only in staging dir
./configure
...
checking for libvncserver-config... /usr/bin/libvncserver-config
...
Building Core Systems:
Linux FBDev support yes
X11 support no
OSX support no
SDL support no
VNC support yes
...
make
...
/opt/buildroot/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-gcc -Os
-pipe -I/opt/buildroot/build_avr32/staging_dir/usr/include
-I/opt/buildroot/build_avr32/staging_dir/include -msoft-float -shared
.libs/vncinput.o -Wl,--rpath
-Wl,/opt/buildroot/build_avr32/DirectFB-1.0.1/src/.libs -L/usr/lib
-lvncserver -lvncclient -lnsl -lz -ljpeg ../../src/.libs/libdirectfb.so
-L/opt/buildroot/build_avr32/DirectFB-1.0.1/lib/fusion/.libs
-L/opt/buildroot/build_avr32/DirectFB-1.0.1/lib/direct/.libs -ldl
-lpthread -msoft-float -Wl,-soname -Wl,libdirectfb_vncinput.so -o
.libs/libdirectfb_vncinput.so
/opt/buildroot/build_avr32/staging_dir/usr/bin/avr32-linux-uclibc-ld:
cannot find -lvncserver
collect2: ld returned 1 exit status
======================================================================
----------------------------------------------------------------------
vanokuten - 11-16-07 08:11
----------------------------------------------------------------------
fixed in 20441
Issue History
Date Modified Username Field Change
======================================================================
11-16-07 05:08 vanokuten New Issue
11-16-07 05:08 vanokuten Status new => assigned
11-16-07 05:08 vanokuten Assigned To => buildroot
11-16-07 08:11 vanokuten Status assigned => closed
11-16-07 08:11 vanokuten Note Added: 0002939
======================================================================
next reply other threads:[~2007-11-16 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 16:11 bugs at busybox.net [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-11-16 13:08 [Buildroot] [buildroot 0001595]: DirectFB detects host installed /usr/bin/libvncserver-config instead checking only in staging dir bugs 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=5f69f3b20ca49daf86b0702b0785537d@busybox.net \
--to=bugs@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