Re: State of the ports collection

2002-06-04 Thread Patrick L Hartling
It's a bit of a beast to compile, but the jdk13 port uses new.h in a couple of C++ files (I could be more specific, but I don't have the source extracted right now). Since that's now in the backward directory, I fixed the compile errors by including instead. Everything else in that port com

Re: State of the ports collection

2002-06-04 Thread Kris Kennaway
On Tue, Jun 04, 2002 at 02:29:17PM -0700, David O'Brien wrote: > On Mon, Jun 03, 2002 at 01:42:24PM -0700, Kris Kennaway wrote: > > * (lots of ports) The new C++ compiler deprecated a lot of headers by > > moving them to a different directory: this breaks a heck of a lot of > > ports). IMO we

Re: State of the ports collection

2002-06-04 Thread David O'Brien
On Mon, Jun 03, 2002 at 01:42:24PM -0700, Kris Kennaway wrote: > * (lots of ports) The new C++ compiler deprecated a lot of headers by > moving them to a different directory: this breaks a heck of a lot of > ports). IMO we should be searching this directory by default. example port please.

RE: State of the ports collection

2002-06-04 Thread Trish Lynch
On Tue, 4 Jun 2002, Dan Trainor wrote: > What's going to happen to all these ports that still depend on file > locations in the 4.5 release(s)? The reason I ask is that I see that > now we're going to have to make two kinds of ports - one for 4.x and one > for 5.x, or are header files and stuff

Re: State of the ports collection

2002-06-04 Thread Christian Weisgerber
Kris Kennaway <[EMAIL PROTECTED]> wrote: > It seems like ports committers are not able to keep up with the > rate at which ports are being broken by -current changes: Since I originally stated that I would work on fixing ports on alpha and I have clearly failed to do so, I would like to point ou

Re: State of the ports collection

2002-06-04 Thread Dan Nelson
In the last episode (Jun 04), Dan Trainor said: > What's going to happen to all these ports that still depend on file > locations in the 4.5 release(s)? The reason I ask is that I see that > now we're going to have to make two kinds of ports - one for 4.x and > one for 5.x, or are header files an

RE: State of the ports collection

2002-06-04 Thread Dan Trainor
What's going to happen to all these ports that still depend on file locations in the 4.5 release(s)? The reason I ask is that I see that now we're going to have to make two kinds of ports - one for 4.x and one for 5.x, or are header files and stuff like that stored as global variables... or somet

Re: State of the ports collection

2002-06-03 Thread Tim J. Robbins
On Mon, Jun 03, 2002 at 01:42:24PM -0700, Kris Kennaway wrote: > * (lots of ports) The new C++ compiler deprecated a lot of headers by > moving them to a different directory: this breaks a heck of a lot of > ports). IMO we should be searching this directory by default. I believe it is the i

Re: State of the ports collection

2002-06-03 Thread Kris Kennaway
On Mon, Jun 03, 2002 at 04:17:14PM -0700, Terry Lambert wrote: > How long does it take to build world + all ports, vs. just "world", > if what you are doing is building everything, not caring about > correcting ports dependencies? E.g. not serializing through the > ports build farm process? Is

Re: State of the ports collection

2002-06-03 Thread Marc G. Fournier
Terry, I have a high speed connection over here, so if its purely a 'typing' change sort of thing, if you want to tell me what needs to be done to fix these, I can make the changes and submit patches (I can't login to my FreeBSD account to make the commits myself ... my key went out of date *sigh

Re: State of the ports collection

2002-06-03 Thread Kris Kennaway
On Mon, Jun 03, 2002 at 04:54:32PM -0700, Terry Lambert wrote: > Kris Kennaway wrote: > > > But the error handling path of any program is not one of them; if > > > you are optimizing something other than the success path, there is > > > something fundamentally wrong with your program or problem st

Re: State of the ports collection

2002-06-03 Thread Terry Lambert
Kris Kennaway wrote: > > But the error handling path of any program is not one of them; if > > you are optimizing something other than the success path, there is > > something fundamentally wrong with your program or problem statement. > > So how about you do more than the average person's part t

Re: State of the ports collection

2002-06-03 Thread Kris Kennaway
On Mon, Jun 03, 2002 at 04:21:24PM -0700, Terry Lambert wrote: > > > http://bento.freebsd.org/errorlogs/5-latest/bogosort-0.3.3.log > > > > Any program which declares sys_errlist for itself is wrong. In most > > cases, the program should be using either strerror() or strerror_r(), > > dependi