From: Alexander Varnin <fenixk19@mail.ru>
To: buildroot@busybox.net
Subject: [Buildroot] Problem building curlftpfs within buildroot
Date: Tue, 30 Oct 2012 16:51:12 +0400 [thread overview]
Message-ID: <508FCD40.4050208@mail.ru> (raw)
In-Reply-To: <1351600599.12245.0.camel@localhost>
30.10.2012 16:36, Alexander Khryukin ?????:
> ? ??., 30/10/2012 ? 13:24 +0100, Richard Braun ?????:
>> On Tue, Oct 30, 2012 at 02:52:08PM +0400, Alexander Varnin wrote:
>>> Hello. I'm trying to build self-made package curlftpfs within
>>> buildroot. It is simple autotools based package. Build fails with
>> Please use my patch as a basis for your work :
>>
>> http://lists.busybox.net/pipermail/buildroot/2012-July/056319.html
>>
>
> patch it's ok but not helpful to solve linkage issue
>
Yes, i understand it.
I'll add fix to patch, after i apply it.
prev parent reply other threads:[~2012-10-30 12:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 10:52 [Buildroot] Problem building curlftpfs within buildroot Alexander Varnin
2012-10-30 11:03 ` Thomas Petazzoni
2012-10-30 11:25 ` Alexander Varnin
2012-10-30 11:26 ` Alexander Khryukin
2012-10-30 11:34 ` Alexander Khryukin
2012-10-30 12:24 ` Richard Braun
2012-10-30 12:33 ` Alexander Varnin
2012-10-30 12:36 ` Alexander Khryukin
2012-10-30 12:51 ` Alexander Varnin [this message]
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=508FCD40.4050208@mail.ru \
--to=fenixk19@mail.ru \
--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