On Sat, Oct 12, 2013 at 11:58 PM, Eitan Adler <li...@eitanadler.com> wrote:
> On Sat, Oct 12, 2013 at 11:43 AM, Matthias Apitz <g...@unixarea.de> wrote: > > El día Friday, October 11, 2013 a las 06:16:23PM -0500, Matthew D. > Fuller escribió: > > > >> On Fri, Oct 11, 2013 at 09:37:13AM +0200 I heard the voice of > >> Matthias Apitz, and lo! it spake thus: > >> > > >> > I have had to uninstall portconf again to be able to build more ports. > >> > >> Near's I can tell, portconf and bmake just flat out don't get along. > >> With some squirreling around in make.conf, you can make _that_ warning > >> shut up, but you just wind up with a different one for ports that you > >> have portconf stuff for. I stopped investigating at that point :| > > > > Maybe my English is poor, I do not understand your message. Please > > clarify. Thx > > Translation: > bmake and portconf are not compatible. Once you fix the "couldn't read > shell's output" error, there are others. > I've submitted a dirty hack for ports-mgmt/portconf as ports/183104. It works fine on my box. HTH Regards, sunpoet > -- > Eitan Adler > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
