[LU-1868] compiling lustre 2.2 client on centos 6.2 error missing ext4 source

• Status: Resolved
• Project: Lustre
• Affects Version/s: Lustre 2.2.0
• Type: Bug
• Priority: Major
• Reporter: Supporto Lustre Jnet2000 (Inactive)
• Assignee: Minh Diep
• Resolution: Not a Bug
• Labels: client

Environment

Centos 6.2 + lustre 2.2 source

• Severity: 3
• Epic: client

Description

I'm trying to compile a patchless client on a centos 6.2 with kernel 2.6.32-220.el6.x86_64, when I run ./configure I receive this error:

checking whether to use ext3 or ext4 source... ext4
checking ext4 source directory...
configure: error: Complete ext4 source must exist.

If you are building using kernel-devel packages then ensure that the
matching kernel-debuginfo-common and kernel-debuginfo-common-<arch>
packages are installed.

The kernel-debuginfo-common package is no longer provide by centos 6. Could you give me information where find the ext4 source?

Thanks in advance.

Comments

[James A Simmons]

What configure options are you using? Try ./configure --disable-server --enable-client

[Brian Murrell (Inactive)]

If you are building using kernel-devel packages then ensure that the
matching kernel-debuginfo-common and kernel-debuginfo-common-<arch>
packages are installed.

We should investigate if this is actually necessary. I can't imagine why it would be.

As for your error, you say you are building a patchless client, so then ext4 source should not be necessary. Lustre's configure should automatically detect if building a server or patchless client is achievable based on the linux-devel location you point to with the "--with-linux" argument, but you can be explicit by giving configure a "--disable-server" option also.

[Peter Jones]

Minh

Could you please help with this one?

Thanks

Peter

[Supporto Lustre Jnet2000 (Inactive)]

Hi Peter,
the problem is solved using explicity the option --disable-server --enable-client .

thanks in advance. This issue is close for me

[Peter Jones]

ok thanks!

[Brian Murrell (Inactive)]

It would be interesting to understand however why configure could not figure the "--disable-server --enable-client" options automagically, as it's supposed to be able to.