Date: Sat, 10 Sep 2011 02:10:06 -0700 (PDT) From: Jakub Lach <jakub_lach@mailplus.pl> To: freebsd-ports-bugs@freebsd.org Subject: Re: These ports don't compile Message-ID: <1315645806187-4789106.post@n5.nabble.com> In-Reply-To: <CADTnMhq-_pZe5N7EWNaGDzfoX0Q6qU21nx9BaxH6BuS9Qx8Epw@mail.gmail.com> References: <CADTnMhpznMnEhdS2htiye3VvxPdvVOQNODpYjkYU0am9oEa7BQ@mail.gmail.com> <CADTnMhq-_pZe5N7EWNaGDzfoX0Q6qU21nx9BaxH6BuS9Qx8Epw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
1. Get fresh binutils from ports, and make sure it's used, and libtool you are using was compiled with gcc you want to use (e.g. libao problem). 2. Ports are usually tested with base compiler, lately some with clang too. If you think you are competent enough to make them work with non-base compiler, you're welcome to provide patches in PR's (http://www.freebsd.org/send-pr.html). Maintainers of ports are not required to test them with non-base compilers, however they're usually happy to make their ports compliant with newer gcc, after all, more and more people are messing with ports compiler, but it's not officially supported configuration. best regards, - Jakub Lach -- View this message in context: http://freebsd.1045724.n5.nabble.com/These-ports-don-t-compile-tp4786515p4789106.html Sent from the freebsd-ports-bugs mailing list archive at Nabble.com.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1315645806187-4789106.post>