Re: building ports (well, pkg) and make -j (even -j1 ) on a fast and64 machine: builds fail (head -r325997 context)

Mark Millard wrote: > [Plain "make" works (no -j ).] > > Is it expected that -j1 and the like get what I report below? A bug in the makefile (eg conflict b/w .ORDER and dependencies) will result in that sort of noise. -j1 is still jobs mode

building ports (well, pkg) and make -j (even -j1 ) on a fast and64 machine: builds fail (head -r325997 context)

[Plain "make" works (no -j ).] Is it expected that -j1 and the like get what I report below? (Other oddities with -j usage for port builds have been noted on an rpi2.) In /usr/ports/ports-mgmt/pkg : ( WRKDIRPREFIX?=/wrkdirs ) # make -j30 --- check-license --- ===> License BSD2CLAUSE accepted

r232498 breaks building ports security/nss with both gcc clang

after updated current- as of Mar 5, security/nss build broken at /usr/include/runetype.h /usr/include/xlocale/_ctype.h. A quick grep shows that nowhere else under /usr/src/include uses 'inline'. gcc: gmake[1]: Entering directory

Re: r232498 breaks building ports security/nss with both gcc clang

On 2012-03-06 20:10, Jia-Shiun Li wrote: after updated current- as of Mar 5, security/nss build broken at /usr/include/runetype.h /usr/include/xlocale/_ctype.h. A quick grep shows that nowhere else under /usr/src/include uses 'inline'. Fixed in r232620. Can you please retry, after updating

Re: Infinite 'make' loops while building ports

I've just seen the same problem with libnet. The machine in question was installed via a DP1 CD yesterday. I updated it about 1PM today to the latest -CURRENT. When I saw the infinite 'make' loop (about 15...30...60 minutes ago), I deleted /usr/ports on the looping machine; resynced my CVS

Re: Infinite 'make' loops while building ports

I should also have mentioned that other ports install normally. I just finished installing unzip. Jay On Thursday 23 May 2002 01:28 am, Jay wrote: I've just seen the same problem with libnet. The machine in question was installed via a DP1 CD yesterday. I updated it about 1PM today to

Re: Infinite 'make' loops while building ports

--- Jay [EMAIL PROTECTED] wrote: I should also have mentioned that other ports install normally. I just finished installing unzip. Jay To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message It seems /usr/bin/make set the

Re: Infinite 'make' loops while building ports

On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka Kudo wrote: It seems /usr/bin/make set the environment variable MAKEFILE to the Makefile it uses. So when you type make build or install, MAKEFILE is pointed to the port's Makefile. Workaround for me at this moment is to run make build

Re: Infinite 'make' loops while building ports

--- Marcel Moolenaar [EMAIL PROTECTED] wrote: On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka Kudo wrote: It seems /usr/bin/make set the environment variable MAKEFILE to the Makefile it uses. So when you type make build or install, MAKEFILE is pointed to the port's Makefile.

Re: Infinite 'make' loops while building ports

On Thu, 23 May 2002, Marcel Moolenaar wrote: On Thu, May 23, 2002 at 02:33:56AM -0700, Shizuka Kudo wrote: It seems /usr/bin/make set the environment variable MAKEFILE to the Makefile it uses. So when you type make build or install, MAKEFILE is pointed to the port's Makefile.

Re: Infinite 'make' loops while building ports

On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: You're right. The only reason it didn't show up several days before is that v 1.58 added the real path to MAKEFILE as mentioned in the commit log: Try with the current make(1) sources. -- [EMAIL PROTECTED] | C, MIPS, POSIX,

Re: Infinite 'make' loops while building ports

On Thursday 23 May 2002 07:18 am, J. Mallett wrote: On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: You're right. The only reason it didn't show up several days before is that v 1.58 added the real path to MAKEFILE as mentioned in the commit log: Try with the current

Re: Infinite 'make' loops while building ports

On Thu, May 23, 2002 at 12:18:59PM +, J. Mallett wrote: On Thu, May 23, 2002 at 03:46:01AM -0700, Shizuka Kudo wrote: You're right. The only reason it didn't show up several days before is that v 1.58 added the real path to MAKEFILE as mentioned in the commit log: Try with the

Infinite 'make' loops while building ports

Hello, I just upgraded my 4-STABLE machine to -CURRENT via source. Everything seemed to go smoothly and things are running fine, EXCEPT when I try to build *any* of the ports in the ports collection. Every time I run 'make' it gets stuck in an infinite loop and doesn't build the port. Some

Re: Infinite 'make' loops while building ports

On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote: Hello, I just upgraded my 4-STABLE machine to -CURRENT via source. Everything seemed to go smoothly and things are running fine, EXCEPT when I try to build *any* of the ports in the ports collection. Every time I run 'make' it

Re: Infinite 'make' loops while building ports

On Wed, 2002-05-22 at 18:27, Kris Kennaway wrote: I just upgraded my 4-STABLE machine to -CURRENT via source. Everything seemed to go smoothly and things are running fine, EXCEPT when I try to build *any* of the ports in the ports collection. Every time I run 'make' it gets stuck in

Problems building ports/x11-toolkits/wxGTK

Hello, I tried to build the wxGTK-2.1.16 port, and noticed that a few AC_CHECK(..) macros in the configure script don't work. The first header file which is not found is X11/XKBlib.h because on FreeBSD systems there is no link /usr/include/X11 - /usr/X11R6/include (shouldn't there be

Re: Problems building ports/x11-toolkits/wxGTK

Sorry, it should be: /usr/include/X11 - /usr/X11R6/include/X11 and CONFIGURE_ENV= GTK_CONFIG="${X11BASE}/bin/gtk12-config"\ CCFLAGS="-I${X11BASE}/include"\ LDFLAGS="-L${X11BASE}/lib" Norbert Irmer wrote: Hello, I tried to build the

Re: building ports

well, on the advice of someone, i manually edited these files changing the date in them to 2201, before changing it it was 19990308. i dunno if its significant, but i rebuilt using make buildworld, make installworld. and i did run mergemaster afterwards. what date is supposed to be in this

Re: building ports

On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: : Your system is too old to use this bsd.port.mk. According to the mail headers, your system clock is about one year behind actual time. That might have screwed up the `make'... Best regards, -- Edwin H. Kremer, senior systems- and

Re: building ports

On Thu, 09 Mar 2000, in a never-ending search for enlightenment, Edwin Kremer wrote: On Mon, Mar 08, 1999 at 09:44:26PM -0600, Ishmael wrote: : Your system is too old to use this bsd.port.mk. According to the mail headers, your system clock is about one year behind actual time. That

building ports

within the last 4 days ive upgraded my system from 3.4-stable to -current. until this morning, i had no problems really, but then (this morning) i no longer was able to build any ports, kept receiving error: Your system is too old to use this bsd.port.mk. You need a fresh make world or an upgrade

RE: building ports

PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ishmael Sent: Tuesday, 9 March 1999 14:44 To: [EMAIL PROTECTED] Subject: building ports within the last 4 days ive upgraded my system from 3.4-stable to -current. until this morning, i had no problems really, but then (this morning) i no longer

Re: Building ports...

Gary D. Margiotta wrote: any given port.? It then tells me the following: fetch: illegal option -- A It seems that you have outdated fetch - update your sources (via cvsup or any other way)? and then do following: # cd /usr/src/lib/libfetch/ # make all install clean # cd

Building ports...

Heya... I apologize if this is a slight off topic question, but I think it might be related to -current... Just loaded a 3.1-STABLE box, and went to build a couple of ports. First it told me that I couldn't use the bsd.port.mk because it was too old. Fine, so I go and cvsup the current sources