from a late June (pre 11-branch, as far as I can tell)
> >> revision to r303771.
> >>
> >> Now, running ???make update??? (or buildworld, ???) in /usr/src fails with
> >> a signal 12:
> >>
> >> matteo@triton:/usr/src$ sudo make update
> &
> On Aug 10, 2016, at 10:41 AM, Konstantin Belousov wrote:
> On Wed, Aug 10, 2016 at 10:33:23AM -0400, Matteo Riondato wrote:
>> Hi all,
>>
>> I recently upgraded from a late June (pre 11-branch, as far as I can tell)
>> revision to r303771.
>>
>> Now
On Wed, Aug 10, 2016 at 10:33:23AM -0400, Matteo Riondato wrote:
> Hi all,
>
> I recently upgraded from a late June (pre 11-branch, as far as I can tell)
> revision to r303771.
>
> Now, running ???make update??? (or buildworld, ???) in /usr/src fails with a
> signal 12:
&g
Hi all,
I recently upgraded from a late June (pre 11-branch, as far as I can tell)
revision to r303771.
Now, running “make update” (or buildworld, …) in /usr/src fails with a signal
12:
matteo@triton:/usr/src$ sudo make update
Password:
*** Signal 12
Stop.
make: stopped in /usr/src
On 12/11/11 01:11, Benjamin Kaduk wrote:
> On Sat, 10 Dec 2011, O. Hartmann wrote:
>
>> On 12/10/11 14:51, Chuck Burns wrote:
>>> On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
>>>> Here is quick, hackish patch to allow your make update to wo
On Sat, 10 Dec 2011, O. Hartmann wrote:
On 12/10/11 14:51, Chuck Burns wrote:
On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
Here is quick, hackish patch to allow your make update to work, it appears
that the Makefile.inc1 does not include the full path to svn, while it does
On 12/10/11 14:51, Chuck Burns wrote:
> On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
>> Here is quick, hackish patch to allow your make update to work, it appears
>> that the Makefile.inc1 does not include the full path to svn, while it does
>> include the
On Saturday, December 10, 2011 7:35:27 AM Chuck Burns wrote:
> Here is quick, hackish patch to allow your make update to work, it appears
> that the Makefile.inc1 does not include the full path to svn, while it does
> include the full path to cvs and other tools, this makes me think
On Saturday, December 10, 2011 3:59:41 AM O. Hartmann wrote:
> Taking the instruction from manpage make.conf(5) and setting variable
> SVN_UPDATE to YES, typing "make update" in /usr/srcfails due to svn
> can not be found. make.conf(5) also contains a variable "SUP&qu
On Sat, Dec 10, 2011, at 10:59, O. Hartmann wrote:
> Taking the instruction from manpage make.conf(5) and setting variable
> SVN_UPDATE to YES, typing "make update" in /usr/srcfails due to svn
> can not be found. make.conf(5) also contains a variable "SUP" conta
Taking the instruction from manpage make.conf(5) and setting variable
SVN_UPDATE to YES, typing "make update" in /usr/src fails due to svn
can not be found. make.conf(5) also contains a variable "SUP" containing
the path for cvsup or cvsup and I'm desperately missi
In article <[EMAIL PROTECTED]>,
Patrick M. Hausen <[EMAIL PROTECTED]> wrote:
>
> Yes, but now we have three different ways to update:
[...]
> 2. call cvsup from /usr/local/etc/periodic with supfiles for whatever you
>need ...
Not a good idea. Add a new crontab entry instead. If everybody u
s, updating both at the same time is rather convinient as well.
And to some of us it isn't. If you want to be consequential, add
/usr/doc as well, and extend this to updates by CVS, too.
The current behavior is this:
"make update" in
| /u
Hi all!
Bill Fumerola wrote:
> On Mon, Feb 07, 2000 at 10:31:17PM +0100, Christian Weisgerber wrote:
>
> > Why does "make update" in /usr/src also include a cvsup of /usr/ports?
> >
> > Since /usr/ports and /usr/docs have Makefiles and "update" t
On Mon, Feb 07, 2000 at 10:31:17PM +0100, Christian Weisgerber wrote:
> Why does "make update" in /usr/src also include a cvsup of /usr/ports?
>
> Since /usr/ports and /usr/docs have Makefiles and "update" targets
> of their own, and the alternative update b
Why does "make update" in /usr/src also include a cvsup of /usr/ports?
Since /usr/ports and /usr/docs have Makefiles and "update" targets
of their own, and the alternative update by cvs doesn't cover
/usr/ports either, I suggest to remove the /usr/ports cvsup from
Makefi
My make update isn't working anymore, and I can't figure out why. I
know the recent stuff regarding Id->FreeBSD, and I've closely watched
all the files that Doug talked about, and they're all the way he said
they should be, but after I get done with the cvsup part of make
Hello,
Would it be possible to add a "make update" target to the top Makefile in
ports and doc? Similar to the Makefile in /usr/src, so that it does something
like "cvs -q update -P -d".
It would keep the Makefiles more orthogonal, and in any case, make update
type
18 matches
Mail list logo
