>> That's not the real error. >> >> There was an error when the configure script ran earlier, but it >> didn't abort, and kept going. >> >> Run the configure script again, and search for errors related to >> executing "courierauthconfig".
KOn 17.09.14 08:30, Christopher Rüprich wrote: >I still have the config.log. I ran "cat -n config.log|grep -C4 error" ( >http://pastebin.com/G21itVS9 ) and "cat -n config.log|grep -C4 failed" ( >http://pastebin.com/iyvFfJhY ), but the results don't tell me much. re-run the configure script as Sam said. extracting error lines from config.log rarely helps, because the errors usually appear on other lines. (btw, using "grep -n -C4" would be more effective. see http://www.smallo.ruhr.de/award.html) -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I'm not interested in your website anymore. If you need cookies, bake them yourself. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
