All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Hallo32 <Hallo32@gmx.net>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs-v4.12: cross compiling
Date: Mon, 14 Aug 2017 21:10:11 +0800	[thread overview]
Message-ID: <3a460074-3cbb-a941-306a-bb6af9f48f1e@gmx.com> (raw)
In-Reply-To: <e8d480c6-758e-0e7d-a024-e9d12d7bf852@gmx.net>



On 2017年08月14日 20:17, Hallo32 wrote:
> Hello at all,
> 
> I'm new at this list. If the mail is not in line with your standards 
> please inform me.
> 
> Since versions 4.12 btrfs-progs is complicated to cross compile for 
> other systems.
> The problem is, that this version includes mktables, which needs to be 
> compiled for the host system and executed there for the creation of 
> tables.c.
> 
> Are there any changes planed for the next version of btrfs-progs to make 
> the cross compiling as simple as in the past? A included tables.c for 
> example?

Including tables.c seems quite crazy for me.
Just check how many lines tables.c has.

If we screw up any number of it, RAID6 is screwed up and we will never 
find the bug by reviewing the such meaningless numbers.

We could enhance the makefile to use host-cc to compile and execute mktable.
But it may make the makefile more complicated just for one file.
(Well, I just don't want to screw traditional Makefile/configure any more)

Another solution is to generate tables.c using scripts, other binary 
executable.
I'll try to port mktable to bash or python, which should solve the 
problem withouth further complicating makefile.
(And maybe I can update kernel too, but kernel has its host-cc and 
cross-cc already distinguished well, so it may not help much)

Thanks,
Qu

> 
> Best regards
> -- 
> 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

      parent reply	other threads:[~2017-08-14 13:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 12:17 btrfs-progs-v4.12: cross compiling Hallo32
2017-08-14 13:06 ` David Sterba
2017-08-14 13:17   ` Qu Wenruo
2017-08-14 14:03     ` David Sterba
2017-08-14 14:14       ` Qu Wenruo
2017-08-14 15:10         ` David Sterba
2017-08-14 18:57           ` Goffredo Baroncelli
2017-08-14 23:39             ` Qu Wenruo
2017-08-15 12:44               ` Hallo32
2017-08-15 12:48                 ` David Sterba
2017-08-15 17:28                   ` Eric Sandeen
2017-08-15 18:14                     ` Eric Sandeen
2017-08-16  0:13                     ` Qu Wenruo
2017-08-15 19:27           ` Jeff Mahoney
2017-08-14 13:10 ` Qu Wenruo [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=3a460074-3cbb-a941-306a-bb6af9f48f1e@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=Hallo32@gmx.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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.