From: bugs at busybox.net <bugs@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [buildroot 0001934]: readline package can't install shared library without headers into target
Date: Tue, 15 Jan 2008 23:24:54 -0800 [thread overview]
Message-ID: <ccc042adcaae44c4e45a08d3401e9115@bugs.uclibc.org> (raw)
The following issue has been SUBMITTED.
======================================================================
http://busybox.net/bugs/view.php?id=1934
======================================================================
Reported By: hmoffatt
Assigned To: buildroot
======================================================================
Project: buildroot
Issue ID: 1934
Category: Shared Library Support
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
======================================================================
Date Submitted: 01-15-2008 23:24 PST
Last Modified: 01-15-2008 23:24 PST
======================================================================
Summary: readline package can't install shared library
without headers into target
Description:
If BR2_READLINE is enabled readline is only installed for the host.
If BR2_PACKAGE_READLINE_TARGET is enabled, both the shared library and
also the header files and info documentation are installed onto the
target.
It would be useful to be able to install just the shared library, so that
it can be used by other applications.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
01-15-08 23:24 hmoffatt New Issue
01-15-08 23:24 hmoffatt Status new => assigned
01-15-08 23:24 hmoffatt Assigned To => buildroot
======================================================================
reply other threads:[~2008-01-16 7:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ccc042adcaae44c4e45a08d3401e9115@bugs.uclibc.org \
--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