Re: Two errors each affecting several ports

2012-12-31 Thread Kevin Oberman
On Mon, Dec 31, 2012 at 5:14 PM, Jeffrey Bouquet wrote: > Reply below. > > --- On Mon, 12/31/12, Kevin Oberman wrote: > > From: Kevin Oberman > Subject: Re: Two errors each affecting several ports > To: "Jeffrey Bouquet" > Cc: freebsd-ports@freebsd.org > Date: Monday, December 31, 2012, 3:37 PM

Re: FreeBSD Port: rubygem-chef-0.10.8_1

2012-12-31 Thread Jason Helfman
On Mon, Dec 31, 2012 at 3:48 PM, Jason Helfman wrote: > On Sat, Dec 29, 2012 at 10:37 AM, Jason Helfman wrote: > >> On Sat, Dec 29, 2012 at 8:17 AM, Renaud Chaput wrote: >> >>> Hi Douglas, >>> >>> The updated Chef port for 10.16.4 is ready, I am waiting for PRs >>> #173646 #173647 and #173648 to

Re: Two errors each affecting several ports

2012-12-31 Thread Jeffrey Bouquet
Reply below. --- On Mon, 12/31/12, Kevin Oberman wrote: From: Kevin Oberman Subject: Re: Two errors each affecting several ports To: "Jeffrey Bouquet" Cc: freebsd-ports@freebsd.org Date: Monday, December 31, 2012, 3:37 PM On Mon, Dec 31, 2012 at 3:13 PM, Jeffrey Bouquet wrote: > First error:

Re: FreeBSD Port: rubygem-chef-0.10.8_1

2012-12-31 Thread Jason Helfman
On Sat, Dec 29, 2012 at 10:37 AM, Jason Helfman wrote: > On Sat, Dec 29, 2012 at 8:17 AM, Renaud Chaput wrote: > >> Hi Douglas, >> >> The updated Chef port for 10.16.4 is ready, I am waiting for PRs >> #173646 #173647 and #173648 to submit it, as they are needed >> dependancies. >> >> If you need

Re: Two errors each affecting several ports

2012-12-31 Thread Kevin Oberman
On Mon, Dec 31, 2012 at 3:13 PM, Jeffrey Bouquet wrote: > First error: > configure: error: the pkg-config script could not be found or is too old. > Make sure it is in your PATH or set the PKG_CONFIG environment variable to > the full path to pkg-config > (affects ports such as shared-mime-info,

Two errors each affecting several ports

2012-12-31 Thread Jeffrey Bouquet
First error: configure: error: the pkg-config script could not be found or is too old. Make sure it is in your PATH or set the PKG_CONFIG environment variable to the full path to pkg-config (affects ports such as shared-mime-info, esound...) Second error: /usr/local/bin/ld: main.o: undefined

Re: Cross Compiling of ports Makefiles.

2012-12-31 Thread Michael Vale
-Original Message- From: Simon J. Gerraty Sent: Tuesday, January 01, 2013 4:43 AM To: Michael Vale Cc: freebsd-hack...@freebsd.org ; freebsd-a...@freebsd.org ; freebsd-ports@freebsd.org Subject: Re: Cross Compiling of ports Makefiles. One is to have a MAKEOBJDIRPREFIX like option,

Re: Cross Compiling of ports Makefiles.

2012-12-31 Thread Simon J. Gerraty
>>One is to have a MAKEOBJDIRPREFIX like option, and redefine every >>target’s DESTDIR ${makeobjDESTDIR} before running do-install. Now i’ve >>yet to complete this stage, but I believe this is the way to do it. > >Would it be sufficient to have an INSTALL_PREFIX and/or INSTALL_DESTDIR >so that DES

Re: multimedia/x264 workaround is broken

2012-12-31 Thread Mark Linimon
On Mon, Dec 31, 2012 at 04:12:54PM +, Matthew Rezny wrote: > Is it expected the build logs will be online again at some point? I would like to see them back online, but it's not under my control. mcl ___ freebsd-ports@freebsd.org mailing list http:/

Re: Cross Compiling of ports Makefiles.

2012-12-31 Thread Michael Vale
-Original Message- From: Garrett Cooper Sent: Tuesday, January 01, 2013 2:37 AM To: Michael Vale Cc: freebsd-hack...@freebsd.org ; freebsd-a...@freebsd.org ; freebsd-ports@freebsd.org ; Simon J. Gerraty Subject: Re: Cross Compiling of ports Makefiles. On Mon, Dec 31, 2012 at 6:33 AM

Re: multimedia/x264 workaround is broken

2012-12-31 Thread Matthew Rezny
Is it expected the build logs will be online again at some point? x264 built with Clang works for playback of everything I have tried. I have not yet verified encoding. (Apologies for the top reply. My phone will not allow me to write below.)On 12/26/12 20:29 Mark Linimon wrote: On Wed, Dec 26

Re: Cross Compiling of ports Makefiles.

2012-12-31 Thread Garrett Cooper
On Mon, Dec 31, 2012 at 6:33 AM, Michael Vale wrote: > -Original Message- From: Simon J. Gerraty > Sent: Friday, December 28, 2012 5:00 AM > To: Michael Vale > Cc: freebsd-hack...@freebsd.org ; freebsd-a...@freebsd.org ; > freebsd-ports@freebsd.org > Subject: Re: Cross Compiling of ports M

Re: Cross Compiling of ports Makefiles.

2012-12-31 Thread Michael Vale
-Original Message- From: Simon J. Gerraty Sent: Friday, December 28, 2012 5:00 AM To: Michael Vale Cc: freebsd-hack...@freebsd.org ; freebsd-a...@freebsd.org ; freebsd-ports@freebsd.org Subject: Re: Cross Compiling of ports Makefiles. Doing the same thing could also prevent the nee

Re: Citrix

2012-12-31 Thread Mark Felder
On Sun, 30 Dec 2012 18:55:40 -0800 "jmdennis @dslextreme.com" wrote: > It would be nice to be able to use version 12.1 of the receiver. I > know you have to download it yourself but it expects an old version > which can no longer be found. It would be nice if you would put down > where you can

Re: xfig build failure on amd64 with clang, possibly imake problem?

2012-12-31 Thread Matthias Andree
See as well. ___ 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"

Re: xfig build failure on amd64 with clang, possibly imake problem?

2012-12-31 Thread Matthias Andree
Am 31.12.2012 14:36, schrieb Anton Shterenlikht: > From utis...@gmail.com Mon Dec 31 13:34:27 2012 > > Yes. > > imake doesn't run properly if built with clang; you must build with > GCC/g++. > > Chris > > So is this something for the port maintaner (x11@) > to sort out?

Re: xfig build failure on amd64 with clang, possibly imake problem?

2012-12-31 Thread Anton Shterenlikht
From utis...@gmail.com Mon Dec 31 13:34:27 2012 Yes. imake doesn't run properly if built with clang; you must build with GCC/g++. Chris So is this something for the port maintaner (x11@) to sort out? Anton On 31 Dec 2012 13:11, "Anton Shterenlikht" w

Re: xfig build failure on amd64 with clang, possibly imake problem?

2012-12-31 Thread Chris Rees
Yes. imake doesn't run properly if built with clang; you must build with GCC/g++. Chris On 31 Dec 2012 13:11, "Anton Shterenlikht" wrote: > > Something wrong with imake/clang? Thanks Anton Script started on Sun Dec 30 22:08:55 2012 command: make ===> Found saved configuration for xfig-3.2.5b_1

xfig build failure on amd64 with clang, possibly imake problem?

2012-12-31 Thread Anton Shterenlikht
Something wrong with imake/clang? Thanks Anton Script started on Sun Dec 30 22:08:55 2012 command: make ===> Found saved configuration for xfig-3.2.5b_1 ===> xfig-3.2.5b_1 depends on file: /usr/local/sbin/pkg - found ===> Extracting for xfig-3.2.5b_1 => SHA256 Checksum OK for xfig.3.2.5b.fu

Current unassigned ports problem reports

2012-12-31 Thread FreeBSD bugmaster
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsol

Re: emulators/virtualbox-ose-kmod: always use compiler "cc" which is on my basesystem CLANG 3.2 (FreeBSD 10.0)

2012-12-31 Thread O. Hartmann
Am 12/31/12 07:22, schrieb Bernhard Fröhlich: > Am 30.12.2012 15:15 schrieb "O. Hartmann" : >> >> Port emulators/virtualbox-ose-kmod is known not to compile with CLANG >> 3.1/3.2. Therefor, it should be compiled with gcc. >> >> Either setting USE_GCC=4.6+ or USE_GCC=any in the port's makefile or by