Yes I understand the significance of /usr/obj, but not why,
in detail, the port builds fail. In any case, if there are
some specific directories that cause problems, perhaps
bsd.port.mk should check for them and complain,
rather than letting the build fail with baffling errors.
Barney
On Mon, F
You have to do it from step to step. Not a one-time upgrade.
Add the following option in you make.conf :
NOPERL = true
NOSUIDPERL = true
then, you can issue 'make world'
if it fails, you'll have to compile libc and install it before
if you still have complains about miniperl, edit Makefiles and
I've been having the exact same problem with the same upgrade for 3 days
now. I keep cvsuping/making buildworld/etc, hoping that someone will fix it
soon but it doesn't look like it's going to happen. For the amount of time
I've spent so far, just trying to get it to work right, I could have
forma
At Sat, 10 Feb 2001 01:04:45 -0500,
Barney Wolff wrote:
>
> Try anything BUT /usr/obj as WRKDIRPREFIX. /usr/obj/ports, for
> example. I found most or all ports fail to build if that
> specific directory is used. I have no idea why.
man make and read .OBJDIR section.
--
FUJISHIMA Satsuki
T
From the signal() manual page:
When a process which has installed signal handlers forks, the child pro-
cess inherits the signals. All caught signals may be reset to their de-
fault action by a call to the execve(2) function; ignored signals remain
ignored.
So I woul
Warner Losh wrote:
>
> In message <[EMAIL PROTECTED]> Andrew
>Gordon writes:
> : I hope that's _late_ Feb 4th sources if your firewall uses ipfw: ipfw was
> : substantially broken from 2001/02/01 20:25:09 to 2001/02/04 05:48:59
> : (/sys/netinet/ip_fw.c rev 1.131.2.13 is the bad version).
>
What you probaby need to do is either:
1. Go to "Options" in the main menu of sysinstall, and change "Release Name" to
4.2-RELEASE. THe ports are the same for the entire 4.x branch, so you will be OK
2. Use cvsup to sync your ports tree. If find this the easiest, anyway, but it's all
a matte
On Sun, Feb 11, 2001 at 05:37:42PM +0200, Pekka Savola wrote:
> As a lot of others including some @FreeBSD.org people, I got:
[snip]
> pp_hot.o(.text+0x16a1): undefined reference to `setresuid'
> pp_hot.o(.text+0x16d4): undefined reference to `setresgid'
> *** Error code 1
> ---
>
> while tryin
try these instructions:
http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=699499+706204+/usr/local/www/db/text/2000/freebsd-stable/2806.freebsd-stable
I did it once on a mail server and vowed never to do it again if I didn't have to.
Basically you have to build perl separately.
--clark
3.5-STAB
Hi All,
After "make world" when I started /stand/sysinstall and tryed to install
ports collection, I received the following message:
l User Confirmation Requested k
x Warning: Can't find the `4.2-STABLE' distribution on this x
x FTP ser
-BEGIN PGP SIGNED MESSAGE-
Hello,
I built new world and kernels today. Trying to boot them, I always run
into
the following:
Copyright (c) 1992-2001 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
The Regents of the University of Calif
In message <[EMAIL PROTECTED]> Andrew
Gordon writes:
: I hope that's _late_ Feb 4th sources if your firewall uses ipfw: ipfw was
: substantially broken from 2001/02/01 20:25:09 to 2001/02/04 05:48:59
: (/sys/netinet/ip_fw.c rev 1.131.2.13 is the bad version).
:
: We were upgrading our firewall
> Well, in Russian BSD newsgroup I see complaints that even
>
> $ program | more # and press `q' while program is still running
>
> giving the same error.
I don't see that myself.
Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
E-mail: [EMAIL PROTECTED], Tel: +386-2-320-63
Matt Dillon ([EMAIL PROTECTED]) napisał(a):
>
> :If the flags 0x100 is specified to syscons (this is now default in
> :GENERIC), syscons should revert to the AT keyboard when the USB
> :keyboard has gone.
> :
> :Kazu
>
> ok... so if we remove 'flags 0x1' from atkbd0, and leave
> 'flags
In message <[EMAIL PROTECTED]>, "Valeriy E.
Ushakov" write
s:
> On Sun, Feb 11, 2001 at 06:25:44 -0800, Cy Schubert wrote:
>
> > > > So no, your makewhatis patch only appears to be a bandaid, but
> > > > there is something going on deeper (possibly in the kernel) that
> > > > was not there in 4.
On Sun, Feb 11, 2001 at 06:25:44 -0800, Cy Schubert wrote:
> > > So no, your makewhatis patch only appears to be a bandaid, but
> > > there is something going on deeper (possibly in the kernel) that
> > > was not there in 4.2-RELEASE.
> >
> > Were you using ssh to login on to the computers when
In message <[EMAIL PROTECTED]>, Kent Stewart writes:
>
>
> Blaz Zupan wrote:
> >
> > > :Actually, I don't think it fixed everything. There have been ports
> > > :that also had problems with piping to tar and broken pipes. It
> > > :wouldn't surprise me if the makewhatis problem was only a littl
> Try the following patch (which I dug up off the Web after the previous
> go-round on this problem). It seems to work.
>
> (The indentation is wrong, I know. I had to apply the patch -l because
> the HTMLization of the original mail message hosed the whitespace.)
Excellent, this seems to be th
subscribe [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
Barney Wolff <[EMAIL PROTECTED]> writes:
> Er, could it possibly be that telnet has been hiding the error
> all along? It's really, really hard to see how ssh could
> *create* this sort of error.
Try the following patch (which I dug up off the Web after the previous
go-round on this problem).
>
> >:If the flags 0x100 is specified to syscons (this is now default in
> >:GENERIC), syscons should revert to the AT keyboard when the USB
> >:keyboard has gone.
> >:
> >:Kazu
> >
> >ok... so if we remove 'flags 0x1' from atkbd0, and leave
> >'flags 0x100' on sc0, and add an entry to /
Jim Weeks:
>On Thu, 8 Feb 2001, David Bushong wrote:
>> I'll try to put a "cleanup" mode in one of these days, but it's rather nasty,
>> since basically you have to:
>>
>> pkg_delete all of the versions (including the most recent), pkg_delete all
>> of the programs that depended on older versions
Hi
Yes, I concur. I had similar problems on an Adaptec 3985 (788x based)
where I changed out a cable and the messages went away and so did the
physical hanging problems I was having.
Chad
--On Sunday, February 11, 2001 9:13 AM +0200 Danny Braniss
<[EMAIL PROTECTED]> wrote:
> i've had simil
On Sat, 10 Feb 2001, Warner Losh wrote:
>
> Yes. I've done this with Feb 4th sources on our 4.0-RELEASE
> firewall. Well, I'm waiting for a time to do the make
> installworld/installkernel since the machine isn't at my house and I'm
> nervous about doing it remotely since I screw 4 people if s
> "Matthew" == Matthew Emmerton <[EMAIL PROTECTED]> writes:
Matthew> Even though your controller supports UDMA operation, not all
Matthew> devices use it.
Thanks, i know that ;-)
Matthew> A quick scan of the manual for your Plextor
Matthew> seems to indicate that it only operates in PIO4 m
On Sun, Feb 11, 2001 at 09:13:59AM +0200, Danny Braniss wrote:
FWIW: My 29160 works just fine with yesterdays stable. I suspect plumbing
problems like Danny says
Wilko
> i've had similar problems, in my case after changing cable/terminator
> the problem was fixed.
>
> danny
>
> In messa
>:If the flags 0x100 is specified to syscons (this is now default in
>:GENERIC), syscons should revert to the AT keyboard when the USB
>:keyboard has gone.
>:
>:Kazu
>
>ok... so if we remove 'flags 0x1' from atkbd0, and leave
>'flags 0x100' on sc0, and add an entry to /etc/usbd.conf to
>
Er, could it possibly be that telnet has been hiding the error
all along? It's really, really hard to see how ssh could
*create* this sort of error.
Barney Wolff
On Sun, Feb 11, 2001 at 09:35:43AM +0100, Blaz Zupan wrote:
> > pkg_add runs tar with the --fast-read option to extract the table
28 matches
Mail list logo
