Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SLE11 build fixes #125

Closed
wants to merge 3 commits into from
Closed

Conversation

@jeffmahoney
Copy link
Contributor

jeffmahoney commented Apr 27, 2018

This patch set allows btrfs-progs to build without further patching
on a stock SLE11 SP4 install. The major issues were:

  • new dependencies on e2fsprogs 1.42
  • use of -std=gnu90, which gcc 4.3.4 doesn't support
  • use of m4_chomp, introduced in autoconf 2.64.
jeffmahoney added 3 commits Apr 27, 2018
Commit 324d4c1 (btrfs-progs: convert: Add larger device support)
introduced new dependencies on the 64-bit API provided by e2fsprogs.
That API was introduced in v1.42 (along with bigalloc).

This patch maps the following to their equivalents in e2fsprogs < 1.42.
- ext2fs_get_block_bitmap_range2
- ext2fs_inode_data_blocks2
- ext2fs_read_ext_attr2

Since we need to detect and define EXT2_FLAG_64BITS for compatibilty
anyway, it makes sense to use that to detect the older e2fsprogs instead
of defining a new flag ourselves.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Older versions of gcc don't support -std=gnu90 so btrfs-progs won't
build at all on older distros.  We can detect whether the compiler
supports -std=gnu90 and fall back to -std=gnu89 if it doesn't.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Commit 2e1932e (btrfs-progs: build: simplify version tracking)
started m4_chomp to strip the newlines from the version file.  m4_chomp
was introduced in autoconf 2.64 but SLE11 ships with autoconf 2.63.
For purposes of just stripping the newline, m4_flatten is sufficient.

Signed-off-by: Jeff Mahoney <jeffm@suse.com>
Copy link
Contributor Author

jeffmahoney left a comment

Since the previous commit adds a new dependency on autoconf 2.64, this commit is pretty pointless.

@jeffmahoney
Copy link
Contributor Author

jeffmahoney commented Apr 27, 2018

Since we still require autoconf 2.64, the last commit is silly. I'll resubmit without it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.