The recent current snapshots are missing readline.h. It has been
missing since at least the July 4 snap at current/releng3.freebsd.org.
Satoshi
---
# tar tvf bindist.tar | grep readline
drwxr-xr-x root/wheel 0 Jul 15 04:01 1999 usr/include/readline/
-r--r--r-- root/wheel202008 Ju
Dear currenters,
/usr/include/readline/readline.h (and whatever else that's supposed to
be in that directory) has been missing from 4-current and 3-stable
snaps for awhile. Does anyone know why?
Satoshi
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the b
Have people seen these?
=== node82 1/2 ===
bash-2.02# gdb -k *.22
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copyin
Hi,
How do I test if sigset_t is empty in -current? The xview sources
have this macro:
#define sigisempty(s) (!(*(s)))
which is ok for the old sigset_t (unsigned int) but obviously won't
work for the new one since it's a struct.
typedef struct __sigset {
unsigned int__bits[_SIG_W
FYI.
-PW
===
From: [EMAIL PROTECTED] (Satoshi Asami)
Subject: HEADS UP: ports Makefiles being updated soon
To: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Date: Fri, 7 Apr 2000 01:15:16 -0700 (PDT)
Message-Id: <[EMAIL PROTECTED]>
Hello world,
As we have been discussing on the ports list, w
Hello world,
As those of you who have been following the ports list may know, we
are changing the ports skeletons' layout in an effort to reduce the
number of small directories and significantly speed up operation on
the ports tree. This should especially help operations such as "CVS
update", an
* From: Chris Timmons
* make: don't know how to make Makefiles. Stop
I've seen similar things, but they went away when I reduced the load
(other compilations in my case) on the server. How busy is your
server?
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe free
I cvsupped a couple of times, even blew away the entire
contrib/texinfo and gnu/usr.bin/texinfo in the middle but I still get
this
===
===> makeinfo
cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/local\"
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo
-
* From: as...@freebsd.org (Satoshi Asami)
*
* * From: Chris Timmons
*
* * make: don't know how to make Makefiles. Stop
*
* I've seen similar things, but they went away when I reduced the load
* (other compilations in my case) on the server. How busy is your
* server?
* ===
* ===> makeinfo
* cc -O -pipe -DHAVE_CONFIG_H -DLOCALEDIR=\"/usr/share/local\"
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo/makeinfo
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib/texinfo
-I/usr/src/gnu/usr.bin/texinfo/makeinfo/../../../../contrib
* From: br...@worldcontrol.com
* So I am now mostly back the square 1. I'm still using an old GUS MAX,
* which at the whim of FreeBSD-core may suddenly stop working.
Just one point -- the axing of voxware was *not* approved by
FreeBSD-core, and that's why it has been brought back.
Satoshi
T
Hi,
In our project, we're trying to connect two PCs to both ends of a SCSI
chain. I've got it somewhat working, but have a couple of questions
re. mounting the filesystems.
If I mount the filesystem from one machine (A) as read-write, then the
other one (B) can't mount it read-write because the
* >However, if I try to mount it from B read-only while A is mounting it
* >read-write, it succeeds. This looks dangerous, as A writing data onto
* >the disk could cause B's cache to go stale without B knowing it. Is
* >it a good idea to allow read-only mounts of a dirty filesystem anyway?
*
Sorry I'm jumping into this in the middle.
* Oliver Fromme wrote:
* >In releases/snapshots they're called "axp" and "x86", while in
* >ports they're called "alpha" and "i386".
I'm not sure where this "axp/x86" thing is coming from, but we are
using "alpha" and "i386" in ports (and /usr/src/sy
* From: "David O'Brien"
* Alternately, I guess we could just have the code live in
* /usr/ports/lang/f2c/src/, but I don't know if Satoshi wants /usr/ports
* to expand like that.
Eek. I don't think people will appreciate the ports collection
suddenly exploding in size with things like that.
* From: Steve Kargl
* Yes, I recognize that this is problem. A partial solution might
* be anoncvs to a shadow tree of the master ports repository. Only
* those ports in the shadow tree which satisfy portlint and "make;
* make install; make package" would get committed to the master
* rep
* Well, actually I did f2c as a port, and it does indeed fit
* inside the ports paradigm. Please, see my original email in
* the thread.
Yes, I know that. I was just wondering why people would want it
otherwise.
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe f
* From: Steve Kargl
* g77 is a frontend to the FSF compiler backend, and thus it is bound
* to specific versions. So, it could become a support nightmare to ensure
* a g77 port is in sync with the egcs backend in the base distribution.
I don't think it would be that much of a support nightm
* The biggest problem has been that the port of g77 has not worked
* properly for quite some time and in fact is currently marked as
* broken. I would anticipate that this situation would not change much in
That (and bug fix issues, as DavidO contends) all depends on the
commitment of the maint
* From: Garrett Wollman
* > A lot of people use a lot of things out of ports. Why should Fortran
* > be different?
*
* Because Berkeley Unix has /always/ included a FORTRAN compiler.
Maybe that's because Berkeley Unix never had (until recently, anyway)
a ports system? :)
Satoshi
To Unsub
* From: Glenn Johnson
* Your points are well taken. I had a local port of g77 that built
* against our current gcc. I never submitted it however for a couple
* of reasons:
*
* 1. The port I had was for 0.5.19. This will build against our current
*gcc, but g77 has advanced significant
* The g77-0.5.19(.1) is *extremely* out-of-date. It should be dropped from
* the ports collection, and if someone wants to use g77, then they should
* install egcs.
*
* The newer versions of g77 do not work with gcc-2.7.2.x. The author of
* g77 states that you shouldn't even try to back po
* Maybe I misunderstood, but I thought Glenn got g77-0.5.19 to
* work with our gcc-2.7.x. g77 is now at version 0.5.24. Those
* micro numbers are significant changes, and these represent over
* a years work on g77.
No, I misunderstood. So Glenn got 0.5.19 to work, but it's very old.
Anyth
* From: Luke
* linux_lib port. [why does it install into / anyways]
You can put it anywhere and symlink to it, like sysinstall does now,
but it has to be called "/compat" (or some other well-known place)
because of the implementation. The string "/compat/linux" has to be
hardcoded in the linu
* From: John Polstra
* On 28-Jan-99 Bruce Evans wrote:
Hey John, are you sure your mailer is Y2K compliant?
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
*Yes, a.out execution support will be standard in FreeBSD for at least
* several more years. At some point it may become an option, but that's a
* long way off.
*The only thing people are talking about is support for building the
* system binaries in a.out. We're moving to ELF because
* Just curious as to why share/emacs and share/emacs/site-lisp are created by
* BSD.local.dist instead of by the emacs ports which might want to use them?
* It's not a big deal, but it seems to me that these aren't useful for the
* general case of someone not wanting to install an emacs port (s
(Send messages like this to -ports next time, please)
* I've noticed that as I'm constantly syncing my /usr/ports directory and
* upgrading programs, the old packages stay there. If I pkg_delete them and
* there's an unchanged file that exists in both the update and the original
then
* t
* From: Robert Watson
* away logged in via the network performing this recovery. Having the
* drives automatically renumber themselves on the complete failure of one
* drive (and it was fairly complete) would have been a disaster. This is
Or just think "ccd". There are people building dis
I just started the first build of packages-4-current. I'm planning to
recompile it and packages-3-stable once a week or so.
Errors are at "http://bento.freebsd.org/~asami/errorlogs/";, as usual.
Satoshi
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in th
Hi,
Some of you may have stumbled upon bsd.port.mk complaining about the
lack of said file even after a make world. This was caused by my
mistake of forgetting to update src/share/mk at the same time I
committed the check to bsd.port.mk.
I have since corrected it so if you cvsup again and make w
31 matches
Mail list logo
