linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dennis Lan (dlan)" <dennis.yxun@gmail.com>
To: Arvin Schnell <aschnell@suse.de>
Cc: Wang Shilong <wangsl.fnst@cn.fujitsu.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs: add arg_strtou64 break library btrfs
Date: Tue, 20 May 2014 18:28:23 +0800	[thread overview]
Message-ID: <CAF1ZMEe3pFdvqwSm3dzFSjBYQ8zHRO9Q2ynb1cfC1Tw-WHuYAA@mail.gmail.com> (raw)
In-Reply-To: <20140520102024.GA12133@suse.de>

On Tue, May 20, 2014 at 6:20 PM, Arvin Schnell <aschnell@suse.de> wrote:
> On Tue, May 20, 2014 at 06:15:49PM +0800, Dennis Lan (dlan) wrote:
>> progs # cat btrfs_mini_tst.c
>>  /*
>>   * gcc -o btrfs_mini_tst btrfs_mini_tst.c -lbtrfs
>>   */
>>
>>   char btrfs_read_and_process_send_stream ();
>>  int
>>  main ()
>>  {
>>  return btrfs_read_and_process_send_stream ();
>>  }
>>
>> progs # gcc -o btrfs_mini_tst btrfs_mini_tst.c -lbtrfs
>> /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.2/../../../../lib64/libbtrfs.so:
>> undefined reference to `arg_strtou64'
>> collect2: error: ld returned 1 exit status
>
> Hi,
>
> that problem was already found. A fix can be found here:
>
> http://www.spinics.net/lists/linux-btrfs/msg33434.html
>
> Regards,
>   Arvin
>
> --
> Arvin Schnell, <aschnell@suse.de>
> Senior Software Engineer, Research & Development
> SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
> Maxfeldstraße 5
> 90409 Nürnberg
> Germany


HI arvin:
  oh, indeed, this patch should fix my problem
  thanks for quick response

Lan

      reply	other threads:[~2014-05-20 10:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-20 10:15 btrfs-progs: add arg_strtou64 break library btrfs Dennis Lan (dlan)
2014-05-20 10:20 ` Arvin Schnell
2014-05-20 10:28   ` Dennis Lan (dlan) [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=CAF1ZMEe3pFdvqwSm3dzFSjBYQ8zHRO9Q2ynb1cfC1Tw-WHuYAA@mail.gmail.com \
    --to=dennis.yxun@gmail.com \
    --cc=aschnell@suse.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangsl.fnst@cn.fujitsu.com \
    /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;
as well as URLs for NNTP newsgroup(s).