2016-10-08 9:12 GMT-05:00 Steve Matzura <[email protected]>: > > Really? I'll have to give it another try as non-root. The first time I > tried, things blew up left and right. Any progress I made was done as > root.
Please do! Running it as root can sometimes hide underlying issues like file rights and etc.. Let us know if you find any issue with the current build system, I'd be happy to fix anything that causes trouble. Romain > On Sat, 8 Oct 2016 01:22:22 -0500, you wrote: > > >2016-10-07 23:28 GMT-05:00 tth <[email protected]>: > >> On 10/08/2016 02:21 AM, Steve Matzura wrote: > >> > >>> 1. Never a good idea to build things as a non-privileged (not root) > >>> user. su to root and try ./configure again. > >> > >> WTF ?!?! > > > >Yeah, I have to concur on this one. It's never a good idea to > >run configure/make as root. Configure scripts, specially, have a lot > >of complex, obscur test code and what not. We've had issues in the > >past with those which made us force our configure script to fail when run > >as root. > > > >Only recently, and only because isolation technologies such as docker made > >it such that it makes sense to run configure as root in these contexts did > >we relax again our configure scripts to allow them to be run as root.. > > > >Romain > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Savonet-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/savonet-users ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
