--
S pozdravem ...
--
Miroslav Kokrda
Team Leader
ICZ a.s.
mailto:miroslav.kok...@i.cz
http://www.i.cz
-
Prosím, neposílejte mi přílohy ve formátech .doc nebo .ppt
Daleko lepší pro Vás i Vaše okolí je používat volně šiřitelný
kancelářský balík OpenOffice (http://www.openoffice.cz), jehož
dokumen
On 10/12/2012 05:00, matt wrote:
I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
"USE_GCC=any" to a port's Makefile, and then committed that change to
various ports. In most (but not all!) cases this will tell the port
"build with gcc instead of clang" (*) .
Why not U
Hi porters,
I'm just wondering if it is possible to have my own ports directory that is
outside the regular ports tree (e.g. if I want a older/newer version of a
port), and when I make something, this directory tree is checked for content to
override what is in the "official" ports tree?
On Op
Это текстовая часть сообщения.
Необходима для пользователей устаревших почтовых клиентов
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freeb
On 10/12/12 00:54, Claude Buisson wrote:
On 10/12/2012 05:00, matt wrote:
I have made changes to ports/Mk/bsd.gcc.mk that allow the addition of
"USE_GCC=any" to a port's Makefile, and then committed that change to
various ports. In most (but not all!) cases this will tell the port
"build wit