The following reply was made to PR os-next/1614; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-next/1614: can't compile
Date: Mon, 5 Jan 1998 07:35:55 -0800 (PST)
[EMAIL PROTECTED]: nm ap_signal.o
nm: no name list
The following reply was made to PR os-next/1614; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: Dean Gaudet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-next/1614: can't compile
Date: Mon, 5 Jan 1998 12:36:23 -0800 (PST)
That worked!
Compiles on NeXT Mach 3.3 and 4.2
The following reply was made to PR os-next/1613; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: Dean Gaudet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-next/1613: can't compile
Date: Fri, 2 Jan 1998 11:10:51 -0800 (PST)
I modified conf.h
I got rid of the if/else and left
The following reply was made to PR os-next/1613; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: Dean Gaudet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-next/1613: can't compile
Date: Fri, 2 Jan 1998 11:30:05 -0800 (PST)
fixed/fixed[EMAIL PROTECTED]: touch aaa.c
[EMAIL
The following reply was made to PR os-next/1614; it has been noted by GNATS.
From: [EMAIL PROTECTED]
To: Dean Gaudet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: os-next/1614: can't compile
Date: Fri, 2 Jan 1998 11:35:00 -0800 (PST)
Yep! I did a make clean first. Even deleted
