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

[Simon J. Gerraty]

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[Mark Millard]

[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 by the user
--- pkg-depends ---
--- do-fetch ---
--- fetch-specials ---
===> Fetching all distfiles required by pkg-1.10.2 for building
--- /wrkdirs/usr/ports/ports-mgmt/pkg/work/.extract_done.pkg._usr_local ---
`check-build-conflicts' was not built (made 1, flags 2009, type 2010001)!
`check-build-conflicts' has .ORDER dependency against fetch (made 0, flags 
9, type 3010001)
`extract-message' was not built (made 1, flags 2009, type a010001)!
`extract-message' has .ORDER dependency against check-build-conflicts (made 
1, flags 2009, type 2010001)
`check-categories' was not built (made 0, flags 2009, type 3010001)!
`identify-install-conflicts' was not built (made 0, flags 2009, type 3010001)!
`identify-install-conflicts' has .ORDER dependency against check-categories 
(made 0, flags 2009, type 3010001)
`check-deprecated' was not built (made 0, flags 2009, type 3010001)!
`check-deprecated' has .ORDER dependency against identify-install-conflicts 
(made 0, flags 2009, type 3010001)
`check-vulnerable' was not built (made 0, flags 2009, type 3010001)!
`check-vulnerable' has .ORDER dependency against check-deprecated (made 0, 
flags 2009, type 3010001)
`check-license' was not built (made 0, flags 2009, type b010001)!
`check-license' has .ORDER dependency against check-vulnerable (made 0, 
flags 2009, type 3010001)
`pre-check-config' was not built (made 0, flags 2009, type 301)!
`pkg-depends' was not built (made 0, flags 2009, type b410001)!
`pkg-depends' has .ORDER dependency against check-sanity (made 0, flags 
3009, type 3010001)
`fetch-depends' was not built (made 0, flags 2009, type 3010001)!
`fetch-depends' has .ORDER dependency against pkg (made 0, flags 3009, type 
3010001)
`do-fetch' was not built (made 0, flags 2009, type b010001)!
`do-fetch' has .ORDER dependency against fetch-depends (made 0, flags 2009, 
type 3010001)
`fetch-specials' was not built (made 0, flags 2009, type b410001)!
`fetch-specials' has .ORDER dependency against do-fetch (made 0, flags 
2009, type b010001)
`extract-depends' was not built (made 1, flags 2009, type 2010001)!
`extract-depends' has .ORDER dependency against checksum (made 1, flags 
3009, type a410001)
`clean-wrkdir' was not built (made 1, flags 2009, type a010001)!
`clean-wrkdir' has .ORDER dependency against extract-depends (made 1, flags 
2009, type 2010001)
`/wrkdirs/usr/ports/ports-mgmt/pkg/work' was not built (made 1, flags 2009, 
type b010001)!
`/wrkdirs/usr/ports/ports-mgmt/pkg/work' has .ORDER dependency against 
clean-wrkdir (made 1, flags 2009, type a010001)
`extract-fixup-modes' was not built (made 1, flags 2009, type a010001)!
`extract-fixup-modes' has .ORDER dependency against do-extract (made 1, 
flags 3009, type a010001)
*** [/wrkdirs/usr/ports/ports-mgmt/pkg/work/.extract_done.pkg._usr_local] Error 
code 1

make: stopped in /usr/ports/ports-mgmt/pkg
1 error

make: stopped in /usr/ports/ports-mgmt/pkg

Even -j1 gets such:

# make -j1
===>  License BSD2CLAUSE accepted by the user
===> Fetching all distfiles required by pkg-1.10.2 for building
`check-build-conflicts' was not built (made 1, flags 2009, type 2010001)!
`check-build-conflicts' has .ORDER dependency against fetch (made 0, flags 
9, type 3010001)
`extract-message' was not built (made 1, flags 2009, type a010001)!
`extract-message' has .ORDER dependency against check-build-conflicts (made 
1, flags 2009, type 2010001)
`check-categories' was not built (made 0, flags 2009, type 3010001)!
`identify-install-conflicts' was not built (made 0, flags 2009, type 3010001)!
`identify-install-conflicts' has .ORDER dependency against check-categories 
(made 0, flags 2009, type 3010001)
`check-deprecated' was not built (made 0, flags 2009, type 3010001)!
`check-deprecated' has .ORDER dependency against identify-install-conflicts 
(made 0, flags 2009, type 3010001)
`check-vulnerable' was not built (made 0, flags 2009, type 3010001)!
`check-vulnerable' has .ORDER dependency against check-deprecated (made 0, 
flags 2009, type 3010001)
`check-license' was not built (made 0, flags 2009, type b010001)!
`check-license' has .ORDER dependency against check-vulnerable (made 0, 
flags 2009, type 3010001)
`pre-check-config' was not built (made 0, flags 2009, type 301)!
`pkg-depends' was not built (made 0, flags 2009, type b410001)!
`pkg-depends' has .ORDER dependency against check-sanity (made 0, flags 
3009, type 3010001)
`fetch-depends' was not built (made 0, flags 2009, type 3010001)!
`fetch-depends' has .ORDER dependency against pkg (made 0, flags 3009, type 
3010001)
`do-fetch' was not built (made 0, flags 2009, type b010001)!

r232498 breaks building ports security/nss with both gcc clang

[Jia-Shiun Li]

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
`/usr/ports/security/nss/work/nss-3.13.3/mozilla/security/nss/lib'
cd util; gmake libs
gmake[2]: Entering directory
`/usr/ports/security/nss/work/nss-3.13.3/mozilla/security/nss/lib/util'
cc -o FreeBSD10.0_OPT.OBJ/quickder.o -c -O2 -pipe
-I/usr/local/include/nspr -L/usr/local/lib -fno-strict-aliasing -O
-fPIC -ansi -Wall
 -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX
-UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_
UTIL_DIRECTLY -I../../dist/FreeBSD10.0_OPT.OBJ/include
-I../../dist/public/ -I../../dist/private/  -O -fPIC -ansi -Wall
-Wno-switch -D
FREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG
-D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -
I../../../dist/FreeBSD10.0_OPT.OBJ/include -I../../../dist/public/
-I../../../dist/private/  -O -fPIC -ansi -Wall -Wno-switch -DFREEBS
D -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG
-D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY
-I../..
/../../dist/FreeBSD10.0_OPT.OBJ/include -I../../../../dist/public/nss
-I../../../../dist/private/nss  quickder.c
In file included from /usr/include/_ctype.h:94,
 from /usr/include/ctype.h:46,
 from secport.h:83,
 from seccomon.h:62,
 from secasn1.h:51,
 from quickder.c:43:
/usr/include/runetype.h:93: error: expected '=', ',', ';', 'asm' or
'__attribute__' before 'const'
In file included from /usr/include/ctype.h:46,
 from secport.h:83,
 from seccomon.h:62,
 from secasn1.h:51,
 from quickder.c:43:
/usr/include/_ctype.h: In function '__maskrune':
/usr/include/_ctype.h:100: error: invalid type argument of '-'
/usr/include/_ctype.h: In function '__sbmaskrune':
/usr/include/_ctype.h:107: error: invalid type argument of '-'
/usr/include/_ctype.h: In function '__toupper':
/usr/include/_ctype.h:133: error: invalid type argument of '-'
/usr/include/_ctype.h: In function '__sbtoupper':
/usr/include/_ctype.h:140: error: invalid type argument of '-'
/usr/include/_ctype.h: In function '__tolower':
/usr/include/_ctype.h:147: error: invalid type argument of '-'
/usr/include/_ctype.h: In function '__sbtolower':
/usr/include/_ctype.h:154: error: invalid type argument of '-'
In file included from /usr/include/ctype.h:83,
 from secport.h:83,
 from seccomon.h:62,
 from secasn1.h:51,
 from quickder.c:43:
/usr/include/xlocale/_ctype.h: At top level:
/usr/include/xlocale/_ctype.h:112: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'int'
/usr/include/xlocale/_ctype.h:112: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'int'
/usr/include/xlocale/_ctype.h:113: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'int'
/usr/include/xlocale/_ctype.h:113: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'int'
/usr/include/xlocale/_ctype.h:114: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'int'



clang:

gmake[1]: Entering directory
`/usr/ports/security/nss/work/nss-3.13.3/mozilla/security/nss/lib'
cd util; gmake libs
gmake[2]: Entering directory
`/usr/ports/security/nss/work/nss-3.13.3/mozilla/security/nss/lib/util'
clang -o FreeBSD10.0_OPT.OBJ/quickder.o -c -O2 -pipe
-I/usr/local/include/nspr -L/usr/local/lib -fno-strict-aliasing -O
-fPIC -ansi -W
all -Wno-switch -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX
-UDEBUG -DNDEBUG -D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DU
SE_UTIL_DIRECTLY -I../../dist/FreeBSD10.0_OPT.OBJ/include
-I../../dist/public/ -I../../dist/private/  -O -fPIC -ansi -Wall
-Wno-switch
 -DFREEBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG
-D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTL
Y -I../../../dist/FreeBSD10.0_OPT.OBJ/include -I../../../dist/public/
-I../../../dist/private/  -O -fPIC -ansi -Wall -Wno-switch -DFRE
EBSD -DHAVE_STRERROR -DHAVE_BSD_FLOCK -DXP_UNIX -UDEBUG -DNDEBUG
-D_THREAD_SAFE -D_REENTRANT -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -I..
/../../../dist/FreeBSD10.0_OPT.OBJ/include
-I../../../../dist/public/nss -I../../../../dist/private/nss
quickder.c
clang: warning: argument unused during compilation: '-L/usr/local/lib'
In file included from quickder.c:43:
In file included from ./secasn1.h:51:
In file included from ./seccomon.h:62:
In file included from ./secport.h:83:
In file included from /usr/include/ctype.h:46:
In file included from /usr/include/_ctype.h:94:
/usr/include/runetype.h:93:8: error: unknown type name 'inline'
static inline const _RuneLocale *__getCurrentRuneLocale(void)
   ^
/usr/include/runetype.h:93:15: error: expected identifier or '('
static inline 

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

[Dimitry Andric]

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 and reinstalling
the headers?  The security/nss port and its dependencies now build fine
here.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Infinite 'make' loops while building ports

[Jay]

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 tree on my server, 
cvsup'd to get /usr/ports back; and attempted to 'make build' libnet.  Same 
thing -- the infinite 'no MD5 sum' loop.

Then I deleted the ports directory out of my CVS tree and resynced it.  While 
I was doing that, I also re-deleted the /usr/ports dir on the looping 
machine.  After resyncing /usr/ports with my fresh (finished updating 5 
minutes ago) CVS tree, I still see the same problem.

Jay

On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote:
 Hello,
=20
 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.=20
 Some examples:

Are you sure you have an up-to-date ports collection?  This bug was
fixed a few weeks ago.

Kris






To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Jay]

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 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 tree on my
 server, cvsup'd to get /usr/ports back; and attempted to 'make build'
 libnet.  Same thing -- the infinite 'no MD5 sum' loop.

 Then I deleted the ports directory out of my CVS tree and resynced it. 
 While I was doing that, I also re-deleted the /usr/ports dir on the looping
 machine.  After resyncing /usr/ports with my fresh (finished updating 5
 minutes ago) CVS tree, I still see the same problem.

 Jay

 On Wed, May 22, 2002 at 06:21:22PM -0700, Scott Reese wrote:
  Hello,
 =20
  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.=20
  Some examples:

 Are you sure you have an up-to-date ports collection?  This bug was
 fixed a few weeks ago.

 Kris






 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Shizuka Kudo]

--- 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 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 MAKEFILE=Makefile so that
bsd.ports.mk use the correct Makefile in WRKSRC.

Is the behaviour in /usr/bin/make changed recently?

__
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Marcel Moolenaar]

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 MAKEFILE=Makefile so that
 bsd.ports.mk use the correct Makefile in WRKSRC.
 
 Is the behaviour in /usr/bin/make changed recently?

No. This is old behaviour and I filed a PR for it many moons ago.
I have replaced all uses of MAKEFILE with MAKE_FILE in all the
makefiles that set it (and changed bsd.ports.mk as well of course)
The problem is more visible if you set WRKDIROREFIX.

-- 
 Marcel Moolenaar USPA: A-39004  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Shizuka Kudo]

--- 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. Workaround for me at this moment
 is
  to run make build MAKEFILE=Makefile so that
  bsd.ports.mk use the correct Makefile in WRKSRC.
  
  Is the behaviour in /usr/bin/make changed
 recently?
 
 No. This is old behaviour and I filed a PR for it
 many moons ago.
 I have replaced all uses of MAKEFILE with MAKE_FILE
 in all the
 makefiles that set it (and changed bsd.ports.mk as
 well of course)
 The problem is more visible if you set WRKDIROREFIX.
 
 -- 
  Marcel Moolenaar   USPA: A-39004 
[EMAIL PROTECTED]

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:

Make ReadMakefile() operate using the realpath(3) name
for the file handed to
it, which means that relative paths will be expanded
to absolute paths, and
filenames without a path will end up with their
absolute path included as
well.  This aids tremendously in debugging a build
using our make(1) with
multiple Makefile's, such as when there is a syntax
error in a file in a
sub-directory as per bsd.subdir.mk.  Normally we'd
end up with just
Makefile known about the Makefile in question, which
means that an error
would be useless for someone trying to debug their
build system, now we
end up with a complete real pathname for the Makefile.

So mostly this is useful in a debugging context, but
possibly others too
(I haven't thought of them yet, but they probably are
more useful if you
make Dir_FindFile use realpath(3), but that's another
story).



__
Do You Yahoo!?
LAUNCH - Your Yahoo! Music Experience
http://launch.yahoo.com

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Rolf Schillinger]

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. Workaround for me at this moment is
  to run make build MAKEFILE=Makefile so that
  bsd.ports.mk use the correct Makefile in WRKSRC.
  
  Is the behaviour in /usr/bin/make changed recently?
 
 No. This is old behaviour and I filed a PR for it many moons ago.
 I have replaced all uses of MAKEFILE with MAKE_FILE in all the
 makefiles that set it (and changed bsd.ports.mk as well of course)
 The problem is more visible if you set WRKDIROREFIX.
http://groups.google.com/groups?hl=enlr=threadm=3CDC0724.C9ACC64C_FreeBSD.org%40ns.sol.netrnum=4prev=/groups%3Fq%3Dfreebsd%2Binfinite%2Bmake%2Bloop%26hl%3Den%26lr%3D%26scoring%3Dd%26selm%3D3CDC0724.C9ACC64C_FreeBSD.org%2540ns.sol.net%26rnum%3D4
says that this is a problem in textproc/expat2 and indeed if I remove the
Makefile there and do a make clean in /usr/ports it chews through the
ports with the occasional error when it hits an expat dependency.
Above thread states that this should be fixed by expat2 Makefile
rev. 1.14. That Makefile however doesn't get updated on cvsup. If I delete
it no version of it gets checked out. My Makefile is rev. 1.13
bis bald, Rolf



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[J. Mallett]

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, UNIX, BSD, IRC Geek.
http://www.FreeBSD.org | The Power to Serve
Vote for me for FreeBSD core or the cute little bunny gets it.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Jay]

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 make(1) sources.

Works great for me.  Thanks.

Jay

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Marcel Moolenaar]

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 current make(1) sources.

Doesn't this push the problem back into obscurity without
fixing anything?

I mean, the problem is simply that MAKEFILE is defined and
reserved by make(1) and its use by the ports collection
conflicts and breaks ports.

-- 
 Marcel Moolenaar USPA: A-39004  [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Infinite 'make' loops while building ports

[Scott Reese]

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 examples:

sysutils/portupgrade:
borges[164] # make
===  Extracting for portupgrade-20020429
 Checksum OK for pkgtools-20020429.tar.bz2.
===   portupgrade-20020429 depends on file: /usr/local/bin/ruby - found
===  Patching for portupgrade-20020429
===  Configuring for portupgrade-20020429
===  Building for portupgrade-20020429
===  Extracting for portupgrade-20020429
 No MD5 checksum file.
===   portupgrade-20020429 depends on file: /usr/local/bin/ruby - found
===  Patching for portupgrade-20020429
===  Configuring for portupgrade-20020429
===  Building for portupgrade-20020429
===  Extracting for portupgrade-20020429
 No MD5 checksum file.

...[ad infinitum]

devel/autoconf213:
borges[167] # make
===  Extracting for autoconf213-2.13.000227_1
 Checksum OK for autoconf-000227.tar.bz2.
===   autoconf213-2.13.000227_1 depends on executable: gm4 - found
===  Patching for autoconf213-2.13.000227_1
===  Applying FreeBSD patches for autoconf213-2.13.000227_1
===  Configuring for autoconf213-2.13.000227_1
creating cache ./config.cache
checking for gm4... /usr/local/bin/gm4
checking for mawk... no
checking for gawk... gawk
checking for perl... /usr/bin/perl
checking for a BSD compatible install... /usr/bin/install -c -o root -g
wheel
updating cache ./config.cache
creating ./config.status
creating Makefile
creating testsuite/Makefile
===  Building for autoconf213-2.13.000227_1
===  Extracting for autoconf213-2.13.000227_1
 No MD5 checksum file.
===   autoconf213-2.13.000227_1 depends on executable: gm4 - found
===  Patching for autoconf213-2.13.000227_1
===  Configuring for autoconf213-2.13.000227_1
creating cache ./config.cache
checking for gm4... /usr/local/bin/gm4
checking for mawk... no
checking for gawk... gawk
checking for perl... /usr/bin/perl
checking for a BSD compatible install... /usr/bin/install -c -o root -g
wheel
updating cache ./config.cache
creating ./config.status
creating Makefile
creating testsuite/Makefile
===  Building for autoconf213-2.13.000227_1
===  Extracting for autoconf213-2.13.000227_1
 No MD5 checksum file.

...[also ad infinitum until I hit ^C]

This is pretty much the case with any port I try to build.  I'm sure
it's due to some silly thing I missed in the upgrade process somewhere,
but after hours of beating my head against a wall, I can't seem to come
up with any answers.  Anyone else seen this or know what to do about
it?  Searching Google and the archives yields nothing of any use.

TIA,
Scott


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Infinite 'make' loops while building ports

[Kris Kennaway]

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 gets stuck in an infinite loop and doesn't build the port. 
 Some examples:

Are you sure you have an up-to-date ports collection?  This bug was
fixed a few weeks ago.

Kris



msg38705/pgp0.pgp
Description: PGP signature

Re: Infinite 'make' loops while building ports

[Scott Reese]

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 an infinite loop and doesn't build the port. 
  Some examples:
 
 Are you sure you have an up-to-date ports collection?  This bug was
 fixed a few weeks ago.

Yes, I cvsup-ed the ports collection just a few minutes prior to my
first email.  Should I blow away the whole ports tree and re-grab them?

The relevant lines in my cvsup file are as follows:

*default host=cvsup14.FreeBSD.org
*default base=/usr/local/etc/cvsup
*default prefix=/usr
*default release=cvs tag=.
*default delete use-rel-suffix
ports-all


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Problems building ports/x11-toolkits/wxGTK

[Norbert Irmer]

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 such a link ? - i heard this is a standard)

The opengl header file GL/gl.h is also not found, and
the link test with "libGL" or "libMesaGL" fails too.

And shouldn't there be a line in the Makefile of the port
which shows how to compile wxGTK with opengl support ?
(it took me an hour to find out how to do this!)  

So i would propose to make the following changes to the
ports Makefile:


CONFIGURE_ENV=  GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
CCFLAGS="-I/usr/X11R6/include"\
LDFLAGS="-L/usr/X11R6/lib"

CONFIGURE_ARGS= "--with-opengl=yes"





-- 
email: [EMAIL PROTECTED]
web: http://gul.sourceforge.net


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Problems building ports/x11-toolkits/wxGTK

[Norbert Irmer]

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 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 such a link ? - i heard this is a standard)
 
 The opengl header file GL/gl.h is also not found, and
 the link test with "libGL" or "libMesaGL" fails too.
 
 And shouldn't there be a line in the Makefile of the port
 which shows how to compile wxGTK with opengl support ?
 (it took me an hour to find out how to do this!)
 
 So i would propose to make the following changes to the
 ports Makefile:
 
 CONFIGURE_ENV=  GTK_CONFIG="${X11BASE}/bin/gtk12-config"\
 CCFLAGS="-I/usr/X11R6/include"\
 LDFLAGS="-L/usr/X11R6/lib"
 
 CONFIGURE_ARGS= "--with-opengl=yes"



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: building ports

[Ishmael]

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 file btw?

Jeremy

 You just did make world and still got this error?  That's not supposed
 to happen.  What do
 
  ls -l /var/db/port.mkversion
  cat /var/db/port.mkversion
 
 say?
 
 Satoshi
 
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message
 



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: building ports

[Edwin Kremer]

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 network administrator.   [EMAIL PROTECTED]
Dept. of Computer Science,  Utrecht University, The Netherlands  [WHOIS: ehk3]
 http://www.cs.uu.nl/people/edwin/ ---


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: building ports

[Walter Brameld]

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 might have screwed up the `make'...
 
 
 Best regards,
 
 -- 
 Edwin H. Kremer, senior systems- and network administrator.   [EMAIL PROTECTED]
 Dept. of Computer Science,  Utrecht University, The Netherlands  [WHOIS: ehk3]
  http://www.cs.uu.nl/people/edwin/ ---
 
Ya think?
-- 
Walter Brameld

Microsoft: Where do you want to go today?
Linux: Where do you want to go tomorrow?
BSD:   Are you guys coming, or what?
Walter:Where the hell am I?



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

building ports

[Ishmael]

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 kit. Please go to http://www.FreeBSD.org/ports/ or a mirror
site and follow the instructions.
now there is obviously no upgrade kit for -current and i just did a make
world, yet i still get this error. ive also tried deleting my entire ports
collection and recvsuping fresh, but still same error.
any ideas how to rectify?

Jeremy



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

RE: building ports

[Chris Knight]

Howdy,
Have a look in bsd.port.mk for the version number that it needs to build
with. Then make a copy of /var/db/port.mkversion. Edit
/var/db/port.mkversion with the version number that bsd.port.mk requires.
I had this same problem when the 34upgrade package had been altered with a
new version number, but had not been released as a new package...

Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664  Fax: +61 3 6331 7032  Mob: +61 419 528 795
Web: http://www.aims.com.au



 -Original Message-
 From: [EMAIL 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 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 kit. Please go to http://www.FreeBSD.org/ports/
 or a mirror
 site and follow the instructions.
 now there is obviously no upgrade kit for -current and i just
 did a make
 world, yet i still get this error. ive also tried deleting my
 entire ports
 collection and recvsuping fresh, but still same error.
 any ideas how to rectify?

 Jeremy



 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Re: Building ports...

[Maxim Sobolev]

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 /usr/src/usr.bin/fetch/
# make all install clean
?

Regards,

Maxim



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message

Building ports...

[Gary D. Margiotta]

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 for /usr/share, and I do a
make install in /usr/src/share/mk.  The files install properly, and I go
to the ports collection.  I go into a number of ports, and try a 'make' an
any given port.  It then tells me the following:

fetch: illegal option -- A

So, it can't go out and grab the needed files to build the port.  No big
deal, I just go grab the source and make it manually.  This is not a huge
problem, but I'm just wondering what I've done wrong, or what I'm stupidly
forgetting to add or do additionally...

Any feedback would be great, TIA!!!

__
-Gary Margiotta Voice:  (973) 835-7855
TBE Internet Services   Fax:(973) 835-4755
http://www.tbe.net  E-Mail: g...@tbe.net



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message