From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libfuse: not available for static builds
Date: Sun, 14 Apr 2013 23:12:11 +0200 [thread overview]
Message-ID: <87sj2solzo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <512CE22D.8070601@zacarias.com.ar> (Gustavo Zacarias's message of "Tue, 26 Feb 2013 13:26:21 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> On 02/26/2013 01:22 PM, Peter Korsgaard wrote:
>> Huh, that build error is just because of the hardcoded target install
>> step (why don't we just use make install)?
>>
>> Did you mean another build error?
Gustavo> Yes, but it leads to other errors if we avoid copying
Gustavo> libfuse*.so If you've just got libfuse.a in staging and
Gustavo> fuse-using programs link/use it it breaks anyway because
Gustavo> libfuse hardcodes dlopen. We'd just be translating the build
Gustavo> failure to exfat, unionfs and so on... Regards.
Ok, committed - Thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-04-14 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 10:16 [Buildroot] [PATCH] libfuse: not available for static builds Gustavo Zacarias
2013-02-26 16:22 ` Peter Korsgaard
2013-02-26 16:26 ` Gustavo Zacarias
2013-04-14 21:12 ` Peter Korsgaard [this message]
2013-04-13 18:17 ` Thomas Petazzoni
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=87sj2solzo.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 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.