Sorry for the confusion; that was a typo in my e-mail trying to copy and
paste from my log; every time I've run that ./configure I did actually get
the leading slash in there:
[build@lustre-mgs lustre-release]$ history | grep configure
70 ./configure
--with-linux=/home/build/kernel/rpmbuild/BUILD/kernel-3.10.0_229.4.2.el7.centos_lustre.x86_64/
72 ./configure
--with-linux=/home/build/kernel/rpmbuild/BUILD/kernel-3.10.0_229.4.2.el7.centos_lustre.x86_64/
97 ./configure
--with-linux=/home/build/kernel/rpmbuild/BUILD/kernel-3.10.0_229.4.2.el7.centos_lustre.x86_64/
122 history | grep configure
[build@lustre-mgs lustre-release]$
I've tried a few "make clean" and retry attempts and I reach the same end;
the make completes with no errors, but "make rpms" fails with that line 144
error.
I looked at the page Richard sent me and I don't see any material changes
from section 30.2.2 on in the administrator's guide; there's a few extra
packages in there that aren't mentioned in my printing of the Lustre 2.x
operations manual ... but I never hit any errors previous in the build
process; the kernel builds fine ... just trying to build the Lustre RPMs
fails ... final step ... I feel like anything I would have made a hash of
so grievously would have caused fatal errors earlier in the process, no?
Best,
Sean
On Fri, Jun 5, 2015 at 3:49 PM, Stephen Champion <schamp(a)sgi.com> wrote:
On 6/5/2015 12:41 PM, Sean Caron wrote:
> I've been following the build directions explicitly from section 30.2.2
> on only correcting for differences between CentOS 7 and RHEL 7 ...
> everything built clean until now, as far as I can tell. At what point in
> the build process would I have gone awry for that to happen?
>
At configure.
Right at momentary freeze as my mail client was sending, I saw the problem.
./configure
>
--with-linux=home/build/kernel/rpmbuild/BUILD/kernel-3.10.0_229.4.2.el7.centos_lustre.x86_64/
>
the leading slash is missing.