libss termination
As far as I can tell, there's nothing in the tree which uses libss any longer, and hasnt been for quite some time. Is there any reason to keep it? Kris PGP signature
Re: libss termination
> > As far as I can tell, there's nothing in the tree which uses libss any > longer, and hasnt been for quite some time. Is there any reason to > keep it? Nope. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
> > > > As far as I can tell, there's nothing in the tree which uses libss any > > longer, and hasnt been for quite some time. Is there any reason to > > keep it? > > Nope. Right. Kill it. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
On Sun, Aug 19, 2001 at 12:51:24PM +0100, Mark Murray wrote: > > > > > > As far as I can tell, there's nothing in the tree which uses libss any > > > longer, and hasnt been for quite some time. Is there any reason to > > > keep it? > > > > Nope. > > Right. Kill it. Dead! Kris PGP signature
Re: libss termination
Is this caused by libss termination? At Sun, 19 Aug 2001 07:48:07 + (UTC), Kris Kennaway wrote: > As far as I can tell, there's nothing in the tree which uses libss any > longer, and hasnt been for quite some time. Is there any reason to > keep it? ===> usr.bin/mk_cmds yacc -d /usr/src/usr.bin/mk_cmds/ct.y cp y.tab.c ct.c lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c rm -f .depend mkdep -f .depend -a-I. -I/usr/src/usr.bin/mk_cmds/../../lib/libss -DIN_MK_CMDS -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/mk_cmds/mk_cmds.c /usr/src/usr.bin/mk_cmds/options.c /usr/src/usr.bin/mk_cmds/utils.c ct.c cmd_tbl.c /usr/src/usr.bin/mk_cmds/mk_cmds.c:16: ss_internal.h: No such file or directory /usr/src/usr.bin/mk_cmds/options.c:8: ss.h: No such file or directory /usr/src/usr.bin/mk_cmds/utils.c:9: ss_internal.h: No such file or directory /usr/src/usr.bin/mk_cmds/ct.y:30: ss.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/mk_cmds. *** Error code 1 -- Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. <[EMAIL PROTECTED]> // FreeBSD Project To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
Yes; mk_cmds is part of libss and should have been deleted as well. > Is this caused by libss termination? > > At Sun, 19 Aug 2001 07:48:07 + (UTC), > Kris Kennaway wrote: > > As far as I can tell, there's nothing in the tree which uses libss any > > longer, and hasnt been for quite some time. Is there any reason to > > keep it? > > > ===> usr.bin/mk_cmds > yacc -d /usr/src/usr.bin/mk_cmds/ct.y > cp y.tab.c ct.c > lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c > rm -f .depend > mkdep -f .depend -a-I. -I/usr/src/usr.bin/mk_cmds/../../lib/libss -DIN_MK > _CMDS -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/mk_cmds/mk_cmds.c > /usr/src/usr.bin/mk_cmds/options.c /usr/src/usr.bin/mk_cmds/utils.c ct.c cmd > _tbl.c > /usr/src/usr.bin/mk_cmds/mk_cmds.c:16: ss_internal.h: No such file or directo > ry > /usr/src/usr.bin/mk_cmds/options.c:8: ss.h: No such file or directory > /usr/src/usr.bin/mk_cmds/utils.c:9: ss_internal.h: No such file or directory > /usr/src/usr.bin/mk_cmds/ct.y:30: ss.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/usr.bin/mk_cmds. > *** Error code 1 > > > -- > Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. > <[EMAIL PROTECTED]> // FreeBSD Project > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
On Mon, Aug 20, 2001 at 10:54:02AM +0900, Jun Kuriyama wrote: > > Is this caused by libss termination? > > At Sun, 19 Aug 2001 07:48:07 + (UTC), > Kris Kennaway wrote: > > As far as I can tell, there's nothing in the tree which uses libss any > > longer, and hasnt been for quite some time. Is there any reason to > > keep it? > > > ===> usr.bin/mk_cmds > yacc -d /usr/src/usr.bin/mk_cmds/ct.y > cp y.tab.c ct.c > lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c > rm -f .depend > mkdep -f .depend -a-I. -I/usr/src/usr.bin/mk_cmds/../../lib/libss -DIN_MK_CMDS >-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/mk_cmds/mk_cmds.c >/usr/src/usr.bin/mk_cmds/options.c /usr/src/usr.bin/mk_cmds/utils.c ct.c cmd_tbl.c > /usr/src/usr.bin/mk_cmds/mk_cmds.c:16: ss_internal.h: No such file or directory > /usr/src/usr.bin/mk_cmds/options.c:8: ss.h: No such file or directory > /usr/src/usr.bin/mk_cmds/utils.c:9: ss_internal.h: No such file or directory > /usr/src/usr.bin/mk_cmds/ct.y:30: ss.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > Stop in /usr/src/usr.bin/mk_cmds. > *** Error code 1 Strange; I'm not sure why my buildworld succeeded, possibly it was picking up stale files from the host. This looks to also be part of the libss package..so the question becomes "is IT used any more"? I'll look into it. Kris PGP signature
Re: libss termination
> Mark Murray <[EMAIL PROTECTED]> wrote: MM> > > MM> > > As far as I can tell, there's nothing in the tree which uses libss any MM> > > longer, and hasnt been for quite some time. Is there any reason to MM> > > keep it? MM> > MM> > Nope. MM> Right. Kill it. Usr.bin/mk_cmds is still using libss. And buildworld fails. ===> usr.bin/mk_cmds yacc -d /usr/src/usr.bin/mk_cmds/ct.y cp y.tab.c ct.c lex -t -l /usr/src/usr.bin/mk_cmds/cmd_tbl.l > cmd_tbl.c rm -f .depend mkdep -f .depend -a -nostdinc -I. -I/usr/src/usr.bin/mk_cmds/../../lib/libss -DIN_MK_CMDS -I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/mk_cmds/mk_cmds.c /usr/src/usr.bin/mk_cmds/options.c /usr/src/usr.bin/mk_cmds/utils.c ct.c cmd_tbl.c /usr/src/usr.bin/mk_cmds/mk_cmds.c:16: ss_internal.h: No such file or directory /usr/src/usr.bin/mk_cmds/options.c:8: ss.h: No such file or directory /usr/src/usr.bin/mk_cmds/utils.c:9: ss_internal.h: No such file or directory /usr/src/usr.bin/mk_cmds/ct.y:30: ss.h: No such file or directory mkdep: compile failed *** Error code 1 Stop in /usr/src/usr.bin/mk_cmds. -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
On Mon, Aug 20, 2001 at 04:28:07PM +0900, NAKAJI Hiroyuki wrote: > > Mark Murray <[EMAIL PROTECTED]> wrote: > MM> > > > MM> > > As far as I can tell, there's nothing in the tree which uses libss any > MM> > > longer, and hasnt been for quite some time. Is there any reason to > MM> > > keep it? > MM> > > MM> > Nope. > > MM> Right. Kill it. > > Usr.bin/mk_cmds is still using libss. And buildworld fails. Thanks; I fixed this already (by removing mk_cmds too :-) Kris PGP signature
Re: libss termination
> In <[EMAIL PROTECTED]> > Kris Kennaway <[EMAIL PROTECTED]> wrote: nakaji> Usr.bin/mk_cmds is still using libss. And buildworld fails. Kris> Thanks; I fixed this already (by removing mk_cmds too :-) Oops... I should have checked http://www.FreeBSD.org/cgi/cvsweb.cgi/src/usr.bin/mk_cmds/ first. Thanks. -- NAKAJI Hiroyuki To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
Mark Murray wrote: > > > > > > > As far as I can tell, there's nothing in the tree which uses libss any > > > longer, and hasnt been for quite some time. Is there any reason to > > > keep it? > > > > Nope. > > Right. Kill it. Are there any ports which depnd on it, and thus assume it's in the base system, which will need to be hacked to have a libss port on which they will need to depend? -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
Terry Lambert wrote: > Mark Murray wrote: > > > > > > > > > > As far as I can tell, there's nothing in the tree which uses libss any > > > > longer, and hasnt been for quite some time. Is there any reason to > > > > keep it? > > > > > > Nope. > > > > Right. Kill it. > > Are there any ports which depnd on it, and thus assume it's > in the base system, which will need to be hacked to have a > libss port on which they will need to depend? > > -- Terry Well, why not have a look and find out? If so, supplying a list is more productive than making somebody else go and look for you. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
Peter Wemm wrote: > > > > > As far as I can tell, there's nothing in the tree which uses > > > > > libss any longer, and hasnt been for quite some time. Is > > > > > there any reason to keep it? > > > > > > > > Nope. > > > > > > Right. Kill it. > > > > Are there any ports which depnd on it, and thus assume it's > > in the base system, which will need to be hacked to have a > > libss port on which they will need to depend? > > Well, why not have a look and find out? If so, supplying a list > is more productive than making somebody else go and look for you. It's not as easy as you paint it, since there are a lot of things that run config scripts and just "magically" find all sorts of libraries you never knew you had. It'd be a heck of a lot easier, if it were possible to force everything to link shared, which would show in an ldd of all the binaries in all the packages, but that would still leave some stuff out. I don't think there's an easy way to deal with testing this sort of thing, if you don't have a full ftp.freebsd.org mirror, with the ability to build each and every port after deleting the library and header files locally. I just asked mostly because I'm not the person diking it out without having checked first, and I remember the last time something like this went wrong... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: libss termination
On Tue, Aug 21, 2001 at 06:12:58AM -0700, Terry Lambert wrote: > Peter Wemm wrote: > > > > > > As far as I can tell, there's nothing in the tree which uses > > > > > > libss any longer, and hasnt been for quite some time. Is > > > > > > there any reason to keep it? > > > > > > > > > > Nope. > > > > > > > > Right. Kill it. > > > > > > Are there any ports which depnd on it, and thus assume it's > > > in the base system, which will need to be hacked to have a > > > libss port on which they will need to depend? > > > > Well, why not have a look and find out? If so, supplying a list > > is more productive than making somebody else go and look for you. > > It's not as easy as you paint it, since there are a lot > of things that run config scripts and just "magically" > find all sorts of libraries you never knew you had. > > It'd be a heck of a lot easier, if it were possible to > force everything to link shared, which would show in an > ldd of all the binaries in all the packages, but that > would still leave some stuff out. I don't think there's > an easy way to deal with testing this sort of thing, if > you don't have a full ftp.freebsd.org mirror, with the > ability to build each and every port after deleting the > library and header files locally. > > I just asked mostly because I'm not the person diking it > out without having checked first, and I remember the last > time something like this went wrong... It's no big deal, Terry. If bento turns up packages which are breaking because they expect libss, then I'll either fix them, or if it's a hard dependency then I'll import libss as a port. Kris PGP signature
Re: libss termination
Terry Lambert wrote: > > Peter Wemm wrote: > > > > > > > > As far as I can tell, there's nothing in the tree which uses > > > > > > libss any longer, and hasnt been for quite some time. Is > > > > > > there any reason to keep it? > > > > > > > > > > Nope. > > > > > > > > Right. Kill it. > > > > > > Are there any ports which depnd on it, and thus assume it's > > > in the base system, which will need to be hacked to have a > > > libss port on which they will need to depend? > > > > Well, why not have a look and find out? If so, supplying a list > > is more productive than making somebody else go and look for you. > > It's not as easy as you paint it, since there are a lot > of things that run config scripts and just "magically" > find all sorts of libraries you never knew you had. It should be pretty straightforward on the ports-building system; remove libss and run the full-up ports build. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
