Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Olivier BATARD <obatard@icloud.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs prof compile error on debian squeeze.
Date: Thu, 11 Apr 2013 11:41:15 -0500	[thread overview]
Message-ID: <5166E7AB.6070306@redhat.com> (raw)
In-Reply-To: <65A4DA2F-1478-4429-816F-2B60A6193764@icloud.com>

On 4/11/13 11:26 AM, Olivier BATARD wrote:
> 
> I agree with you. Debian package are out of date. I've chosen to
> change distribution, I switched to ArchLinux and everything is fine.
> And finally I don't like the way debian works anymore.
> 
> Thanks for your help.

FWIW, I did just send patches to the list to work w/ older
util-linux blkid, with the caveat that they may fail to detect
an SSD on an older, buggy blkid.

-Eric
 
> 
> Le 11 avr. 2013 à 03:41, Eric Sandeen <sandeen@redhat.com> a écrit :
> 
>> On 4/10/13 7:28 PM, Mitch Harder wrote:
>>> We had a discussion on this topic in another thread.
>>>
>>> I'd be happy to be corrected, but I think the conclusion was that you
>>> probably need to be on a really  modern version of Linux to work with
>>> the latest version of btrfs-progs that is in the kernel git
>>> repository.
>>>
>>> The mkfs.btrfs version in the kernel git tree won't even work
>>> correctly on a kernel <= 3.7, and only partially works on the 3.8
>>> kernel.
>>
>> Well, that needs to be fixed too, IMHO, and I think that's the plan?
>>
>> For userspace, if we used autoconf, we could pretty easily turn off the
>> ssd code in btrfs for older systems.
>>
>> We could probably use the older blkid interfaces to do the same thing
>> as well, but nobody's made it a priority yet.
>>
>> -Eric
>>
>>> On 4/10/13, Wang Shilong <wangshilong1991@gmail.com> wrote:
>>>> Hello,
>>>> Maybe this url will help you.
>>>>
>>>> https://btrfs.wiki.kernel.org/index.php/Btrfs_source_repositories
>>>>
>>>> Thanks,
>>>> Wang
>>>>> Hello,
>>>>>
>>>>> I'm trying to build btrfs-prog on debian squeeze but when I'm trying to
>>>>> use make, I have an error :
>>>>>
>>>>>
>>>>> pc@debian:~/b/btrfs-progs$ make
>>>>>   [LD]     mkfs.btrfs
>>>>> mkfs.o: In function `is_ssd':
>>>>> /home/pc/b/btrfs-progs/mkfs.c:1234: undefined reference to
>>>>> `blkid_probe_get_wholedisk_devno'
>>>>> collect2: ld returned 1 exit status
>>>>> make: *** [mkfs.btrfs] Erreur 1
>>>>>
>>>>>
>>>>> After a few searches over the internet, it seems that my blkid library is
>>>>> out of date. How can I compile btrfs prog on debian squeeze ?
>>>>>
>>>>> Thanks !
>>>>>
>>>>>
>>>>> Olivier.--
>>>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>>>> the body of a message to majordomo@vger.kernel.org
>>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>>
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>>
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


      reply	other threads:[~2013-04-11 16:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-09 19:31 btrfs prof compile error on debian squeeze Olivier BATARD
2013-04-10 11:41 ` Wang Shilong
2013-04-11  0:28   ` Mitch Harder
2013-04-11  1:41     ` Eric Sandeen
2013-04-11 16:26       ` Olivier BATARD
2013-04-11 16:41         ` Eric Sandeen [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=5166E7AB.6070306@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=obatard@icloud.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