Hi guys, Did one of you had a little moment to have a look to my previous message?
Regards, Thierry L. -----Message d'origine----- De : lustre-discuss-boun...@lists.lustre.org [mailto:lustre-discuss-boun...@lists.lustre.org] De la part de Thierry Lamoureux Envoyé : mercredi 7 janvier 2015 17:15 À : Dilger, Andreas; Kilian Cavalotti Cc : lustre-discuss@lists.lustre.org Objet : Re: [Lustre-discuss] Build lustre 2.6 Client on Debian Wheezy Hi, Thanks for your replies. I tried Kilian's advice and it going further, but it is still not work. You can see the result of make-kpkg here : http://pastebin.com/9E0gDGve It looks like it doesn't found any module to build even if I've correctly configure MODULE_LOC variable according to this example : http://lists.lustre.org/pipermail/lustre-discuss/2014-May/017734.html It would be great if someone have another idea. Thank you, Thierry. -----Message d'origine----- De : Dilger, Andreas [mailto:andreas.dil...@intel.com] Envoyé : mercredi 7 janvier 2015 12:43 À : Kilian Cavalotti; Thierry Lamoureux Cc : lustre-discuss@lists.lustre.org Objet : Re: [Lustre-discuss] Build lustre 2.6 Client on Debian Wheezy On 2015/01/07, 4:33 AM, "Kilian Cavalotti" <kilian.cavalotti.w...@gmail.com> wrote: >Bonjour Thierry, > >> /bin/sh: 1: [: -lt: unexpected operator > >I'm pretty sure that's because in Debian, /bin/sh is linked to dash and >the Lustre build script expects bash. > >You can try to run: ># dpkg-reconfigure dash >choose No to link /bin/sh to bash, and re-run the make-kpkg part. >Hopefully it will work better. > >I suggest to re-run "dpkg-reconfigure dash" afterwards to restore dash >as the default shell. Which script is under discussion here? Definitely we've assumed bash is available, and use bashisms heavily in the testing scripts, since bash is standard on Linux. If there are are a limited number of places where /bin/sh is assumed to be /bin/bash then it makes sense to fix them so that Debian builds work without users having to change their config. Is this just a matter of using "#!/bin/bash" explicitly in these scripts, or should they be changed to conform to POSIX sh behaviour? Cheers, Andreas -- Andreas Dilger Lustre Software Architect Intel High Performance Data Division _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list Lustre-discuss@lists.lustre.org http://lists.lustre.org/mailman/listinfo/lustre-discuss
