Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Satoshi - Ports Wraith - Asami
* From: Nik Clayton <[EMAIL PROTECTED]> I really wish you would stop spreading FUD. Don't open your mouth if you don't know what you are talking about. * I was under the impression that if you were CVSup'ing the ports tree then * any changes to the ports subsystem (for example, new command l

Re: "objtrm" problem probably found (was Re: Stuck in "objtrm")

1999-07-11 Thread Matthew Dillon
: :That said, it should be fairly simple to change Matt's new in-line :assembler versions to insert LOCK prefixes when building an SMP :kernel. (Although I don't know that this is necessary yet, given :the `Big Giant Lock'). : :There remains the problem of locating all the operations in the kerne

ftp passive mode

1999-07-11 Thread Adam Wight
Why was the FTP_PASS_MODE logic changed? This forces everyone who uses active connections to alter their environment... -Adam Wight To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message

When will -CURRENT support PCMCIA modems again?

1999-07-11 Thread Greg Lehey
I've just updated my laptop from 3.2-RELEASE to 4.0-CURRENT, and I find that PCMCIA modems (sio) are no longer supported. I'm playing around with it to get it to work, but so far I've just managed to get panics out of sioprobe. Before I continue with this: is anybody else working on it? If so,

Re: Stuck in "objtrm" - live kernel test to run

1999-07-11 Thread Stephen McKay
On Saturday, 10th July 1999, Matthew Dillon wrote: >I'm trying to simulate your 486 setup. You must love pain! A make -j5 >buildworld on a 16MB-limited machine pages like hell (200-400 pageins/sec >AND 200-400 pageouts/sec simultaniously, almost continuously). Maximal pain, maximal

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread John Baldwin
On 12-Jul-99 Kris Kennaway wrote: > On Sun, 11 Jul 1999, Jordan K. Hubbard wrote: > >> > Q: I want to use this cool piece of software that's in the FreeBSD >> > ports system. But I can't build it on my 3.x-stable system. >> > >> > Why not? >> >> A. Likely because someone running onl

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Doug White
On Mon, 12 Jul 1999, Kris Kennaway wrote: > On Sun, 11 Jul 1999, Jordan K. Hubbard wrote: > > > > Q: I want to use this cool piece of software that's in the FreeBSD > > > ports system. But I can't build it on my 3.x-stable system. > > > > > > Why not? > > > > A. Likely because someo

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Tim Vanderhoek
On Mon, Jul 12, 1999 at 12:46:12AM +0100, Nik Clayton wrote: > > I was under the impression that if you were CVSup'ing the ports tree then > any changes to the ports subsystem (for example, new command line > parameters to fetch(1)) would be utilised by the ports system *before* > they had been

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Kris Kennaway
On Sun, 11 Jul 1999, Jordan K. Hubbard wrote: > > Q: I want to use this cool piece of software that's in the FreeBSD > > ports system. But I can't build it on my 3.x-stable system. > > > > Why not? > > A. Likely because someone running only on a -current box last committed >a cha

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Nik Clayton
On Mon, Jul 12, 1999 at 03:54:40PM -0700, Chris Piazza wrote: > Um..er... I hope you were really just being sarcastic. All ports > should work on -stable as well as -current. In fact, more build > on -stable than -current according to http://bento.freebsd.org/. > If any ports work on one but not

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread David O'Brien
> Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. Why not? > > A: Ah, sorry. The ports system only targets -current, trying to get it to > work with -stable is too much work. If you want to be sure of

Re: "objtrm" problem probably found (was Re: Stuck in "objtrm")

1999-07-11 Thread Peter Jeremy
Mike Haertel <[EMAIL PROTECTED]> wrote: >Um. FYI on x86, even if the compiler generates the RMW >form "addl $1, foo", it's not atomic. If you want it to >be atomic you have to precede the opcode with a LOCK >prefix 0xF0. I'd noticed that point as well. The top of sys/i386/include/atomic.h _doe

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Adam Strohl
On Sun, 11 Jul 1999, Nik Clayton wrote: > Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. > > Why not? > > A: Ah, sorry. The ports system only targets -current, trying to get > it to work with -sta

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Jordan K. Hubbard
> Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. > > Why not? A. Likely because someone running only on a -current box last committed a change to the port which broke it with 3.x. Please submit a bug

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Chris Piazza
On Sun, Jul 11, 1999 at 10:00:50PM +0100, Nik Clayton wrote: > hmm... > > > > Any other question? > > Q: I want to use this cool piece of software that's in the FreeBSD > ports system. But I can't build it on my 3.x-stable system. > > Why not? > > A: Ah, sorry. The ports syst

Re: "objtrm" problem probably found (was Re: Stuck in "objtrm")

1999-07-11 Thread Mike Haertel
>On Sat, 10 Jul 1999, Matthew Dillon wrote: >> >> The supposedly atomic functions in i386/include/atomic.h are not >> as atomic as was previously thought :-): >> >> #define atomic_add_short(P, V) (*(u_short*)(P) += (V)) >[...] > >Before I fixed this stuff for the alpha, the += e

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Nik Clayton
On Sun, Jul 11, 1999 at 08:13:37PM +0900, Daniel C. Sobral wrote: [snip] > "Q: Why shouldn't I just go ahead and run -current? That's got > all the latest stuff, right? [snip] > If you can live with that, and think you have any compelling reason > to run -current, read the handbook for fur

Re: utmp & last

1999-07-11 Thread Joe Greco
> Why do we store the utmp/wtmp and last logs in different data > structures? > > What seems strange is that they use the different data types to > store the same information (the time): > > struct lastlog { > time_t ll_time; > charll_line[UT_LINES

Re: HELP!!! -CURRENT libtool problem.

1999-07-11 Thread Daniel C. Sobral
Nicolas Blais wrote: > > Hi. I've finally installed FreeBSD 4.0 and to tell you the truth, I'm > not > very impressed. I was expecting some bugs but not like that... Well, maybe this FAQ entry candidate will help clarify things for you: "Q: Why shouldn't I just go ahead and run -current? Tha

Re: "objtrm" problem probably found (was Re: Stuck in "objtrm")

1999-07-11 Thread Doug Rabson
On Sun, 11 Jul 1999, Alan Cox wrote: > On Sun, Jul 11, 1999 at 08:12:52AM +0100, Doug Rabson wrote: > > > > What a nightmare. This must be due to egcs compiling things differently > > from gcc 2.7.1. ... > > Yes, at least for the one case in vm_pageout_flush. (I checked > the analogous code on

Re: "objtrm" problem probably found (was Re: Stuck in "objtrm")

1999-07-11 Thread Alan Cox
Actually, I should have said swap_pager_getpages and not vm_pageout_flush. Alan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message