Re: make world broken

1999-12-19 Thread Jos Backus

On Sat, Dec 18, 1999 at 05:13:39PM -0800, Steve Kargl wrote:
> I did a "make -j 4 buildworld" every day last week.  I did not
> see this error.  Did you by any chance run configure in the
> contrib/gcc (or whatever the current gcc contrib source tree
> is called)?

No.

> If your build tree ends up in /usr/obj, then you might try
> rm -rf /usr/obj
> chflags -r noschg /usr/obj
> rm -rf /usr/obj
> cd /usr/src 
> make clean
> make buildworld

That did the trick (although I had to do the buildworld twice - the first time
there was this error about not knowing how to make .../stdarg.h). All is well
again on my home box now. Maybe this was caused by my having done a world
build in the middle of the build restructuring, which left /usr/obj in a "bad"
state somehow.

Thanks for your help sorting this one out.

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


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



Re: make world broken

1999-12-18 Thread Steve Kargl

Jos Backus wrote:
> More precisely, three things seem to be wrong:
> 
> - hconfig.h is missing/not being generated.
> 
> - /usr/include/stdio.h says:
> 
>   extern __const char *__const sys_errlist[];
> 
>   but /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h says:
> 
>   extern char *sys_errlist[];
> 
>   possibly because HAVE_STRERROR is not defined at that point.
> 
> - The PVPROTO macro is not defined at that point; it is defined in
>   /usr/src/contrib/gcc/gansidecl.h as
> 
>   #define PVPROTO(ARGS) PARAMS(ARGS)
> 
> Is anyone else seeing this?
> 

I did a "make -j 4 buildworld" every day last week.  I did not
see this error.  Did you by any chance run configure in the
contrib/gcc (or whatever the current gcc contrib source tree
is called)?

If your build tree ends up in /usr/obj, then you might try
rm -rf /usr/obj
chflags -r noschg /usr/obj
rm -rf /usr/obj
cd /usr/src 
make clean
make buildworld

-- 
Steve


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



Re: make world broken

1999-12-18 Thread Jos Backus

More precisely, three things seem to be wrong:

- hconfig.h is missing/not being generated.

- /usr/include/stdio.h says:

extern __const char *__const sys_errlist[];

  but /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h says:

extern char *sys_errlist[];

  possibly because HAVE_STRERROR is not defined at that point.

- The PVPROTO macro is not defined at that point; it is defined in
  /usr/src/contrib/gcc/gansidecl.h as

#define PVPROTO(ARGS) PARAMS(ARGS)

Is anyone else seeing this?

jos:/usr/src# make -f Makefile.inc1 build-tools
cd /usr/src/bin/sh; make build-tools
cd /usr/src/games/adventure; make build-tools
cd /usr/src/games/hack; make build-tools
cd /usr/src/games/phantasia; make build-tools
cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools
cd /usr/src/gnu/usr.bin/cc/f771; make build-tools
cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H 
-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" 
-I/usr/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc 
-I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/config 
-I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f -I.   -c 
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c
In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/proj.h:28,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c:24:
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h: No 
such file or directory
In file included from 
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/system.j:25,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/proj.h:32,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fini.c:24:
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting types 
for `sys_errlist'
/usr/include/stdio.h:225: previous declaration of `sys_errlist'
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error before 
`PVPROTO'
*** Error code 1

Stop in /usr/src/gnu/usr.bin/cc/f771.
*** Error code 1

Stop in /usr/src.
jos:/usr/src# 

Thanks,
-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


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



Re: make world is failed on pc98

1999-12-18 Thread Bruce Evans

On Sun, 12 Dec 1999, Takahashi Yoshihiro wrote:

> The 'loader' program is only transplanted for pc98. The boot2
> (sys/boot/pc98/boot2) is the mostly same as the old biosboot
> (sys/pc98/boot/biosboot) .
> 
> > boot2 is already capable of loading ELF, right?
> 
> No.

I use a modified version of biosboot which is capable of loading ELF.
biosboot has many improvements on i386/boot2.  E.g., its C source
files actually have comments apart from copyrights.

> > Isn't it therefore enough to just compile boot2 as ELF?
> 
> No.
> 
> > In other words, what are the problems?
> 
> We need to transplant the new boot2 (sys/boot/i386/boot2) to pc98 to
> compile as ELF.

I think you only need to compile it to ELF and maybe use btxld instead
of dd to strip the headers.  It can then load `loader'.

Bruce



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



Re: Proposed end-all fix for (Re: Make world broken in libc_r)

1999-12-18 Thread Marcel Moolenaar

Jason Evans wrote:
> 
> I've got a change in the pipeline that will cause world breakage again,
> unless we do something about this.  Is there anything wrong with simply
> adding:
> 
> CFLAGS+=-I${.CURDIR}/../../include
> 
> to lib/libc_r/Makefile?  It fixes such build problems.

Yes, anything is wrong. ${DESTDIR}/usr/include is already present in
CFLAGS and points to the proper include files.

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Proposed end-all fix for (Re: Make world broken in libc_r)

1999-12-17 Thread Jason Evans

On Sat, Nov 27, 1999 at 11:40:08AM -0800, Alfred Perlstein wrote:
> On Sat, 27 Nov 1999, Mark Murray wrote:
> 
> > Hi
> > 
> > "make world" is broken in libc_r. Simple fix is to replace all
> > "socklen_t" with "int".
> 
> libc_r likes to pull data from /usr/include instead of the 
> source tree, "make includes" fixes this.  I'm not sure if
> that's the correct way to fix it though.

I've got a change in the pipeline that will cause world breakage again,
unless we do something about this.  Is there anything wrong with simply
adding:

CFLAGS+=-I${.CURDIR}/../../include

to lib/libc_r/Makefile?  It fixes such build problems.

Jason


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



Re: make world broken

1999-12-17 Thread Jos Backus

On Fri, Dec 17, 1999 at 04:30:16PM -0700, Darren Wiebe wrote:
> I just built the world from sources about 3-4 hours ago.  It was all
> great.

Fwiw, I just got the same error on another system, cvsupped this morning.

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


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



Re: make world broken

1999-12-16 Thread Darren Wiebe

Jos Backus wrote:

I just built the world from sources about 3-4 hours ago.  It was all
great.

Darren Wiebe
[EMAIL PROTECTED]

> 
> cd /usr/src/gnu/usr.bin/cc/f771; make build-tools
> cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T
> ARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/us
> r/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools
>  -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/c
> c/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../..
> /contrib/gcc/f -I.   -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/f
> ini.c
> In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro
> j.h:28,
>  from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin
> i.c:24:
> /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h:
> No such file or directory
> In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/sys
> tem.j:25,
>  from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro
> j.h:32,
>  from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin
> i.c:24:
> /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting t
> ypes for `sys_errlist'
> /usr/include/stdio.h:225: previous declaration of `sys_errlist'
> /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error
> before `PVPROTO'
> *** Error code 1
> 
> Stop in /usr/src/gnu/usr.bin/cc/f771.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> --
> Jos Backus  _/ _/_/_/  "Reliability means never
>_/ _/   _/   having to say you're sorry."
>   _/ _/_/_/ -- D. J. Bernstein
>  _/  _/ _/_/
> [EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;
> 
> 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: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-16 Thread Daniel C. Sobral

David Scheidt wrote:
> 
> What's wrong with run with system V runlevels?  Other than it's system V and
> everything AT^HUSL did is evil, of course.

They try to map graphs into a line.

--
Daniel C. Sobral(8-DCS)
who is as social as a wampas

[EMAIL PROTECTED]
[EMAIL PROTECTED]



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



make world broken

1999-12-16 Thread Jos Backus

cd /usr/src/gnu/usr.bin/cc/f771; make build-tools
cc -O -pipe -march=pentium -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H -DDEFAULT_T
ARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" -I/us
r/src/gnu/usr.bin/cc/f771/../cc_tools -I/usr/src/gnu/usr.bin/cc/f771/../cc_tools
 -I/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc -I/usr/src/gnu/usr.bin/c
c/f771/../../../../contrib/gcc/config -I/usr/src/gnu/usr.bin/cc/f771/../../../..
/contrib/gcc/f -I.   -c /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/f
ini.c
In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro
j.h:28,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin
i.c:24:
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/hconfig.j:25: hconfig.h:
No such file or directory
In file included from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/sys
tem.j:25,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/pro
j.h:32,
 from /usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/f/fin
i.c:24:
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:348: conflicting t
ypes for `sys_errlist'
/usr/include/stdio.h:225: previous declaration of `sys_errlist'
/usr/src/gnu/usr.bin/cc/f771/../../../../contrib/gcc/system.h:394: syntax error
before `PVPROTO'
*** Error code 1

Stop in /usr/src/gnu/usr.bin/cc/f771.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


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



make world [bsd.info.mk] - patch ?

1999-12-16 Thread Brian Somers

Hi,

I can only assume that I'm doing something strange locally, but I've 
now got two machines that do this, and my third -current machine 
hasn't been installworld'd in a while

The problem is that I can't ``make install'' any info files... I get 
something like:

$ make clean && make depend && make && sudo make install
.[make looks fine].
===> doc
sflag=`grep -q ^INFO-DIR-SECTION com_err.info || echo 1`;  eflag=`grep -q 
^START-INFO-DIR-ENTRY com_err.info || echo 1`;  install-info  
${sflag:+--section="Programming & development tools."}  ${eflag:+--entry="* 
libcom_err: (com_err).A Common Error Description Library for UNIX."}  
com_err.info /usr/share/info/dir
install-info: Undefined error: 0 for /usr/share/info/dir
*** Error code 1

Stop in /usr/src/lib/libcom_err/doc.
*** Error code 1

Stop in /usr/src/lib/libcom_err.


>From what I can tell, this shouldn't work anyway but the attached 
patch fixes things.

Am I missing something ?

Cheers.


cvs diff: Diffing .
Index: bsd.info.mk
===
RCS file: /home/ncvs/src/share/mk/bsd.info.mk,v
retrieving revision 1.56
diff -u -r1.56 bsd.info.mk
--- bsd.info.mk 1999/08/28 00:21:46 1.56
+++ bsd.info.mk 1999/12/16 07:27:58
@@ -32,7 +32,7 @@
 # INFODIR  Base path for GNU's hypertext system
 #  called Info (see info(1)). [${SHAREDIR}/info]
 #
-# INFODIRFILE  Top level node/index for info files. [dir]
+# INFODIRFILE  Top level node/index for info files. [$INFO.info.gz]
 #
 # INFOGRP  Info group. [${SHAREGRP}]
 #
@@ -86,7 +86,7 @@
 MAKEINFO?= makeinfo
 MAKEINFOFLAGS+=--no-split # simplify some things, e.g., compression
 SRCDIR?=   ${.CURDIR}
-INFODIRFILE?=   dir
+INFODIRFILE?=  ${INFO:S/$/.info.gz/}
 INFOTMPL?=  ${INFODIR}/dir-tmpl
 INSTALLINFO?=   install-info
 INFOSECTION?=   Miscellaneous

-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
     <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour !  <[EMAIL PROTECTED]>




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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-16 Thread Jos Backus

On Thu, Dec 16, 1999 at 12:07:49AM +0100, Poul-Henning Kamp wrote:
> I would prefer if the lines could be added to /etc/ttys somewhat
> like:
>   sshd "/usr/local/sbin/sshd" none ondemand
> 
> And then we could
>   telinit -on sshd
>   telinit -off sshd

hal:/service# ls -l telnetd
total 2
-rwxr-xr-x  1 root  wheel   64 Sep 20 11:34 run
drwx--  2 root  wheel  512 Dec 14 16:09 supervise
hal:/service# cat telnetd/run
#!/bin/sh
exec \
tcpserver -RH -D 0 telnet /usr/libexec/telnetd
hal:/service# svstat telnetd
telnetd: up (pid 224)
hal:/service# svc -d telnetd
hal:/service# svstat telnetd
telnetd: down, normally up
hal:/service# svc -u telnetd
hal:/service# svstat telnetd
telnetd: up (pid 40965)

init's role is assumed by a program named svscan. Of course, svscan not being
init, it cannot control daemons that background themselves.

http://cr.yp.to/daemontools.html

-- 
Jos Backus  _/ _/_/_/  "Reliability means never
   _/ _/   _/   having to say you're sorry."
  _/ _/_/_/ -- D. J. Bernstein
 _/  _/ _/_/
[EMAIL PROTECTED]  _/_/  _/_/_/  use Std::Disclaimer;


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



Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-16 Thread Rodney W. Grimes

> On Thu, Dec 16, 1999 at 01:22:46AM -0500, Donn Miller wrote:
> 
>  > runlevels, OpenBSD does not or goes with an entirely different
>  > system), them would it be fair to consider FreeBSD "BSD"?  The
>  > advantage here is that FreeBSD would mature into it's own type of
>  > UNIX with a BSD heritage.
>  
> Can we please not have this thread again?  Anyone who is interested
> in following up on anything whatsoever to do with SysV runlevels 
> should first familiarize themselves with the numerous problems they
> have which have been hashed out on the lists several times over the
> last 12 months (hint:  to to the mail archive search engine at 
> www.freebsd.org and search for "runlevel").

Only correction here is ``over the last 7 years'' not ``12 months''.  This
will be atleast the 4th time we have been over this...


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


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



Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-15 Thread Mark Newton

On Thu, Dec 16, 1999 at 01:22:46AM -0500, Donn Miller wrote:

 > runlevels, OpenBSD does not or goes with an entirely different
 > system), them would it be fair to consider FreeBSD "BSD"?  The
 > advantage here is that FreeBSD would mature into it's own type of
 > UNIX with a BSD heritage.
 
Can we please not have this thread again?  Anyone who is interested
in following up on anything whatsoever to do with SysV runlevels 
should first familiarize themselves with the numerous problems they
have which have been hashed out on the lists several times over the
last 12 months (hint:  to to the mail archive search engine at 
www.freebsd.org and search for "runlevel").

- mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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



Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-15 Thread Donn Miller

David Scheidt wrote:

> What's wrong with run with system V runlevels?  Other than it's system V and
> everything AT^HUSL did is evil, of course.

Well, the one danger is that we'd be slowly drifting away from
the classic BSD way of doing thigs.  Of course, the official BSD
is dead (right?).  But OTOH, we want to carry FreeBSD forward, so
if that means we have to incorporate some SysVisms, then so be
it.  After all, SysV borrowed some things from BSD.

The second question I have is, do we try to stay on par with what
Open/NetBSD are doing?  Should we stick together, synchronise our
efforts, and try to define what comprises "BSD"?  Or, do we let
the 3 BSDs diverge completely?

Well, if the 3 diverge too far (ex:  FreeBSD implements SysV
runlevels, OpenBSD does not or goes with an entirely different
system), them would it be fair to consider FreeBSD "BSD"?  The
advantage here is that FreeBSD would mature into it's own type of
UNIX with a BSD heritage.

- Donn


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



make world breakage

1999-12-15 Thread Clive Lin

FreeBSD current source cvsuped about 2 hrs ago:

===> gnu/usr.bin/binutils/ld
cc -Os -pipe -mpentiumpro -march=pentiumpro -D_GNU_SOURCE -I- -I. 
-I/usr/src/gnu/usr.bin/binutils/ld/i386 -I/usr/src/gnu/usr.bin/binutils/ld 
-I/usr/src/gnu/usr.bin/binutils/ld/../libbfd/i386 
-I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/include 
-DDEFAULT_EMULATION=\"elf_i386\" -DTARGET=\"i386-unknown-freebsdelf\" 
-DSCRIPTDIR=\"/usr/obj/usr/src/i386/usr/libdata\" 
-I/usr/src/gnu/usr.bin/binutils/ld/../../../../contrib/binutils/ld   
-I/usr/obj/usr/src/i386/usr/include -c eelf_i386.c
eelf_i386.c:133: warning: initialization makes integer from pointer without a cast
eelf_i386.c:133: initializer element is not constant
eelf_i386.c:133: warning: data definition has no type or storage class
eelf_i386.c:134: syntax error before `if'
cpp: output pipe has been closed
*** Error code 1

Stop in /usr/src/gnu/usr.bin/binutils/ld.
*** Error code 1

Stop in /usr/src/gnu/usr.bin/binutils.
*** Error code 1

Stop in /usr/src/gnu/usr.bin.
*** Error code 1

Stop in /usr/src/gnu.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
# root@cartier /usr/src>

-- 
CirX 
Clive Lin <[EMAIL PROTECTED]>

FreeBSD - The Power to Serve 


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



Re: Today's make world breakage

1999-12-15 Thread David O'Brien

On Wed, Dec 15, 1999 at 02:10:43PM -0500, Forrest Aldrich wrote:
> cpp: }: No such file or directory
> cpp: }: No such file or directory
> mkdep: compile failed
> *** Error code 1


Fixed.  Thanks for the report.

-- 
-- David([EMAIL PROTECTED])


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Peter Jeremy

On 1999-Dec-16 10:07:49 +1100, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
>In message <[EMAIL PROTECTED]>, Peter Jeremy writes
>:
>>It can do that now.  Add the following lines to /etc/ttys:
>>
>>sshd  "/usr/local/sbin/sshd" none on
>>inetd "/usr/sbin/inetd -Ww" none on
>>syslogd   "/usr/sbin/syslogd" none on
>>
>>(This ability has always been present, but is now documented).
>
>Yes, but apart from the highly unintuitive name "/etc/ttys"

I agree that it's non-intuitive, but I doubt that any attempt to
change the name would survive very long.

>I would prefer if the lines could be added to /etc/ttys somewhat
>like:
>   sshd "/usr/local/sbin/sshd" none ondemand
>
>And then we could
>   telinit -on sshd
>   telinit -off sshd

This looks nice.  The major problem I see is coming up with a secure
mechanism for passing the daemon name from telinit to init.  (And the
issue of whether the state should be persistent over reboots - which
is regularly hashed to death whenever DEVFS comes up).

And, whilst it's even less intuitive than /etc/ttys, we already have
equivalent functionality now (assuming you have an entry in /dev for
a non-existent device).  The state in /etc/ttys always is `on'.

Using sshd as an example:

To enable:
rm -f /dev/sshd
kill -HUP 1

To disable:
ln -s /dev/some_device_that_isnt_configured /dev/sshd
kill -HUP 1

(This works because init will always try to open /dev/sshd.  If
the open returns ENXIO, it will skip that line.  If the open
succeeds, or fails with any other error (ie ENOENT) the line
is accepted).

Peter


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Peter Jeremy writes
:
>On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
>>And we don't really need YAD when we have init hanging around doing
>>nothing for its keep anyway...
>
>I beg to differ.  To quote init(8):
> The role of init is so critical that if it dies, the system will reboot
> itself automatically.  If, at bootstrap time, the init process cannot be
> located, the system will panic with the message ``panic: init died
> (signal %d, exit %d)''.
>
>This suggests that init needs to be very robust - which generally
>translates to `small and well audited'.  Non-core functionality
>(which IMHO includes devd) really belongs in another process.

Well, there are a lot of chicken & eggs issues with devd, which
may skew that a bit, but lets examine that when we get there.

>>and at the same time I wouldn't mind if init were taught to keep
>>important programs running, things like sshd, inetd, syslogd and
>>similar should be restarted if they die.
>
>It can do that now.  Add the following lines to /etc/ttys:
>
>sshd   "/usr/local/sbin/sshd" none on
>inetd  "/usr/sbin/inetd -Ww" none on
>syslogd"/usr/sbin/syslogd" none on
>
>(This ability has always been present, but is now documented).

Yes, but apart from the highly unintuitive name "/etc/ttys" any
process which involves edititing a file and signalling a process
has a big potential for races.

I would prefer if the lines could be added to /etc/ttys somewhat
like:
sshd "/usr/local/sbin/sshd" none ondemand

And then we could
telinit -on sshd
telinit -off sshd

or similar.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Peter Jeremy

On 1999-Dec-16 07:48:48 +1100, Poul-Henning Kamp <[EMAIL PROTECTED]> wrote:
>And we don't really need YAD when we have init hanging around doing
>nothing for its keep anyway...

I beg to differ.  To quote init(8):
 The role of init is so critical that if it dies, the system will reboot
 itself automatically.  If, at bootstrap time, the init process cannot be
 located, the system will panic with the message ``panic: init died
 (signal %d, exit %d)''.

This suggests that init needs to be very robust - which generally
translates to `small and well audited'.  Non-core functionality
(which IMHO includes devd) really belongs in another process.

Looking at the development side, it's also painful to debug init -
another reason for leaving it alone.

>and at the same time I wouldn't mind if init were taught to keep
>important programs running, things like sshd, inetd, syslogd and
>similar should be restarted if they die.

It can do that now.  Add the following lines to /etc/ttys:

sshd"/usr/local/sbin/sshd" none on
inetd   "/usr/sbin/inetd -Ww" none on
syslogd "/usr/sbin/syslogd" none on

(This ability has always been present, but is now documented).

Peter


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



Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-15 Thread David Scheidt

On Wed, 15 Dec 1999, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, Dav
> id Scheidt writes:
> >What's wrong with run with system V runlevels?  Other than it's system V and
> >everything AT^HUSL did is evil, of course.   
> 
> runlevels are a very oldfashioned way to think about things, I don't
> want to have one big button which is called "NETWORKING ON/OFF".

runlevels let you do more than just run gettys, control networking, and run
/sbin/rc?.d scripts.  We do.

David Scheidt



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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Matthew Jacob


> But lets say you add a pccard on which you want a getty, so devd will
> have to tell init to run a getty on that port wouldn't it ?

Of course- but this lays out very clearly where breakage
could occur and leads to be better flexibility. Let's assume this is devd
and leave to the side whether devfs would or would not be better.

a. insert card
b.  card recognized (8 new tty ports)

c. devd awakened
d.  (re)makes /dev nodes
e.  updates /etc/ttys [ this is a debatable step ]
f.  notifies init (kill(1,1))

g. init awakens
h.  rescans /etc/ttys
i.  spawns new gettys, kills dead ones (the old rmut hat dance)


Groups a-b, c-f, g-i, are separable steps with pretty clear audit trail
stops as to how things could go.

Let's take another more complicated example:

a. SAN Fabric SCN (change notify) is received by Qlogic FC-AL driver.
b.  Fabric Nameserver rescanned- 32 new disks arrived, 8 disks left.
c.  ASYNC notification upcall to CAM is made [ this is as yet an 
undesigned area, but assume that does like what a camcontrol
rescan now does (or is supposed to)- new disks get assigned new
instance numbers, dead disks are either safely removed of pack
invalidation occurs if they were still open ]

d. devd awakened
e.  (re)makes /dev nodes
f.  [ VARIABLE HOOK HERE- POLICY LEFT OPEN ]

g1. vinum awakened, yatta yatta yatta

g2. VxVM (Veritas Volume Manager) awakened, yatta yatta yatta

g3. Specified perl script activated, (auto disklabel, newfs, mount)

...

Again, Groups a-b and d-f are separable steps with pretty clear audit
trail stops. It's not quite clear what step G should be, or whether it
should be left to 3rd party hooks, but it's pretty clear to me that
putting volume management in init makes no sense whatsoever. For things
like what init itself manages (tty lines), sure it does. Otherwise, no.


-matt





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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Matthew
 Jacob writes:
>> >
>> >I was just thinking it could get tricky and have subtle ordering bugs of
>> >new tty devices, changes to ttys and signals all about the same time.
>> 
>> Well, they are no less subtle by having them in different processes...
>
>No, but possibly easier to track and debug. Just a minor nit. N'mind...

But lets say you add a pccard on which you want a getty, so devd will
have to tell init to run a getty on that port wouldn't it ?

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Dav
id Scheidt writes:
>On Wed, 15 Dec 1999, Poul-Henning Kamp wrote:
>
>> In message <[EMAIL PROTECTED]>, Warner Losh writes:
>> 
>> I would really like to see the devd functionality to live in init
>> and at the same time I wouldn't mind if init were taught to keep
>> important programs running, things like sshd, inetd, syslogd and
>> similar should be restarted if they die.
>> 
>> No, I don't want sysV runlevels or the weird shit AIX has.  I'm sure
>> a clean and sensible way can be found, if some mental energies are
>> poured into the problem.
>
>What's wrong with run with system V runlevels?  Other than it's system V and
>everything AT^HUSL did is evil, of course.   

runlevels are a very oldfashioned way to think about things, I don't
want to have one big button which is called "NETWORKING ON/OFF".

We need to be able to dynamically say "keep this puppy alive" and
later "ok, forget about that one from now on".

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Matthew Jacob

> >
> >I was just thinking it could get tricky and have subtle ordering bugs of
> >new tty devices, changes to ttys and signals all about the same time.
> 
> Well, they are no less subtle by having them in different processes...

No, but possibly easier to track and debug. Just a minor nit. N'mind...




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



Init Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) ) )

1999-12-15 Thread David Scheidt

On Wed, 15 Dec 1999, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> 
> I would really like to see the devd functionality to live in init
> and at the same time I wouldn't mind if init were taught to keep
> important programs running, things like sshd, inetd, syslogd and
> similar should be restarted if they die.
> 
> No, I don't want sysV runlevels or the weird shit AIX has.  I'm sure
> a clean and sensible way can be found, if some mental energies are
> poured into the problem.

What's wrong with run with system V runlevels?  Other than it's system V and
everything AT^HUSL did is evil, of course.   

David



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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Matthew
 Jacob writes:
>> >Isn't this throwing an awful lot onto init?
>> 
>> Not really...
>> 
>> The meta-daemon part is no different from keeping gettys in the air...
>> 
>> The devd thing consists of selecting on some magic fd and running a
>> program when something happens.  This could be done with a getty
>> like daemon too of course.
>
>I was just thinking it could get tricky and have subtle ordering bugs of
>new tty devices, changes to ttys and signals all about the same time.

Well, they are no less subtle by having them in different processes...

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Matthew Jacob

> >Isn't this throwing an awful lot onto init?
> 
> Not really...
> 
> The meta-daemon part is no different from keeping gettys in the air...
> 
> The devd thing consists of selecting on some magic fd and running a
> program when something happens.  This could be done with a getty
> like daemon too of course.

I was just thinking it could get tricky and have subtle ordering bugs of
new tty devices, changes to ttys and signals all about the same time.




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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Matthew
 Jacob writes:
>> 
>
>> I would really like to see the devd functionality to live in init
>> and at the same time I wouldn't mind if init were taught to keep
>> important programs running, things like sshd, inetd, syslogd and
>> similar should be restarted if they die.
>> 
>> No, I don't want sysV runlevels or the weird shit AIX has.  I'm sure
>> a clean and sensible way can be found, if some mental energies are
>> poured into the problem.
>> 
>
>Isn't this throwing an awful lot onto init?

Not really...

The meta-daemon part is no different from keeping gettys in the air...

The devd thing consists of selecting on some magic fd and running a
program when something happens.  This could be done with a getty
like daemon too of course.


--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Matthew Jacob

> 

> I would really like to see the devd functionality to live in init
> and at the same time I wouldn't mind if init were taught to keep
> important programs running, things like sshd, inetd, syslogd and
> similar should be restarted if they die.
> 
> No, I don't want sysV runlevels or the weird shit AIX has.  I'm sure
> a clean and sensible way can be found, if some mental energies are
> poured into the problem.
> 

Isn't this throwing an awful lot onto init?




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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Warner Losh writes:
>In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
>: A "devd" program would solve 98% of what devfs could solve.  It cannot
>: solve the homebrew-a-vnode-for-the-root-fs problem.  FreeBSD needs a
>: "devd" program *anyway* because what good is dynamic devices if you
>: can't do something intelligent with them when they appear (mount/ifconfig
>: etc etc etc).
>
>Yes.  I'd like to see this in the future.  There is no reason to have
>pccardd after the cut over to the new code.  I don't think there is a
>reason to have both devd and usbd.  They all just do things when
>devices come and go.

And we don't really need YAD when we have init hanging around doing
nothing for its keep anyway...

I would really like to see the devd functionality to live in init
and at the same time I wouldn't mind if init were taught to keep
important programs running, things like sshd, inetd, syslogd and
similar should be restarted if they die.

No, I don't want sysV runlevels or the weird shit AIX has.  I'm sure
a clean and sensible way can be found, if some mental energies are
poured into the problem.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Warner Losh

In message <[EMAIL PROTECTED]> Poul-Henning Kamp writes:
: A "devd" program would solve 98% of what devfs could solve.  It cannot
: solve the homebrew-a-vnode-for-the-root-fs problem.  FreeBSD needs a
: "devd" program *anyway* because what good is dynamic devices if you
: can't do something intelligent with them when they appear (mount/ifconfig
: etc etc etc).

Yes.  I'd like to see this in the future.  There is no reason to have
pccardd after the cut over to the new code.  I don't think there is a
reason to have both devd and usbd.  They all just do things when
devices come and go.

Warner


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



Re: make world broken building fortunes

1999-12-15 Thread Peter Jeremy

On 1999-Dec-15 19:57:49 +1100, Sheldon Hearn <[EMAIL PROTECTED]> wrote:
>> -gnu/usr.bin/bison gnu/usr.bin/cc
>> +gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo
>
>Presumably this hunk is a stray fix for something other than the fortune
>database? :-)

Yes it is.  I was having problems with buildworld dying in makeinfo.
I've since done some more checking and found a stray (and ancient)
makeinfo lying around - it appears to have been installed by an
old teTeX port.

Ignore that hunk.

Peter


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



Re: Today's make world breakage

1999-12-15 Thread Tom Bartol


Ditto here.

Tom


On Wed, 15 Dec 1999, Forrest Aldrich wrote:

> FYI just CVSup'd and got this:
> 
> 
> 
> X-UIDL: 495287ccf607850cc65e4c59c7b49751
> 
> cd /usr/src/lib/librpcsvc;  make beforeinstall
> cd /usr/src/lib/libskey;make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h  
>/usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libstand;   make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 
>/usr/src/lib/libstand/stand.h  /usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libtacplus; make beforeinstall
> sh /usr/src/tools/install.sh -c -o root -g wheel -m 444  
>/usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libcom_err; make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
>/usr/src/lib/libcom_err/../../contrib/com_err/com_err.h 
>/usr/src/lib/libcom_err/../../contrib/com_err/com_right.h  
>/usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libss;  make -B hdrs beforeinstall
> test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et .
> compile_et ss_err.et
> test -h ss_err.et && rm -f ss_err.et
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h  
>ss_err.h /usr/obj/usr/src/i386/usr/include/ss
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 
>/usr/src/lib/libss/copyright.h  
>/usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h
> cd /usr/src/lib/libutil;make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 
>/usr/src/lib/libutil/libutil.h  /usr/obj/usr/src/i386/usr/include
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 
>/usr/src/lib/libutil/login_cap.h  /usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libvgl; make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h  
>/usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libwrap;make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
>/usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h  
>/usr/obj/usr/src/i386/usr/include
> cd /usr/src/lib/libz;   make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h  
>/usr/obj/usr/src/i386/usr/include
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h  
>/usr/obj/usr/src/i386/usr/include
> cd /usr/src/usr.bin/lex;make beforeinstall
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 644  
>/usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++
> 
> --
>  >>> Building libraries
> --
> cd /usr/src; 
>COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin  
>LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib  
>OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
>PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503  MAKEOBJDIRPREFIX=/usr/obj  
>DESTDIR=/usr/obj/usr/src/i386  INSTALL="sh /usr/src/tools/install.sh"  
>PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin
> make -f Makefile.inc1 -DNOINFO -DNOMAN libraries
> cd /usr/src/lib/csu/i386-elf;  make depend;  make all;  make install
> rm -f .depend
> mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include
>/usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S
> cpp: }: No such file or directory
> cpp: }: No such file or directory
> mkdep: compile failed
> *** Error code 1
> 
> Stop in /usr/src/lib/csu/i386-elf.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> *** Error code 1
> 
> Stop in /usr/src.
> 
> 
> 
> 
> 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



Today's make world breakage

1999-12-15 Thread Forrest Aldrich

FYI just CVSup'd and got this:



X-UIDL: 495287ccf607850cc65e4c59c7b49751

cd /usr/src/lib/librpcsvc;  make beforeinstall
cd /usr/src/lib/libskey;make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libskey/skey.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libstand;   make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libstand/stand.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libtacplus; make beforeinstall
sh /usr/src/tools/install.sh -c -o root -g wheel -m 444  
/usr/src/lib/libtacplus/taclib.h /usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libcom_err; make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
/usr/src/lib/libcom_err/../../contrib/com_err/com_err.h 
/usr/src/lib/libcom_err/../../contrib/com_err/com_right.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libss;  make -B hdrs beforeinstall
test -e ss_err.et || ln -s /usr/src/lib/libss/ss_err.et .
compile_et ss_err.et
test -h ss_err.et && rm -f ss_err.et
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/ss.h  
ss_err.h /usr/obj/usr/src/i386/usr/include/ss
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libss/copyright.h 
 /usr/obj/usr/src/i386/usr/include/ss/mit-sipb-copyright.h
cd /usr/src/lib/libutil;make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libutil/libutil.h 
 /usr/obj/usr/src/i386/usr/include
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 
/usr/src/lib/libutil/login_cap.h  /usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libvgl; make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libvgl/vgl.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libwrap;make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444  
/usr/src/lib/libwrap/../../contrib/tcp_wrappers/tcpd.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/lib/libz;   make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zconf.h  
/usr/obj/usr/src/i386/usr/include
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 /usr/src/lib/libz/zlib.h  
/usr/obj/usr/src/i386/usr/include
cd /usr/src/usr.bin/lex;make beforeinstall
sh /usr/src/tools/install.sh -C -o root -g wheel -m 644  
/usr/src/usr.bin/lex/FlexLexer.h /usr/obj/usr/src/i386/usr/include/g++

--
 >>> Building libraries
--
cd /usr/src; 
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin  
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib  
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503  MAKEOBJDIRPREFIX=/usr/obj  
DESTDIR=/usr/obj/usr/src/i386  INSTALL="sh /usr/src/tools/install.sh"  
PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/X11R6/bin:/usr/local/samba/bin:/usr/local/home/forrie/bin
 make -f Makefile.inc1 -DNOINFO -DNOMAN libraries
cd /usr/src/lib/csu/i386-elf;  make depend;  make all;  make install
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include
/usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S
cpp: }: No such file or directory
cpp: }: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /usr/src/lib/csu/i386-elf.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.




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



make world breakage

1999-12-15 Thread Steve Kargl

FreeBSD-current source cvsup'd at 1034pst on 991215.

--
>>> Building libraries
--
cd /usr/src; 
COMPILER_PATH=/usr/obj/usr/src/i386/usr/libexec:/usr/obj/usr/src/i386/usr/bin  
LIBRARY_PATH=/usr/obj/usr/src/i386/usr/lib:/usr/obj/usr/src/i386/usr/lib  
OBJFORMAT_PATH=/usr/obj/usr/src/i386/usr/libexec  
PERL5LIB=/usr/obj/usr/src/i386/usr/libdata/perl/5.00503  MAKEOBJDIRPREFIX=/usr/obj  
DESTDIR=/usr/obj/usr/src/i386  INSTALL="sh /usr/src/tools/install.sh"  
PATH=/usr/obj/usr/src/i386/bin:/usr/obj/usr/src/i386/usr/bin:/root/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/bin:/usr/local/libexec:/root/Office40/bin
 make -f Makefile.inc1 -DNOINFO -DNOMAN libraries
cd /usr/src/lib/csu/i386-elf;  make depend;  make all;  make install
rm -f .depend
mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include
/usr/src/lib/csu/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S
cpp: }: No such file or directory
cpp: }: No such file or directory
mkdep: compile failed
*** Error code 1
1 error
*** Error code 2
1 error
*** Error code 2

-- 
Steve


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world brokenbuilding fortunes ) )

1999-12-15 Thread Matthew Jacob



On Wed, 15 Dec 1999, Poul-Henning Kamp wrote:

> In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
> >"Rodney W. Grimes" wrote:
> >> 
> >> Yea... been hearing that for 4 years... one of it's big short comings is
> >> that it needs a persistent backing store for this.  Sounds like this C
> >> program could fullfill one of the missing parts of devfs :-)
> 
> A "devd" program would solve 98% of what devfs could solve.  It cannot
> solve the homebrew-a-vnode-for-the-root-fs problem.  FreeBSD needs a
> "devd" program *anyway* because what good is dynamic devices if you
> can't do something intelligent with them when they appear (mount/ifconfig
> etc etc etc).

I mostly agree with you. I tend to also not worry terribly much about
root-fs type issues, except that I keep being told by *my* customers that
this is what they want, particularly for large SANs.




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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes:
>"Rodney W. Grimes" wrote:
>> 
>> Yea... been hearing that for 4 years... one of it's big short comings is
>> that it needs a persistent backing store for this.  Sounds like this C
>> program could fullfill one of the missing parts of devfs :-)

A "devd" program would solve 98% of what devfs could solve.  It cannot
solve the homebrew-a-vnode-for-the-root-fs problem.  FreeBSD needs a
"devd" program *anyway* because what good is dynamic devices if you
can't do something intelligent with them when they appear (mount/ifconfig
etc etc etc).


--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-15 Thread Daniel C. Sobral

"Rodney W. Grimes" wrote:
> 
> Yea... been hearing that for 4 years... one of it's big short comings is
> that it needs a persistent backing store for this.  Sounds like this C
> program could fullfill one of the missing parts of devfs :-)

F persistent backing store. The daemon solution is perfectly fine.

--
Daniel C. Sobral(8-DCS)
who is as social as a wampas

[EMAIL PROTECTED]
[EMAIL PROTECTED]



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



Re: make world broken building fortunes

1999-12-15 Thread Sheldon Hearn



On Wed, 15 Dec 1999 06:21:48 +1100, Peter Jeremy wrote:

> @@ -344,7 +352,7 @@
>  tools::
>  .for _tool in ${_strfile} ${_aout_tools} usr.bin/gensetdefs \
>  gnu/usr.bin/binutils usr.bin/objformat usr.bin/yacc usr.bin/colldef \
> -gnu/usr.bin/bison gnu/usr.bin/cc
> +gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo
>   cd ${.CURDIR}/${_tool}; \
>   ${MAKE} obj; \
>   ${MAKE} depend; \

Presumably this hunk is a stray fix for something other than the fortune
database? :-)

Ciao,
Sheldon.


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-14 Thread Warner Losh

In message <[EMAIL PROTECTED]> Brian Somers writes:
: *cough*DEVFS*cough*

devfs*D*

Warner


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



Re: RE: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Matthew Dillon


:
:Poul-Henning Kamp wrote
:> It would make more sense, considering the way FreeBSD is distributed for
:> /usr/local to be a mountpoint than for /usr to be a mountpoint.
:>
:> /var is traditionally a mountpoint to keep the logs out of harms
:> way (and vice versa), but /usr never had that level of justification.
:>
:
:one idea about /usr is to allow the admin to mount it read-only.

I tend to make /usr a separate mount point for one reason and one
reason only:  So root (/) can be made a small partition (64-128M) and 
thus be less likely to get corrupted beyond repair in a crash.

-Matt



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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-14 Thread Mark Newton

On Wed, Dec 15, 1999 at 01:39:28AM +, Brian Somers wrote:

 > [.]
 > > On a related subject: don't you think it's high time to end up this
 > > madness with MAKEDEV being a shell script, and reimplement it in C? Today,
 > [.]
 > *cough*DEVFS*cough*

Gesunteit.

   - mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-14 Thread Rodney W. Grimes

> [.]
> > On a related subject: don't you think it's high time to end up this
> > madness with MAKEDEV being a shell script, and reimplement it in C? Today,
> [.]
> *cough*DEVFS*cough*

Yea... been hearing that for 4 years... one of it's big short comings is
that it needs a persistent backing store for this.  Sounds like this C
program could fullfill one of the missing parts of devfs :-)


-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


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



Re: MAKEDEV (Re: Speaking of moving files (Re: make world broken building fortunes ) )

1999-12-14 Thread Brian Somers

[.]
> On a related subject: don't you think it's high time to end up this
> madness with MAKEDEV being a shell script, and reimplement it in C? Today,
[.]
*cough*DEVFS*cough*
-- 
Brian <[EMAIL PROTECTED]><[EMAIL PROTECTED]>
     <[EMAIL PROTECTED]>
Don't _EVER_ lose your sense of humour !  <[EMAIL PROTECTED]>




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



MAKEDEV (Re: Speaking of moving files (Re: make world broken buildingfortunes ) )

1999-12-14 Thread Andrzej Bialecki

On Mon, 13 Dec 1999, Bill Fumerola wrote:

> On Mon, 13 Dec 1999, Louis A. Mamakos wrote:
> 
> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
> > just the root file system mounted?   
> 
> As one who just got his ass bitten by this, I would vote yes.

On a related subject: don't you think it's high time to end up this
madness with MAKEDEV being a shell script, and reimplement it in C? Today,
MAKEDEV uses about 10 external programs, it's inflexible and complicated,
but the task it's doing could be relatively easily ported to C plus config
file. Have you ever tried to use it in nonstandad location, or on a
minimal system? The end result is usually an unpleasant surprise...

Andrzej Bialecki

//  <[EMAIL PROTECTED]> WebGiro AB, Sweden (http://www.webgiro.com)
// ---
// -- FreeBSD: The Power to Serve. http://www.freebsd.org 
// --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ 




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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Lyndon Nerenberg

> "BSDman" == BSDman  <[EMAIL PROTECTED]> writes:

BSDman> one idea about /usr is to allow the admin to mount it
BSDman> read-only.  I didn't tried it but this would give some
BSDman> level of security against modifications of the files there
BSDman> in.

This is particulary useful in a lab environment where you have xx
workstations with local root, var, and swap NFS mounting an RO /usr.

--lyndon


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



RE: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread BSDman



Poul-Henning Kamp wrote
> It would make more sense, considering the way FreeBSD is distributed for
> /usr/local to be a mountpoint than for /usr to be a mountpoint.
>
> /var is traditionally a mountpoint to keep the logs out of harms
> way (and vice versa), but /usr never had that level of justification.
>

one idea about /usr is to allow the admin to mount it read-only.
I didn't tried it but this would give some level of security against
modifications
of the files there in.

> It is getting even less justifiable as time progress.  The last
> sensible argument we had for it was the "load the filesystem from
> the first 1024 cylinders or bust" problem.

I think the "cylinder" limitation is still of concern. If all OSes come
with large root paritions, installing many of them on the same host would be
a nightmare.


Regards,

mouss

Free your Net with BSD



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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Blaz Zupan

> How about removing awk from MAKEDEV so life isn't so hard to recover
> when you use a 3.3 fixit floppy after removing /dev and not making
> enough of it again.

How about finally starting to work on devfs and forget about all the
MAKEDEV junk and leave it as it is for now?

Blaz Zupan, [EMAIL PROTECTED], http://home.amis.net/blaz/
Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia



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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Wilko Bulte

On Tue, Dec 14, 1999 at 07:38:32PM +0100, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
> >
> >I think at one time or another all of us have missed *something* in
> >/usr that wasn't in /.  For example, disklabel -e doesn't work without
> >vi -- which is in /usr.
> 
>   EDITOR=/bin/ed
>   export EDITOR
>   disklabel -e
> 
> >But if we go down that path we are going to wind up with *every* binary
> >in /usr being moved to /, which is clearly wrong.
> 
> Dogmatically, yes.   Sensibly:  I'm not so sure.
> 
> It would make more sense, considering the way FreeBSD is distributed for
> /usr/local to be a mountpoint than for /usr to be a mountpoint.
> 
> /var is traditionally a mountpoint to keep the logs out of harms
> way (and vice versa), but /usr never had that level of justification.

It just has an historical justification. When /usr was another RK05
pack/drive.

-- 
Wilko Bulte Arnhem, The Netherlands   - The FreeBSD Project 
WWW : http://www.tcja.nl  http://www.freebsd.org


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Wilko Bulte

On Tue, Dec 14, 1999 at 10:32:23AM -0800, Matthew Dillon wrote:
> :> 
> :> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
> :> > just the root file system mounted?   
> :> 
> :> As one who just got his ass bitten by this, I would vote yes.
> :
> :As one who's missed chown at times when only root's mounted, I'm with Bill.
> :
> :--
> : Ben Rosengart
> :
> :UNIX Systems Engineer, Skunk Group
> :StarMedia Network, Inc.
> 
> I think at one time or another all of us have missed *something* in
> /usr that wasn't in /.  For example, disklabel -e doesn't work without
> vi -- which is in /usr.

Bad example:

yedi#EDITOR=ed disklabel -re da0
831
1,$p
# /dev/rda0c:
type: SCSI
disk: da0s2
label: 
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065

[etc]

yedi#type ed
ed is /bin/ed
yedi#

8)

-- 
Wilko Bulte Arnhem, The Netherlands   - The FreeBSD Project 
WWW : http://www.tcja.nl  http://www.freebsd.org


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



Re: make world broken building fortunes

1999-12-14 Thread Peter Jeremy

On 1999-Dec-13 20:42:36 +1100, Marcel Moolenaar <[EMAIL PROTECTED]> wrote:
>Index: Makefile.inc1
>===
>RCS file: /home/ncvs/src/Makefile.inc1,v
>retrieving revision 1.106
>diff -u -r1.106 Makefile.inc1
>--- Makefile.inc1   1999/12/12 22:24:08 1.106
>+++ Makefile.inc1   1999/12/13 09:40:16
>@@ -113,7 +113,7 @@
> OBJTREE=   ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH}
> .endif
> WORLDTMP=  ${OBJTREE}${.CURDIR}/${BUILD_ARCH}
>-STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
>+STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
> TMPPATH=   ${STRICTTMPPATH}:${PATH}

Taking into account Sheldon and Rodney's comments, together with
another few glitches (casear is also needed to build the ROT-13
fortune database and my existing makeinfo wasn't up to building
the gawk info files), I came up with the following:

Index: src/Makefile.inc1
===
RCS file: /home/CVSROOT/src/Makefile.inc1,v
retrieving revision 1.106
diff -u -r1.106 Makefile.inc1
--- Makefile.inc1   1999/12/12 22:24:08 1.106
+++ Makefile.inc1   1999/12/13 23:07:53
@@ -113,7 +113,14 @@
 OBJTREE=   ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH}
 .endif
 WORLDTMP=  ${OBJTREE}${.CURDIR}/${BUILD_ARCH}
+.if exists(${.CURDIR}/games) && !defined(NOGAMES)
+# /usr/games is needed for strfile and caesar, both of which are
+# required for building the fortune databases.
+STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
+.else
 STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
+.endif
+
 TMPPATH=   ${STRICTTMPPATH}:${PATH}
 
 # bootstrap/tools make
@@ -334,7 +341,8 @@
 # tools - Build tools needed to run the actual build.
 #
 .if exists(${.CURDIR}/games) && !defined(NOGAMES)
-_strfile=  games/fortune/strfile
+# strfile and caesar are needed to build the fortune database
+_strfile=  games/fortune/strfile games/caesar
 .endif
 
 .if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98"
@@ -344,7 +352,7 @@
 tools::
 .for _tool in ${_strfile} ${_aout_tools} usr.bin/gensetdefs \
 gnu/usr.bin/binutils usr.bin/objformat usr.bin/yacc usr.bin/colldef \
-gnu/usr.bin/bison gnu/usr.bin/cc
+gnu/usr.bin/bison gnu/usr.bin/cc gnu/usr.bin/texinfo
cd ${.CURDIR}/${_tool}; \
${MAKE} obj; \
${MAKE} depend; \
Index: src/games/fortune/datfiles/Makefile
===
RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v
retrieving revision 1.23
diff -u -r1.23 Makefile
--- Makefile1999/11/05 08:17:53 1.23
+++ Makefile1999/12/13 20:00:49
@@ -33,16 +33,13 @@
 
 .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy
 $f.dat: $f
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
strfile -Crs ${.ALLSRC} ${.TARGET}
 .endfor
 
 fortunes-o.dat: fortunes-o
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
strfile -Crsx ${.ALLSRC} ${.TARGET}
 
 fortunes-o: fortunes-o.${TYPE}
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \
caesar 13 < ${.ALLSRC} > ${.TARGET}
 
 .include 


I can now successfully do a -CURRENT buildworld on a system running
-CURRENT before the signal changes.

Peter


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread David Wolfskill

[Recipient list trimmed down to just the list.  dhw]

>Date: Tue, 14 Dec 1999 19:38:32 +0100
>From: Poul-Henning Kamp <[EMAIL PROTECTED]>

>

>It would make more sense, considering the way FreeBSD is distributed for
>/usr/local to be a mountpoint than for /usr to be a mountpoint.

It's hardly impossible for both to be mountpoints.  :-}

>/var is traditionally a mountpoint to keep the logs out of harms
>way (and vice versa), but /usr never had that level of justification.

>It is getting even less justifiable as time progress.  The last
>sensible argument we had for it was the "load the filesystem from
>the first 1024 cylinders or bust" problem.

Somehow, I'm getting a feeling of deja vu [sorry about the loss of
diacritical marks], reflecting on SunOS (both 4.x & 5.x), where /bin is
a symlink to /usr/bin, and /lib is a symlink to /usr/lib.

All of which reminds me of a singularly memorable time when I came in to
(then-)work, where I had my (personal) Sun 3/60 in use as my workstation,
and found that it had re-booted, but failed to switch to multi-user
mode.

Shortening this story, it turns out that /etc/fstab was no longer
present.  And it had been so long since I had paid any attention to the
filesystems, I didn't know what the name of the partition for /usr was.
And this was the only SunOS 4.x box in the shop.

So... I didn't have access to such user-level programs as "ls", for
example.

Shell built-ins, especially "echo", along with redirection (to fabricate
a skeleton /etc/fstab enough to get boot-strapped) saved the day... and
I learned a little.  :-}

Cheers,
david
-- 
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
voice: (650) 577-7158   pager: (888) 347-0197   FAX: (650) 372-5915


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Poul-Henning Kamp

In message <[EMAIL PROTECTED]>, Matthew Dillon writes:
>
>I think at one time or another all of us have missed *something* in
>/usr that wasn't in /.  For example, disklabel -e doesn't work without
>vi -- which is in /usr.

EDITOR=/bin/ed
export EDITOR
disklabel -e

>But if we go down that path we are going to wind up with *every* binary
>in /usr being moved to /, which is clearly wrong.

Dogmatically, yes.   Sensibly:  I'm not so sure.

It would make more sense, considering the way FreeBSD is distributed for
/usr/local to be a mountpoint than for /usr to be a mountpoint.

/var is traditionally a mountpoint to keep the logs out of harms
way (and vice versa), but /usr never had that level of justification.

It is getting even less justifiable as time progress.  The last
sensible argument we had for it was the "load the filesystem from
the first 1024 cylinders or bust" problem.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Ben Rosengart

On Tue, 14 Dec 1999, Matthew Dillon wrote:

> I think at one time or another all of us have missed *something* in
> /usr that wasn't in /.  For example, disklabel -e doesn't work without
> vi -- which is in /usr.

Good example of something else that would be great to have in /bin.

*ducking*

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Matthew Dillon

:> 
:> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
:> > just the root file system mounted?   
:> 
:> As one who just got his ass bitten by this, I would vote yes.
:
:As one who's missed chown at times when only root's mounted, I'm with Bill.
:
:--
: Ben Rosengart
:
:UNIX Systems Engineer, Skunk Group
:StarMedia Network, Inc.

I think at one time or another all of us have missed *something* in
/usr that wasn't in /.  For example, disklabel -e doesn't work without
vi -- which is in /usr.

But if we go down that path we are going to wind up with *every* binary
in /usr being moved to /, which is clearly wrong.

Moving a well known, long-existing system binary is not something that
should be undertaken lightly.  I will remind everyone that when
sendmail was moved from /usr/libexec to /usr/sbin, it created 
ramifications that didn't clear up for a year.  Sendmail's move could be
justified, but I don't think chown's move can be -- certainly not on
the basis of something as flimsy as MAKEDEV needing it!

-Matt
Matthew Dillon 
<[EMAIL PROTECTED]>


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Ben Rosengart

On Mon, 13 Dec 1999, Bill Fumerola wrote:

> On Mon, 13 Dec 1999, Louis A. Mamakos wrote:
> 
> > So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
> > just the root file system mounted?   
> 
> As one who just got his ass bitten by this, I would vote yes.

As one who's missed chown at times when only root's mounted, I'm with Bill.

--
 Ben Rosengart

UNIX Systems Engineer, Skunk Group
StarMedia Network, Inc.



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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-14 Thread Matthew Thyer

On Mon, 13 Dec 1999, Louis A. Mamakos wrote:
> So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
> just the root file system mounted?   

How about removing awk from MAKEDEV so life isn't so hard to recover
when you use a 3.3 fixit floppy after removing /dev and not making
enough of it again.

-- 
/===\
| Work: [EMAIL PROTECTED] | Home: [EMAIL PROTECTED] |
\===/
"If it is true that our Universe has a zero net value for all conserved
quantities, then it may simply be a fluctuation of the vacuum of some
larger space in which our Universe is imbedded. In answer to the
question of why it happened, I offer the modest proposal that our
Universe is simply one of those things which happen from time to time."
 E. P. Tryon   from "Nature" Vol.246 Dec.14, 1973



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



Re: make world broken building fortunes

1999-12-14 Thread Marcel Moolenaar

Peter Wemm wrote:
> 
> I wonder if we should move fortune to usr.bin?  It's hardly a game and I'm
> way beyond tired of it being left out of standard paths...
> (ie: "/bin:/usr/bin[:/usr/local/bin]")

After letting this go through my head for a day (it probably isn't
important anymore :-), I think it's better to add /usr/games to the
standard search path. Fortune is not a tool you use for anything other
than fun and does not really belong in a "serious" directory as
/usr/bin. On the other hand it's too frequently used to not have it
somewhere in a search path. Also, having games as part of FreeBSD
without a proper search path to them is also a bit odd.

Anyway, my 2c...

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-13 Thread Bill Fumerola

On Mon, 13 Dec 1999, Louis A. Mamakos wrote:

> So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
> just the root file system mounted?   

As one who just got his ass bitten by this, I would vote yes.

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -






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



Re: Speaking of moving files (Re: make world broken building fortunes )

1999-12-13 Thread Louis A. Mamakos

> On Mon, 13 Dec 1999, Kris Kennaway wrote:
> 
> > On Mon, 13 Dec 1999, Peter Wemm wrote:
> > 
> > > I wonder if we should move fortune to usr.bin?  It's hardly a game and I'm
> > > way beyond tired of it being left out of standard paths...
> > > (ie: "/bin:/usr/bin[:/usr/local/bin]")
> > 
> > I have no opinion about fortune, but I do think that md5 should be moved
> > from /sbin to /bin - it's hardly a "system program or administration
> > utility" but is a quite general-purpose tool.
> 
> /me 's gratuitous-change alarm goes off

So how about /usr/sbin/chown -> /sbin/chown so that MAKEDEV works with
just the root file system mounted?   

louie






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



Re: Speaking of moving files (Re: make world broken building fortunes)

1999-12-13 Thread Doug White

On Mon, 13 Dec 1999, Kris Kennaway wrote:

> On Mon, 13 Dec 1999, Peter Wemm wrote:
> 
> > I wonder if we should move fortune to usr.bin?  It's hardly a game and I'm
> > way beyond tired of it being left out of standard paths...
> > (ie: "/bin:/usr/bin[:/usr/local/bin]")
> 
> I have no opinion about fortune, but I do think that md5 should be moved
> from /sbin to /bin - it's hardly a "system program or administration
> utility" but is a quite general-purpose tool.

/me 's gratuitous-change alarm goes off

Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED] |  www.FreeBSD.org



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



Speaking of moving files (Re: make world broken building fortunes)

1999-12-13 Thread Kris Kennaway

On Mon, 13 Dec 1999, Peter Wemm wrote:

> I wonder if we should move fortune to usr.bin?  It's hardly a game and I'm
> way beyond tired of it being left out of standard paths...
> (ie: "/bin:/usr/bin[:/usr/local/bin]")

I have no opinion about fortune, but I do think that md5 should be moved
from /sbin to /bin - it's hardly a "system program or administration
utility" but is a quite general-purpose tool.

Kris



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



Re: make world broken building fortunes

1999-12-13 Thread Rodney W. Grimes

> 
> 
> On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote:
> 
> > I think the easiest solution would be (instead of your patches of
> > course):
> 
> > -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
> > +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
> 
> Only if you preceded the line with a comment explaining that the games
> part of the path is needed exclusively for strfile, which is needed
> exclusivelty for fortune.

And protect it all by !defined(NOGAMES)

-- 
Rod Grimes - KD7CAX @ CN85sl - (RWG25)   [EMAIL PROTECTED]


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



Re: make world broken building fortunes

1999-12-13 Thread Peter Wemm

Sheldon Hearn wrote:
> 
> 
> On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote:
> 
> > I think the easiest solution would be (instead of your patches of
> > course):
> 
> > -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
> > +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
> 
> Only if you preceded the line with a comment explaining that the games
> part of the path is needed exclusively for strfile, which is needed
> exclusivelty for fortune.
> 
> I've been bitten once already by undocumented dependencies. :-(

I wonder if we should move fortune to usr.bin?  It's hardly a game and I'm
way beyond tired of it being left out of standard paths...
(ie: "/bin:/usr/bin[:/usr/local/bin]")

Cheers,
-Peter




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



Re: make world broken building fortunes

1999-12-13 Thread Sheldon Hearn



On Mon, 13 Dec 1999 10:42:36 +0100, Marcel Moolenaar wrote:

> I think the easiest solution would be (instead of your patches of
> course):

> -STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
> +STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games

Only if you preceded the line with a comment explaining that the games
part of the path is needed exclusively for strfile, which is needed
exclusivelty for fortune.

I've been bitten once already by undocumented dependencies. :-(

Ciao,
Sheldon.


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



Re: make world broken building fortunes

1999-12-13 Thread Marcel Moolenaar

Peter Jeremy wrote:
> 
> >===> games/fortune/datfiles
> >PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile 
>strfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat
> >strfile: illegal option -- C
> >strfile [-iorsx] [-c char] sourcefile [datafile]
> >*** Error code 1

This is exactly why strfile is built as a tool.


> Well, the following fixes that problem for me:

>  .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy
>  $f.dat: $f
> -   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
> +   LD_LIBRARY_PATH=${LIBRARY_PATH} \
> +   PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \
> strfile -Crs ${.ALLSRC} ${.TARGET}
>  .endfor

The problem basicly is that the strfile tool is installed in
/usr/obj/.../usr/games, which isn't in the path. I think the easiest
solution would be (instead of your patches of course):

Index: Makefile.inc1
===
RCS file: /home/ncvs/src/Makefile.inc1,v
retrieving revision 1.106
diff -u -r1.106 Makefile.inc1
--- Makefile.inc1   1999/12/12 22:24:08 1.106
+++ Makefile.inc1   1999/12/13 09:40:16
@@ -113,7 +113,7 @@
 OBJTREE=   ${MAKEOBJDIRPREFIX}/${MACHINE_ARCH}
 .endif
 WORLDTMP=  ${OBJTREE}${.CURDIR}/${BUILD_ARCH}
-STRICTTMPPATH= ${WORLDTMP}/bin:${WORLDTMP}/usr/bin
+STRICTTMPPATH=
${WORLDTMP}/bin:${WORLDTMP}/usr/bin:${WORLDTMP}/usr/games
 TMPPATH=   ${STRICTTMPPATH}:${PATH}
 
 # bootstrap/tools make

Can you try it and tell me if that works?

> And buildworld then dies at:
> 
> colldef -I /3.0/cvs/src/share/colldef -o ru_SU.ISO_8859-5.out 
>/3.0/cvs/src/share/colldef/ru_SU.ISO_8859-5.src
> colldef: syntax error near line 1
> *** Error code 69

Yes. I had it built as a tool in my tests, but got lost somehow in the
final commit.

Thanks,

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Re: make world broken building fortunes

1999-12-12 Thread Peter Jeremy

>On 1999-Dec-13 11:06:19 +1100, I wrote:
>I'm still running a -CURRENT from just before the signal changes and
>for the past 4 days, my nightly buildworld has been dying at follows:
>
>===> games/fortune/datfiles
>PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile 
>-Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat
>strfile: illegal option -- C
>strfile [-iorsx] [-c char] sourcefile [datafile]
>*** Error code 1
>...

Well, the following fixes that problem for me:

Index: datfiles/Makefile
===
RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v
retrieving revision 1.23
diff -u -r1.23 Makefile
--- Makefile1999/11/05 08:17:53 1.23
+++ Makefile1999/12/13 02:27:16
@@ -33,16 +33,19 @@
 
 .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy
 $f.dat: $f
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
+   LD_LIBRARY_PATH=${LIBRARY_PATH} \
+   PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \
strfile -Crs ${.ALLSRC} ${.TARGET}
 .endfor
 
 fortunes-o.dat: fortunes-o
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
+   LD_LIBRARY_PATH=${LIBRARY_PATH} \
+   PATH=${.OBJDIR}/../strfile:$$PATH:/usr/games \
strfile -Crsx ${.ALLSRC} ${.TARGET}
 
 fortunes-o: fortunes-o.${TYPE}
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \
+   LD_LIBRARY_PATH=${LIBRARY_PATH} \
+   PATH=${.OBJDIR}/../../caesar:$$PATH:/usr/games \
caesar 13 < ${.ALLSRC} > ${.TARGET}
 
 .include 


And buildworld then dies at:

colldef -I /3.0/cvs/src/share/colldef -o ru_SU.ISO_8859-5.out 
/3.0/cvs/src/share/colldef/ru_SU.ISO_8859-5.src
colldef: syntax error near line 1
*** Error code 69

This looks like it is solved by Marcel's commit:
  1.106 +3 -3  src/Makefile.inc1

Peter


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



Re: make world broken building fortunes

1999-12-12 Thread Peter Jeremy

On 1999-Dec-13 11:06:19 +1100, I wrote:
>I'm still running a -CURRENT from just before the signal changes and
>for the past 4 days, my nightly buildworld has been dying at follows:
>
>===> games/fortune/datfiles
>PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile strfile 
>-Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat
>strfile: illegal option -- C
>strfile [-iorsx] [-c char] sourcefile [datafile]
>*** Error code 1
>...

I tried using PATH=${.OBJDIR}/../strfile:$PATH:/usr/games (which is
slightly different and more correct than the patch I posted).  This
changed the problem to:
/usr/libexec/ld-elf.so.1: Shared object "libc.so.4" not found

Which isn't a good sign.  Running the command manually with
LD_LIBRARY_PATH pointing to the new libc.so works for me (which
means that strfile isn't using signals), but I'm not sure how far
back this will work.

Peter


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



make world broken building fortunes

1999-12-12 Thread Peter Jeremy

I'm still running a -CURRENT from just before the signal changes and
for the past 4 days, my nightly buildworld has been dying at follows:

===> games/fortune/datfiles
PATH=$PATH:/usr/games:/usr/obj/3.0/cvs/src/games/fortune/datfiles/../strfile  st
rfile -Crs /3.0/cvs/src/games/fortune/datfiles/fortunes fortunes.dat
strfile: illegal option -- C
strfile [-iorsx] [-c char] sourcefile [datafile]
*** Error code 1
...


Looking at the command in question, I believe the fix is as follows, but
it'll be a couple of hours to confirm.

Index: Makefile
===
RCS file: /home/CVSROOT/src/games/fortune/datfiles/Makefile,v
retrieving revision 1.23
diff -u -r1.23 Makefile
--- Makefile1999/11/05 08:17:53 1.23
+++ Makefile1999/12/13 00:04:00
@@ -33,16 +33,16 @@
 
 .for f in fortunes fortunes2 fortunes2-o limerick startrek zippy
 $f.dat: $f
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
+   PATH=/usr/games:${.OBJDIR}/../strfile:$$PATH \
strfile -Crs ${.ALLSRC} ${.TARGET}
 .endfor
 
 fortunes-o.dat: fortunes-o
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../strfile \
+   PATH=/usr/games:${.OBJDIR}/../strfile:$$PATH \
strfile -Crsx ${.ALLSRC} ${.TARGET}
 
 fortunes-o: fortunes-o.${TYPE}
-   PATH=$$PATH:/usr/games:${.OBJDIR}/../../caesar \
+   PATH=/usr/games:${.OBJDIR}/../../caesar:$$PATH \
caesar 13 < ${.ALLSRC} > ${.TARGET}
 
 .include 

Peter
-- 
Peter Jeremy (VK2PJ)[EMAIL PROTECTED]
Alcatel Australia Limited
41 Mandible St  Phone: +61 2 9690 5019
ALEXANDRIA  NSW  2015   Fax:   +61 2 9690 5982


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



Re: make world is failed on pc98

1999-12-12 Thread Takahashi Yoshihiro

In article <[EMAIL PROTECTED]>
Marcel Moolenaar <[EMAIL PROTECTED]> writes:

> Since pc98 only has a specialized boot2 and thus shares boot0 and boot1
> with other architectures, it can be assumed that an ELF boot2 doesn't
> need any special hacking in boot0 and/or boot1, right?

No, if HDD is formated with the format command in MS-DOS for pc98, it
is installed 'HDD booting menu' in the HDD. Since the menu is
substituting for boot0, boot0 is not always necessary to pc98.

The 'loader' program is only transplanted for pc98. The boot2
(sys/boot/pc98/boot2) is the mostly same as the old biosboot
(sys/pc98/boot/biosboot) .

> boot2 is already capable of loading ELF, right?

No.

> Isn't it therefore enough to just compile boot2 as ELF?

No.

> In other words, what are the problems?

We need to transplant the new boot2 (sys/boot/i386/boot2) to pc98 to
compile as ELF.

---
Takahashi Yoshihiro / [EMAIL PROTECTED]


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



Re: make world is failed on pc98

1999-12-12 Thread Marcel Moolenaar

Takahashi Yoshihiro wrote:
> 
> > BTW: Is there a special reason to have boot2 in aout?
> 
> Because nobody transplant from the i386 boot2 :-).
> FreeBSD(98) porting team is always suffering from a shortage of
> workers.
> 
> In article <[EMAIL PROTECTED]>
> Mike Smith <[EMAIL PROTECTED]> writes:
> 
> > Only in the longer term, I think.  How hard would it be to port the 'new'
> > i386 boot2?
> 
> There are few people who are knowledgeable about pc98 boot sequence.
> And that we all have our regular work. So, it is very difficult to
> port the i386 boot2 to pc98.

Please correct me if I'm wrong while I'm drawing the picture:

Since pc98 only has a specialized boot2 and thus shares boot0 and boot1
with other architectures, it can be assumed that an ELF boot2 doesn't
need any special hacking in boot0 and/or boot1, right?

boot2 is already capable of loading ELF, right?

Isn't it therefore enough to just compile boot2 as ELF?

In other words, what are the problems?

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Re: make world is failed on pc98

1999-12-11 Thread Takahashi Yoshihiro

In article <[EMAIL PROTECTED]>
Marcel Moolenaar <[EMAIL PROTECTED]> writes:

> Other than that: Go ahead!

Thank you for many comments.

> BTW: Is there a special reason to have boot2 in aout?

Because nobody transplant from the i386 boot2 :-).
FreeBSD(98) porting team is always suffering from a shortage of
workers.

In article <[EMAIL PROTECTED]>
Mike Smith <[EMAIL PROTECTED]> writes:

> Only in the longer term, I think.  How hard would it be to port the 'new' 
> i386 boot2?

There are few people who are knowledgeable about pc98 boot sequence.
And that we all have our regular work. So, it is very difficult to
port the i386 boot2 to pc98.

---
Takahashi Yoshihiro / [EMAIL PROTECTED]


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



Re: make world is failed on pc98

1999-12-11 Thread Mike Smith

> The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several
> tools for a.out are needed to make boot2.
> 
> I make the patch to fix this. Is there any problem?

Only in the longer term, I think.  How hard would it be to port the 'new' 
i386 boot2?



-- 
\\ Give a man a fish, and you feed him for a day. \\  Mike Smith
\\ Tell him he should learn how to fish himself,  \\  [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime. \\  [EMAIL PROTECTED]




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



make world broken by choose-temp.c

1999-12-11 Thread Adam Wight

===> cc
cc -O -pipe -m486 -DFREEBSD_NATIVE -DIN_GCC -DHAVE_CONFIG_H 
-DDEFAULT_TARGET_VERSION=\"2.95.2\" -DDEFAULT_TARGET_MACHINE=\"i386-unknown-freebsd\" 
-I/usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_tools 
-I/usr2/src/gnu/usr.bin/cc/cc/../cc_tools 
-I/usr2/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc 
-I/usr2/src/gnu/usr.bin/cc/cc/../../../../contrib/gcc/config   
-I/usr/obj/usr2/src/tmp/usr/include  -o cc gcc.o gccspec.o  
/usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a
/usr/obj/usr2/src/gnu/usr.bin/cc/cc/../cc_drv/libcc_drv.a(choose-temp.o): In function 
`make_temp_file':
choose-temp.o(.text+0x286): undefined reference to `mkstemps'
*** Error code 1


After my hard drive died, I was put in the unfortunate position of building
current from a 3.3-RELEASE system and found what is apparently a known
problem with this compilation path...  The fix was checked in as rev 1.8 of
gnu/usr.bin/cc/cc_drv/Makefile, but was backed out several hours later.
Considering that 3.x is where many -current users have to begin, either this
fix should be re-inserted or the reference to mkstemps should be removed.

-adam wight


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



Re: make world is failed on pc98

1999-12-11 Thread Marcel Moolenaar

Takahashi Yoshihiro wrote:

> +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf"
> +USRDIRS+=  usr/libexec/aout
> +.endif

I don't think you need to test for OBJFORMAT. Also, include MACHINE_ARCH
in case of cross-building. eg:

.if ${MACHINE_ARCH} == "i386" && ${MACHINE} == "pc98"

> +.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf"
> +_aout_tools=   usr.bin/size usr.bin/strip gnu/usr.bin/as gnu/usr.bin/ld
> +.endif

Same here.

>  .for _tool in ${_strfile} gnu/usr.bin/binutils usr.bin/objformat \
> -usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc
> +usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc ${_aout_tools}


Don't build anything after cc has been built, because cc will be a
cross-compiler when cross-building. Try putting it as early as possible.

Other than that: Go ahead!

BTW: Is there a special reason to have boot2 in aout?

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



make world is failed on pc98

1999-12-11 Thread Takahashi Yoshihiro

The boot2 for pc98 (sys/boot/pc98/boot2) is a.out program. So, several
tools for a.out are needed to make boot2.

I make the patch to fix this. Is there any problem?


--- Makefile.inc1   1999/12/10 16:13:41 1.102
+++ Makefile.inc1   1999/12/11 10:01:21
@@ -143,6 +143,10 @@
 USRDIRS=   usr/bin usr/lib/compat/aout usr/games usr/libdata/ldscripts \
usr/libexec/${OBJFORMAT} usr/share/misc
 
+.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf"
+USRDIRS+=  usr/libexec/aout
+.endif
+
 INCDIRS=   arpa g++/std objc protocols readline rpc rpcsvc security ss
 
 #
@@ -330,9 +334,13 @@
 _strfile=  games/fortune/strfile
 .endif
 
+.if ${MACHINE} == "pc98" && ${OBJFORMAT} == "elf"
+_aout_tools=   usr.bin/size usr.bin/strip gnu/usr.bin/as gnu/usr.bin/ld
+.endif
+
 tools::
 .for _tool in ${_strfile} gnu/usr.bin/binutils usr.bin/objformat \
-usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc
+usr.bin/yacc gnu/usr.bin/bison gnu/usr.bin/cc ${_aout_tools}
cd ${.CURDIR}/${_tool}; \
${MAKE} obj; \
${MAKE} depend; \

---
Takahashi Yoshihiro / [EMAIL PROTECTED]


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



Re: Make world breakage (12/09/99)

1999-12-09 Thread Marcel Moolenaar

Forrest Aldrich wrote:
> 
> Getting this from this morning's make world (after doing a make clean, just
> for good measure):

re-cvsup. The problem should be fixed already.

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Make world breakage (12/09/99)

1999-12-09 Thread Forrest Aldrich

Getting this from this morning's make world (after doing a make clean, just 
for good measure):



--
 >>> Rebuilding dependencies
--
cd /usr/src; 
COMPILER_PATH=/usr/obj/usr/src/tmp/usr/libexec:/usr/obj/usr/src/tmp/usr/
bin  LIBRARY_PATH=/usr/obj/usr/src/tmp/usr/lib:/usr/obj/usr/src/tmp/usr/lib 
  OBJFORMA
T_PATH=/usr/obj/usr/src/tmp/usr/libexec  CFLAGS="-nostdinc -O 
-pipe"  PERL5LIB=/usr/l
ibdata/perl/5.00503 
PATH=/usr/obj/usr/src/tmp/bin:/usr/obj/usr/src/tmp/usr/bin:/loca
l/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/ssl/bin:/usr/ 
X11R6/bin
:/usr/local/samba/bin:/usr/local/home/forrie/bin make 
DESTDIR=/usr/obj/usr/src/tmp  I
NSTALL="sh /usr/src/tools/install.sh" -f Makefile.inc1 par-depend
===> share/info
===> include
===> include/rpcsvc
===> lib
===> lib/csu/i386-elf
rm -f .depend
mkdep -f .depend -a   -nostdinc 
-I/usr/obj/usr/src/tmp/usr/include/usr/src/lib/cs
u/i386-elf/crti.S /usr/src/lib/csu/i386-elf/crtn.S
mkdep -f .depend -a   -nostdinc 
-I/usr/obj/usr/src/tmp/usr/include  /usr/src/lib/csu/
i386-elf/crt1.c /usr/src/lib/csu/i386-elf/crtbegin.c 
/usr/src/lib/csu/i386-elf/crtend
.c
In file included from /usr/src/lib/csu/i386-elf/crt1.c:32:
/usr/obj/usr/src/tmp/usr/include/stddef.h:39: machine/ansi.h: No such file 
or directo
ry
In file included from /usr/src/lib/csu/i386-elf/crt1.c:33:
/usr/obj/usr/src/tmp/usr/include/stdlib.h:39: sys/cdefs.h: No such file or 
directory
/usr/obj/usr/src/tmp/usr/include/stdlib.h:41: machine/ansi.h: No such file 
or directo
ry
/usr/src/lib/csu/i386-elf/crtbegin.c:28: sys/cdefs.h: No such file or directory
/usr/src/lib/csu/i386-elf/crtend.c:28: sys/cdefs.h: No such file or directory
mkdep: compile failed
*** Error code 1

Stop in /usr/src/lib/csu/i386-elf.
*** Error code 1

Stop in /usr/src/lib.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.



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



Re: make world: doesn't?

1999-12-08 Thread Kris Kennaway

On Wed, 8 Dec 1999, John W. DeBoskey wrote:

>I've just cvsup'd my -current source tree about 5 minutes
> ago and tried to make world... and got the following:
> 
> FreeBSD(root)/usr/src %make world
> make: don't know how to make world. Stop
> *** Error code 2

Is this a candidate for 'world's largest pointy hat'? :-)

Kris



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



Re: make world is no more ?

1999-12-08 Thread Marcel Moolenaar

Poul-Henning Kamp wrote:
> 
> I guess this is the ultimate way to break make world...
> 
>     syv# make world
> make: don't know how to make world. Stop
> *** Error code 2

Oops :-/

The `world' target has been added to Makefile. I guess this only shows
that I'm used to use `buildworld' and `installworld'...

A new round of testing has been started. Sorry for the inconvenience,

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Re: make world: doesn't?

1999-12-08 Thread Marcel Moolenaar

"John W. DeBoskey" wrote:

> FreeBSD(root)/usr/src %make world
> make: don't know how to make world. Stop
> *** Error code 2

Fixed!
thanks,

-- 
Marcel Moolenaarmailto:[EMAIL PROTECTED]
SCC Internetworking & Databases   http://www.scc.nl/
The FreeBSD projectmailto:[EMAIL PROTECTED]


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



Re: make world: doesn't?

1999-12-08 Thread Gianmarco Giovannelli

At 08/12/99, John W. DeBoskey wrote:
>Hi,
>
>I've just cvsup'd my -current source tree about 5 minutes
>ago and tried to make world... and got the following:
>
>FreeBSD(root)/usr/src %make world
>make: don't know how to make world. Stop
>*** Error code 2
>
>Stop in /usr/src.
>FreeBSD(root)/usr/src %
>
>This was ok 24 hours ago...

We are in the same boat. It happens here yoo ...

Cvsupped 5 minutes ago...



Best Regards,
Gianmarco Giovannelli ,  "Unix expert since yesterday"
http://www.giovannelli.it/~gmarco
http://www2.masternet.it





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



make world is no more ?

1999-12-08 Thread Poul-Henning Kamp


I guess this is the ultimate way to break make world...

syv# make world
make: don't know how to make world. Stop
*** Error code 2

Stop in /usr/src.
syv# 

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



make world: doesn't?

1999-12-08 Thread John W. DeBoskey

Hi,

   I've just cvsup'd my -current source tree about 5 minutes
ago and tried to make world... and got the following:

FreeBSD(root)/usr/src %make world
make: don't know how to make world. Stop
*** Error code 2

Stop in /usr/src.
FreeBSD(root)/usr/src %

   This was ok 24 hours ago...

   I receive -current as a digest, so I apologize if this is already
known and I simply don't know it yet.

   I'll check the cvs histories to see if I can figure out what
changed this afternoon.

Thanks!
John


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



Re: "make world" broken on a 3 month old system

1999-12-07 Thread Edwin Culp

Mark Newton wrote:

> I'm trying to "make world" on a system last built on Sep 29th;  it's
> failing like so:
>
> ===> f77doc
> /usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc
> cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO 
>-DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED cleandepend;  
>/usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE 
>-DNOSHARED all;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC 
>-DNOPROFILE -DNOSHARED -B install;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD 
>-DNOINFO -DNOMAN -DNOPROFILE -DNOSHARED -B cleandir obj
> rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH 
>/usr/obj/usr/src/gnu/lib/libgcc/GRTAGS  /usr/obj/usr/src/gnu/lib/libgcc/GSYMS 
>/usr/obj/usr/src/gnu/lib/libgcc/GTAGS
> echo '#include '> config.h
> echo '#include '  >> config.h
> echo '#include "gansidecl.h"'   > tconfig.h
> echo '#include "i386/xm-i386.h"'>> tconfig.h
> echo '#include "i386/i386.h"'   > tm.h
> echo '#include "i386/att.h"'>> tm.h
> echo '#include "svr4.h"'>> tm.h
> echo '#include ' >> tm.h
> echo '#include "i386/freebsd.h"'>> tm.h
> echo '#include "i386/perform.h"'>> tm.h
> cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
>-I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC 
>-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o 
>/usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c
> *** Signal 12
>
> Stop in /usr/src/gnu/lib/libgcc.
> *** Error code 1
>
> Stop in /usr/src.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
> *** Error code 1
>
> Stop.
>
> Should I be expecting this? :-)
>
> - mark

I think that your problem is covered in this  cut and paste from /usr/src/UPDATING 
that has very interesting content:-)  Be sure and read everything previous to this 
also.

19990929:
The sigset_t datatype has been changed from an integral type
to a compound type and can hold 128 signals. Syscalls directly
or indirectly using the new sigset_t have been added as to
maintain compatibility with existing binaries. A new kernel must
be made and installed and booted with before a make world can
be done.

Hope that helps.

ed



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



"make world" broken on a 3 month old system

1999-12-07 Thread Mark Newton

I'm trying to "make world" on a system last built on Sep 29th;  it's
failing like so:

===> f77doc
/usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc
cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN 
-DNOPIC -DNOPROFILE -DNOSHARED cleandepend;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD 
-DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all;  
/usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE 
-DNOSHARED -B install;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN 
-DNOPROFILE -DNOSHARED -B cleandir obj
rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH 
/usr/obj/usr/src/gnu/lib/libgcc/GRTAGS  /usr/obj/usr/src/gnu/lib/libgcc/GSYMS 
/usr/obj/usr/src/gnu/lib/libgcc/GTAGS
echo '#include '> config.h
echo '#include '  >> config.h
echo '#include "gansidecl.h"'   > tconfig.h
echo '#include "i386/xm-i386.h"'>> tconfig.h
echo '#include "i386/i386.h"'   > tm.h
echo '#include "i386/att.h"'>> tm.h
echo '#include "svr4.h"'>> tm.h
echo '#include ' >> tm.h
echo '#include "i386/freebsd.h"'>> tm.h
echo '#include "i386/perform.h"'>> tm.h
cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o 
/usr/src/gnu/lib/libgcc/../../../contrib/gcc/libgcc1.c
*** Signal 12

Stop in /usr/src/gnu/lib/libgcc.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.


Should I be expecting this? :-)

- mark

-- 
Mark Newton   Email:  [EMAIL PROTECTED] (W)
Network Engineer  Email:  [EMAIL PROTECTED]  (H)
Internode Systems Pty Ltd Desk:   +61-8-82232999
"Network Man" - Anagram of "Mark Newton"  Mobile: +61-416-202-223


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



make world failure in pccardc

1999-12-03 Thread Poul-Henning Kamp


===> usr.sbin/pccard/pccardc
cc -O -pipe -I/usr/src/usr.sbin/pccard/pccardc/../pccardd -Wall -g -static   -c 
/usr/src/usr.sbin/pccard/pccardc/power.c
/usr/src/usr.sbin/pccard/pccardc/power.c: In function `power_main':
/usr/src/usr.sbin/pccard/pccardc/power.c:79: `PIOCSVIR' undeclared (first use in this 
function)
/usr/src/usr.sbin/pccard/pccardc/power.c:79: (Each undeclared identifier is reported 
only once
/usr/src/usr.sbin/pccard/pccardc/power.c:79: for each function it appears in.)
*** Error code 1

Stop in /usr/src/usr.sbin/pccard/pccardc.

--
Poul-Henning Kamp FreeBSD coreteam member
[EMAIL PROTECTED]   "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


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



Re: Make world broken in libc_r

1999-11-27 Thread Alfred Perlstein

On Sat, 27 Nov 1999, Mark Murray wrote:

> Hi
> 
> "make world" is broken in libc_r. Simple fix is to replace all
> "socklen_t" with "int".

libc_r likes to pull data from /usr/include instead of the 
source tree, "make includes" fixes this.  I'm not sure if
that's the correct way to fix it though.

-Alfred



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



Make world broken in libc_r

1999-11-27 Thread Mark Murray

Hi

"make world" is broken in libc_r. Simple fix is to replace all
"socklen_t" with "int".

M


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



Re: Make world this morning.

1999-11-16 Thread Bill Fumerola

On Tue, 16 Nov 1999, Edwin Culp wrote:

> /usr/src/games/larn/monster.c: In function `hitm':
> /usr/src/games/larn/monster.c:856: syntax error before `amt'

My first breakage of world, how neat.

Thanks to Marcel for fixing what was the result of me having too many
local copies of src/games on my laptop and checking one and committing
another.

Sorry -CURRENT folks..

-- 
- bill fumerola - [EMAIL PROTECTED] - BF1560 - computer horizons corp -
- ph:(800) 252-2421 - [EMAIL PROTECTED] - [EMAIL PROTECTED]  -


PS. Sorry wpaul.



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



Re: Make world this morning.

1999-11-16 Thread Donn Miller

On Tue, 16 Nov 1999, Edwin Culp wrote:

> Just looking at the results of a make world from a cvsup at about 4:40
> PST.
> 
> ed
> 
> /usr/obj/usr/src/tmp/usr/include/sys/ttydev.h:60: warning: `B115200'
> redefined
> /usr/obj/usr/src/tmp/usr/include/termios.h:227: warning: this is the
> location of the previous definition
> cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE
> -fwritable-strings   -I/usr/obj/usr/src/tmp/usr/include -c
> /usr/src/games/larn/monster.c
> /usr/src/games/larn/monster.c: In function `hitm':
> /usr/src/games/larn/monster.c:856: syntax error before `amt'
> *** Error code 1
> 
> Stop in /usr/src/games/larn.
> *** Error code 1

Yep - same here.  One other problem I had is that make world failed when I
used:

make -j 3 -DNOPROFILE world

It bombed out somewhere near the beginning of make world when gcc was
being built.  When I eliminated the parallel build (make -DNOPROFILE
world), it got further into the build, but bombed out at the point you
describe.

I was able to continue on by doing

 make -j 3 -DNOCLEAN -DNOGAMES -DNOPROFILE world

- Donn



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



Make world this morning.

1999-11-16 Thread Edwin Culp

Just looking at the results of a make world from a cvsup at about 4:40
PST.

ed

/usr/obj/usr/src/tmp/usr/include/sys/ttydev.h:60: warning: `B115200'
redefined
/usr/obj/usr/src/tmp/usr/include/termios.h:227: warning: this is the
location of the previous definition
cc -nostdinc -O -pipe -DBSD -DVER=12 -DSUBVER=0 -DNONAP -DUIDSCORE
-fwritable-strings   -I/usr/obj/usr/src/tmp/usr/include -c
/usr/src/games/larn/monster.c
/usr/src/games/larn/monster.c: In function `hitm':
/usr/src/games/larn/monster.c:856: syntax error before `amt'
*** Error code 1

Stop in /usr/src/games/larn.
*** Error code 1

Stop in /usr/src/games.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.





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



Re: -current Make World

1999-11-16 Thread Matt Hamilton

> Speaking of which, is their an archive (web based?) of the FreeBSD-current
> mailing list (how about others?)?  I didn't see one linked in my searches
> around the web pages.

I am currently working on a full-text search/archive of Open Source
mailing lists, which should be up at http://www.osdigger.com for testing
before the end of the year.  The site will have searchable archives of
over 300 lists including *BSD, Linux, Perl, Apache, KDE, Gnome, and lots
lots more :)

Watch this space.

-Matt


 Matt Hamilton[EMAIL PROTECTED]
 Hamilton Computing +44 (0)797 707 2482




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



Re: -current Make World

1999-11-15 Thread Kris Kennaway

On Sun, 14 Nov 1999, Lester Igo wrote:

> Speaking of which, is their an archive (web based?) of the FreeBSD-current
> mailing list (how about others?)?  I didn't see one linked in my searches
> around the web pages.

http://www.freebsd.org/mail/

kind of obviously pointed to by
http://www.freebsd.org/search/#mailinglists ;-)

Kris


Cthulhu for President! For when you're tired of choosing the _lesser_ of
two evils..



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



Re: -current Make World

1999-11-14 Thread David O'Brien

On Sun, Nov 14, 1999 at 11:02:18PM -0800, Lester Igo wrote:
> I started with FreeBSD-3.3-Release last Friday, tried current and it
> failed so I moved on to stable, it worked, I installed it and built a new
> kernel, and then using the fresh compile I tried to go to -current and it
> still fails at the same location with the same signal 12...

Did you build a -CURRENT kernel before trying to build a -CURRENT world?

See also /usr/src/UPDATING.

-- 
-- David([EMAIL PROTECTED])


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



-current Make World

1999-11-14 Thread Lester Igo


I have been trying to get world to compile on my system and had a "signal
12" failure at the same location every time.

I started with FreeBSD-3.3-Release last Friday, tried current and it
failed so I moved on to stable, it worked, I installed it and built a new
kernel, and then using the fresh compile I tried to go to -current and it
still fails at the same location with the same signal 12...

This computer in it's same hardware config compiled many -current versions
prior to 3.0 (it is an SMP system 2xP166MMX), so I am fairly sure of the
hardware. (not to mention it compiled -stable without a hitch)

I haven't followed the FreeBSD current mailing lists for about a year, so
if instructions have been sent to get around this problem, I missed them.
Note: yes I joined the mailing lists now that I am trying to get back on
that track...

Speaking of which, is their an archive (web based?) of the FreeBSD-current
mailing list (how about others?)?  I didn't see one linked in my searches
around the web pages.

All that said, it bails on a "signal 12" as follows (any suggestions of
things to try please let me know):

-
===> f77doc
===> cc_tools
/usr/obj/usr/src/gnu/usr.bin/cc/cc_tools created for /usr/src/gnu/usr.bin/cc/cc_tools
===> cc_int
/usr/obj/usr/src/gnu/usr.bin/cc/cc_int created for /usr/src/gnu/usr.bin/cc/cc_int
===> cc_drv
/usr/obj/usr/src/gnu/usr.bin/cc/cc_drv created for /usr/src/gnu/usr.bin/cc/cc_drv
===> cpp
/usr/obj/usr/src/gnu/usr.bin/cc/cpp created for /usr/src/gnu/usr.bin/cc/cpp
===> cc1
/usr/obj/usr/src/gnu/usr.bin/cc/cc1 created for /usr/src/gnu/usr.bin/cc/cc1
===> cc
/usr/obj/usr/src/gnu/usr.bin/cc/cc created for /usr/src/gnu/usr.bin/cc/cc
===> cc1obj
/usr/obj/usr/src/gnu/usr.bin/cc/cc1obj created for /usr/src/gnu/usr.bin/cc/cc1obj
===> cc1plus
/usr/obj/usr/src/gnu/usr.bin/cc/cc1plus created for /usr/src/gnu/usr.bin/cc/cc1plus
===> c++
/usr/obj/usr/src/gnu/usr.bin/cc/c++ created for /usr/src/gnu/usr.bin/cc/c++
===> c++filt
/usr/obj/usr/src/gnu/usr.bin/cc/c++filt created for /usr/src/gnu/usr.bin/cc/c++filt
===> doc
/usr/obj/usr/src/gnu/usr.bin/cc/doc created for /usr/src/gnu/usr.bin/cc/doc
===> f77
/usr/obj/usr/src/gnu/usr.bin/cc/f77 created for /usr/src/gnu/usr.bin/cc/f77
===> f771
/usr/obj/usr/src/gnu/usr.bin/cc/f771 created for /usr/src/gnu/usr.bin/cc/f771
===> f77doc
/usr/obj/usr/src/gnu/usr.bin/cc/f77doc created for /usr/src/gnu/usr.bin/cc/f77doc
cd /usr/src/gnu/lib/libgcc; /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN 
-DNOPIC -DNOPROFILE -DNOSHARED cleandepend;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD 
-DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED all;  
/usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE 
-DNOSHARED -B install;  /usr/obj/usr/src/tmp/usr/bin/make -DWORLD -DNOINFO -DNOMAN 
-DNOPROFILE -DNOSHARED -B cleandir obj
rm -f .depend /usr/obj/usr/src/gnu/lib/libgcc/GPATH 
/usr/obj/usr/src/gnu/lib/libgcc/GRTAGS  /usr/obj/usr/src/gnu/lib/libgcc/GSYMS 
/usr/obj/usr/src/gnu/lib/libgcc/GTAGS
echo '#include '> config.h
echo '#include '  >> config.h
echo '#include "i386/xm-i386.h"'> tconfig.h
echo '#include "i386/i386.h"'   > tm.h
echo '#include "i386/att.h"'>> tm.h
echo '#include "i386/freebsd.h"'>> tm.h
echo '#include "i386/perform.h"'>> tm.h
cc -c -O -pipe -I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/config 
-I/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc -I. -fexceptions -DIN_GCC 
-I/usr/obj/usr/src/tmp/usr/include -DL_mulsi3 -o _mulsi3.o 
/usr/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
*** Signal 12

Stop in /usr/src/gnu/lib/libgcc.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop.
*** Error code 1

Stop.
*** Error code 1

Stop.

-

Thanks, and I look forward to being back on the -current track again!

--
Lester Igo  
[EMAIL PROTECTED]
http://www.vtic.net/~igo





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



Re: perl error in make world

1999-11-13 Thread Kris Kennaway

On Sat, 13 Nov 1999, Annelise Anderson wrote:

> I'm getting the following error with today's -current sources;
> this particular system has a rather strange history, so it may
> not be the sources, but something else.  I have tried -DNOCRYPT,
> which doesn't help.  And I've searched the archives without
> finding anything directly applicable, so suggestions would be
> appreciated.

Back in september libcrypt grew the ability to use SHA-1 passwords..looks
like your libcrypt wasn't linked against libmd, so the SHA_* symbols
aren't found in libcrypt. Adding -lmd to the perl link line would fix it,
but you should try rebuilding libcrypt first. Doing a "nm
/usr/lib/libcrypt.so.2" should show the symbols with a 'T' next to them.

Kris


Cthulhu for President! For when you're tired of choosing the _lesser_ of
two evils..



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



Re: Make World dies.......

1999-11-13 Thread Doug Rabson

On Sat, 13 Nov 1999, Mike Muir wrote:

> William Woods wrote:
> > 
> > Shit, I will loose all my custom settings...no other way around this
> 
> Try compiling and installing the kernel first, reboot, buildworld..
> should work (did for me but hey, im x86..) NO PROMISES! heh

This should work (I have moved an alpha from -stable to -current with
this). You should use mergemaster to update your /etc.

--
Doug Rabson Mail:  [EMAIL PROTECTED]
Nonlinear Systems Ltd.  Phone: +44 181 442 9037




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



Re: Make World dies.......

1999-11-13 Thread Mike Muir

William Woods wrote:
> 
> Shit, I will loose all my custom settings...no other way around this

Try compiling and installing the kernel first, reboot, buildworld..
should work (did for me but hey, im x86..) NO PROMISES! heh

mike.


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



<    1   2   3   4   5   6   7   >