, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Santiago
It might be useful to know:
* What you are running at the time;
* what the most recent c
ithout a problem ( just in case).
Thanks.
Santi
On 12/28/23 16:23, David Wolfskill wrote:
On Thu, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Sant
On Thu, Dec 28, 2023 at 04:05:49PM +0100, Santiago Martinez wrote:
> Hi Everyone, I'm having issues building world from current (just now).
>
> Same header missing on multiple parts.
>
> Best regards.
>
> Santiago
>
It might be useful to know:
* What you ar
Hi Everyone, I'm having issues building world from current (just now).
Same header missing on multiple parts.
Best regards.
Santiago
"""
In file included from
/usr/src/contrib/llvm-project/llvm/lib/Demangle/ItaniumDemangle.cpp:13:
In file included from
/usr/src/contr
Error building world in current:
--
>>> stage 3.1: building everything
--
/usr/src/sys/netlink/route/iface.c:1315:22: error: use of undeclared
identifier 'if_fla
On 2019-09-09 23:08, Warner Losh wrote:
>
>> Aspirationally, yes. I did a successful CROSS_TOOLCHAIN=amd64-gcc
>> buildworld earlier this week. (It doesn't play well with binary pkg's
>> built with Clang, so I ended up replacing it with a Clang-built world
>> instead, but it compiled.)
>>
>> Unfo
On Mon, Sep 9, 2019 at 11:05 PM Conrad Meyer wrote:
> On Mon, Sep 9, 2019 at 8:25 PM Rebecca Cran wrote:
> >
> > Is building world with gcc still supported? I'm getting an error running
> > the following:
> >
> > make XCC=/usr/local/bin/gcc9 XCXX=/usr/lo
On Mon, Sep 9, 2019 at 8:25 PM Rebecca Cran wrote:
>
> Is building world with gcc still supported? I'm getting an error running
> the following:
>
> make XCC=/usr/local/bin/gcc9 XCXX=/usr/local/bin/g++9 buildworld
Hi Rebecca,
Aspirationally, yes. I did a successful CROSS
Is building world with gcc still supported? I'm getting an error running
the following:
make XCC=/usr/local/bin/gcc9 XCXX=/usr/local/bin/g++9 buildworld
/usr/local/bin/gcc9 --sysroot=/usr/obj/usr/src/amd64.amd64/tmp
-B/usr/obj/usr/src/amd64.amd64/tmp/usr/bin -O2 -pipe -DNO__SCCSID
-DNO__
dard "make buildworld"
>
>
> On 10/8/18 1:43 AM, Dimitry Andric wrote:
>> On 7 Oct 2018, at 23:28, Eric McCorkle wrote:
>>>
>>> I'm having some trouble building world from current. The problem looks
>>> to be various tools' c++ files no
wrote:
>>
>> I'm having some trouble building world from current. The problem looks
>> to be various tools' c++ files not including string.h, and therefore
>> missing defs.
>>
>> Is there some critical update step I missed somewhere?
>
> If
On 7 Oct 2018, at 23:28, Eric McCorkle wrote:
>
> I'm having some trouble building world from current. The problem looks
> to be various tools' c++ files not including string.h, and therefore
> missing defs.
>
> Is there some critical update step I missed somewher
I'm having some trouble building world from current. The problem looks
to be various tools' c++ files not including string.h, and therefore
missing defs.
Is there some critical update step I missed somewhere?
signature.asc
Description: OpenPGP digital signature
rs,
-pete
Someone can correct me if I'm wrong but I believe the current "correct"
way to get ccache builds is WITH_CCACHE_BUILD set in src.conf.
src.conf(5) seems to indicate as much as well. To answer your question,
yes, I am I'm sure many others are building world on HEAD wi
conf
> .if !defined(NO_CCACHE)
> CC= /usr/local/libexec/ccache/world/cc
> CXX= /usr/local/libexec/ccache/world/c++
> .endif
>
> cheers,
> -pete
>
Someone can correct me if I'm wrong but I believe the current "co
#x27;m wrong but I believe the current "correct"
way to get ccache builds is WITH_CCACHE_BUILD set in src.conf.
src.conf(5) seems to indicate as much as well. To answer your question,
yes, I am I'm sure many others are building world on HEAD with ccache
without issue.
thanks, i had
On 10/02/2017 13:07, Pete Wright wrote:
hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running, but i've since cut over to CURRENT and am still
having issues. running "make build
hey there,
i've been unable to buildworld using ccache for a while. initially i
assumed it was due to some incompatibilities on the drm-next branch
which i was running, but i've since cut over to CURRENT and am still
having issues. running "make buildworld" i am running into this exception:
Hi there,
I just tried to do a buildworld with a current svn checkout (r286978). However
it appears that world fails with WITHOUT_SSP set.
I'm currently running r284582, so the SSP issue must have been introduced
somewhere between those two revision.
Cheers
Alexander
Here's the error log:
>>
On 24/04/2015 12:05, Garrett Cooper wrote:
> On Apr 24, 2015, at 3:03, Garrett Cooper
> wrote:
>
>> On Apr 24, 2015, at 2:59, Garrett Cooper
>> wrote:
>>
>>> On Apr 23, 2015, at 2:05, Willem Jan Withagen
>>> wrote:
>>>
On 22/04/2015 23:37, Ed Maste wrote:
> On 22 April 2015 at 15:
On 24/04/2015 12:05, Garrett Cooper wrote:
> On Apr 24, 2015, at 3:03, Garrett Cooper wrote:
>
>> On Apr 24, 2015, at 2:59, Garrett Cooper wrote:
>>
>>> On Apr 23, 2015, at 2:05, Willem Jan Withagen wrote:
>>>
On 22/04/2015 23:37, Ed Maste wrote:
> On 22 April 2015 at 15:55, Willem Jan
On Apr 24, 2015, at 3:03, Garrett Cooper wrote:
> On Apr 24, 2015, at 2:59, Garrett Cooper wrote:
>
>> On Apr 23, 2015, at 2:05, Willem Jan Withagen wrote:
>>
>>> On 22/04/2015 23:37, Ed Maste wrote:
On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
>
>> Yes:
>> https:/
On Apr 24, 2015, at 2:59, Garrett Cooper wrote:
> On Apr 23, 2015, at 2:05, Willem Jan Withagen wrote:
>
>> On 22/04/2015 23:37, Ed Maste wrote:
>>> On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
> Yes:
> https://lists.freebsd.org/pipermail/freebsd-current/2015-February/05
On Apr 23, 2015, at 2:05, Willem Jan Withagen wrote:
> On 22/04/2015 23:37, Ed Maste wrote:
>> On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
>>>
Yes:
https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
>>>
>>> But this is not enough to make yac
On 22/04/2015 23:37, Ed Maste wrote:
> On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
>>
>>> Yes:
>>> https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
>>>
>>
>> But this is not enough to make yacc part of the build tools??
>
> yacc is unconditionally built duri
On 22-4-2015 23:37, Ed Maste wrote:
On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
Yes:
https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
But this is not enough to make yacc part of the build tools??
yacc is unconditionally built during bootstrap-tools
On 22 April 2015 at 15:55, Willem Jan Withagen wrote:
>
> > Yes:
> > https://lists.freebsd.org/pipermail/freebsd-current/2015-February/054740.html
> >
>
> But this is not enough to make yacc part of the build tools??
yacc is unconditionally built during bootstrap-tools as of r281615.
What SVN rev
On 22/04/2015 18:45, Warren Block wrote:
> On Wed, 22 Apr 2015, Willem Jan Withagen wrote:
>
>> Hi,
>>
>> [I thought that I've seen talk about this before.]
>>
>> On a customers system I'm trying to build a new world, with a fresh tree.
>> I've deleted lines from other tracks in parallel compilati
On Wed, 22 Apr 2015, Willem Jan Withagen wrote:
Hi,
[I thought that I've seen talk about this before.]
On a customers system I'm trying to build a new world, with a fresh tree.
I've deleted lines from other tracks in parallel compilation.
--- aslcompilerparse.c ---
yacc -d -pAslCompiler -oasl
Hi,
[I thought that I've seen talk about this before.]
On a customers system I'm trying to build a new world, with a fresh tree.
I've deleted lines from other tracks in parallel compilation.
--- aslcompilerparse.c ---
yacc -d -pAslCompiler -oaslcompilerparse.c aslcompiler.y
yacc: 89 shift/reduc
On Tue, 2013-09-24 at 22:15 -0700, Sean Bruno wrote:
> On Sun, 2013-09-22 at 16:53 -0500, Brooks Davis wrote:
> > On Sat, Sep 21, 2013 at 03:42:16PM +0400, Lev Serebryakov wrote:
> > > Hello, Sean.
> > > You wrote 20 2013 ??., 22:39:30:
> > >
> > > SB> wow, that didn't work at all
On Sun, 2013-09-22 at 16:53 -0500, Brooks Davis wrote:
> On Sat, Sep 21, 2013 at 03:42:16PM +0400, Lev Serebryakov wrote:
> > Hello, Sean.
> > You wrote 20 2013 ??., 22:39:30:
> >
> > SB> wow, that didn't work at all. :-)
> >
> > SB> I set these in make.conf:
> >
> > SB> CC=/us
On Sat, Sep 21, 2013 at 03:42:16PM +0400, Lev Serebryakov wrote:
> Hello, Sean.
> You wrote 20 2013 ??., 22:39:30:
>
> SB> wow, that didn't work at all. :-)
>
> SB> I set these in make.conf:
>
> SB> CC=/usr/local/bin/clang
> SB> C++=/usr/local/bin/clang++
> SB> CPP=/usr/local/b
Hello, Sean.
You wrote 20 сентября 2013 г., 22:39:30:
SB> wow, that didn't work at all. :-)
SB> I set these in make.conf:
SB> CC=/usr/local/bin/clang
SB> C++=/usr/local/bin/clang++
SB> CPP=/usr/local/bin/clang++
SB> It exploded pretty badly:
SB> http://people.freebsd.org/~sbruno/doingitwrong.
On Sep 20, 2013, at 20:39, Sean Bruno wrote:
> wow, that didn't work at all. :-)
>
> I set these in make.conf:
>
> CC=/usr/local/bin/clang
> C++=/usr/local/bin/clang++
> CPP=/usr/local/bin/clang++
You should use XCC, XCXX and XCPP instead, as described here:
https://wiki.freebsd.org/ExternalT
wow, that didn't work at all. :-)
I set these in make.conf:
CC=/usr/local/bin/clang
C++=/usr/local/bin/clang++
CPP=/usr/local/bin/clang++
It exploded pretty badly:
http://people.freebsd.org/~sbruno/doingitwrong.txt
Any reason that this shouldn't work?
$ pkg info |grep clang
clang-devel-3.4.r
On 2012-09-13 11:27, Edward Meewis wrote:
...
FWIW: The clang build finished too, but with two hick-ups:
1. - kdump: build reports 4 errors:
===> usr.bin/kdump (depend)
sh /usr/home/emeewis/contrib/FreeBSD-HEAD/usr.bin/kdump/mksubr
/usr/obj/usr/home/emeewis/contrib/FreeBSD-HEAD/tmp/usr/include >
Hi Brook,
On 12-09-12 18:34, Brooks Davis wrote:
Note that some people have been working on external toolchain support.
This would aim to make it possible to do what you were trying, e.g.
building world using WITHOUT_TOOLCHAIN, which sets both WITHOUT_CLANG
and WITHOUT_GCC, among others
UT_CLANG line.
> >
> > I'll be damned, that did it! (with gcc)
>
> Note that some people have been working on external toolchain support.
>
> This would aim to make it possible to do what you were trying, e.g.
> building world using WITHOUT_TOOLCHAIN, wh
ng on external toolchain support.
This would aim to make it possible to do what you were trying, e.g.
building world using WITHOUT_TOOLCHAIN, which sets both WITHOUT_CLANG
and WITHOUT_GCC, among others.
However, I am not sure how far these efforts have come b
On 12-09-12 14:15, Dimitry Andric wrote:
Try building with gcc, while removing the WITHOUT_GCC line, or building
with clang, while removing the WITHOUT_CLANG line.
I'll be damned, that did it! (with gcc)
Thanks, guys!
-- Ed.
___
freebsd-current@free
On 2012-09-12 13:45, Edward Meewis wrote:
...
I added the following lines to each individual Makefile it stumbled on:
CFLAGS+= -I/usr/obj/usr/home/emeewis/src/FreeBSD-HEAD/tmp/usr/include
LDADD+=-L/usr/obj/usr/home/emeewis/src/FreeBSD-HEAD/tmp/usr/lib
or:
LDFLAGS+=-L/usr/obj/usr/home/emeewis/sr
Hi Dimitry,
On 12-09-12 13:09, Dimitry Andric wrote:
On 2012-09-12 12:46, Edward Meewis wrote:
Has anyone recently built FreeBSD10-current with clang on a FreeBSD9
amd64 system?
I've bumped into a number of issues. Mainly, buildworld picks up the old
system includes, which miss newly introduce
On 2012-09-12 12:46, Edward Meewis wrote:
Has anyone recently built FreeBSD10-current with clang on a FreeBSD9
amd64 system?
I've bumped into a number of issues. Mainly, buildworld picks up the old
system includes, which miss newly introduced symbols; same thing with
libraries. I fixed that by p
Hi,
Has anyone recently built FreeBSD10-current with clang on a FreeBSD9
amd64 system?
I've bumped into a number of issues. Mainly, buildworld picks up the old
system includes, which miss newly introduced symbols; same thing with
libraries. I fixed that by pointing compiler and linker to
/usr/ob
I was trying to upgrade my 9.0-CURRENT amd64 after clang
was updated, but i got following error:
===> sys/boot/i386/cdboot (all)
===> sys/boot/i386/gptboot (all)
===> sys/boot/i386/kgzldr (all)
===> sys/boot/i386/libi386 (all)
clang -O2 -pipe -DLOADER_NFS_SUPPORT -DCOMPORT=0x3f8 -DCOMSPEED=9600
-
On Mon, Feb 21, 2011 at 12:34 PM, Renato Botelho wrote:
> I was trying to upgrade my 9.0-CURRENT amd64 after clang
> was updated, but i got following error:
>
> ===> sys/boot/i386/cdboot (all)
> ===> sys/boot/i386/gptboot (all)
> ===> sys/boot/i386/kgzldr (all)
> ===> sys/boot/i386/libi386 (all)
>
On Fri, Nov 05, 2010 at 09:42:27PM -0700, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 1:25 PM, Ulrich Sp?rlein wrote:
> > Hey folks, not sure why, but I had a stab at looking which files were
> > actually read during building world.
[..]
> > usr.bin/cpio/test/* ? ? # mov
On Fri, Nov 05, 2010 at 09:42:27PM -0700, Garrett Cooper wrote:
> On Fri, Nov 5, 2010 at 1:25 PM, Ulrich Spörlein wrote:
> > Hey folks, not sure why, but I had a stab at looking which files were
> > actually read during building world.
> > bin/sh/bltin/echo.1
> I'd
Hi,
> On Fri, 5 Nov 2010 17:16:47 -0400
> John Baldwin said:
> etc/periodic/security/610.ipf6denied
jhb> I wonder if this is stale due to ip6fw being removed?
No, it seems to me that it is not related to ip6fw, and it calls
ipfstat. Perhaps, some work for IPv6 support of IP Filter?
S
On Fri, Nov 5, 2010 at 1:25 PM, Ulrich Spörlein wrote:
> Hey folks, not sure why, but I had a stab at looking which files were
> actually read during building world.
>
> Method went something like this:
>
> (turn on atime)
> # find . -exec touch {} +
> # sleep 2;
On Friday, November 05, 2010 4:25:36 pm Ulrich Spörlein wrote:
> Hey folks, not sure why, but I had a stab at looking which files were
> actually read during building world.
>
> Method went something like this:
>
> (turn on atime)
> # find . -exec touch {} +
> # sleep 2;
On Fri, Nov 05, 2010 at 09:25:36PM +0100, Ulrich Sp??rlein wrote:
> lib/msun/src/s_fabs.c
> lib/msun/src/s_modf.c
These are explicitly ignored by msun/Makefile.
# FreeBSD's C library supplies these functions:
#COMMON_SRCS+= s_fabs.c s_frexp.c s_isnan.c s_ldexp.c s_modf.c
--
Steve
_
Hey folks, not sure why, but I had a stab at looking which files were
actually read during building world.
Method went something like this:
(turn on atime)
# find . -exec touch {} +
# sleep 2; touch timestamp
# make buildworld buildkernel installworld installkernel (this is on amd64)
# make
Dimitry Andric writes:
> Dag-Erling Smørgrav writes:
> > No, what is used is a variant of method 1 *on top of* method 2 for a
> > very specific case. You need "a special version of clang" (method 2)
> > anyway to support cross-building.
> Eventually, clang should support building objects for all
On 2010-08-18 11:15, Dag-Erling Smørgrav wrote:
> I'm not a big fan of "reasonable chances" when it comes to the
> toolchain.
Me neither, which is why I created method 2 originally. :) The
-isysroot method was invented by Roman Divacky in r198248.
> No, what is used is a variant of method 1 *on
Dimitry Andric writes:
> Alexander Kabaev writes:
> > Does method 1) work fine with 'make buildenv'? I doubt that. I would
> > strongly suggest we should not lose this feature. I do not like the
> > idea of having to depend on -isystem in CFLAGS in such an environment.
> I have not tested make b
On 2010-08-17 17:04, Eitan Adler wrote:
> what about -nostdinc ?
>Do not search the standard system directories for header files.
>
> Or will this also disable the command line equivalents ?
It seems that -isysroot doesn't work with that:
$ gcc -nostdinc -isysroot ${WORLDTMP} -S -v
On Tue, Aug 17, 2010 at 10:28 AM, Daniel Nebdal wrote:
> On Tue, Aug 17, 2010 at 3:47 PM, Dimitry Andric wrote:
>> On 2010-08-17 15:03, Daniel Nebdal wrote:
> However, a disadvantage is that the built-in search paths of the
> bootstrap compiler are not entirely disabled by using the -isys
On 2010-08-17 16:28, Daniel Nebdal wrote:
> Mmh, I just read through the in-detail description you gave in another
> mail. It's a bit surprising that there isn't a simple and reliable way
> to disable/replace all hardcoded paths, but I guess it doesn't come up
> that often.
Well, except when you w
On Tue, Aug 17, 2010 at 3:47 PM, Dimitry Andric wrote:
> On 2010-08-17 15:03, Daniel Nebdal wrote:
However, a disadvantage is that the built-in search paths of the
bootstrap compiler are not entirely disabled by using the -isysroot, -B
and -L flags,
> ...
>> For clarification, did y
On 2010-08-17 15:15, Alexander Kabaev wrote:
> Dimitry Andric wrote:
...
>> 1) The "isysroot" method: build a regular version of clang, and make
>>sure WMAKEENV contains something like:
>>
>>CC="${CC} -isysroot ${WORLDTMP} -B${WORLDTMP}/usr/lib/ \
>>-L$
On 2010-08-17 15:03, Daniel Nebdal wrote:
>>> However, a disadvantage is that the built-in search paths of the
>>> bootstrap compiler are not entirely disabled by using the -isysroot, -B
>>> and -L flags,
...
> For clarification, did you (Dimitry, that is) mean
> a) The paths are still there so the
On Tue, 17 Aug 2010 13:32:39 +0200
Dimitry Andric wrote:
> Hi,
>
> Since clang has gone into the tree, there has been an effort to get
> head in a state where world can optionally be built with it. A
> number of changes required for this have already been committed,
> mainly thanks to Ed Schout
On Tue, Aug 17, 2010 at 1:49 PM, Bob Bishop wrote:
> On 17 Aug 2010, at 12:32, Dimitry Andric wrote:
>
>> However, a disadvantage is that the built-in search paths of the
>> bootstrap compiler are not entirely disabled by using the -isysroot, -B
>> and -L flags,
>
> This could be viewed as a bug .
On 2010-08-17 13:49, Bob Bishop wrote:
>> However, a disadvantage is that the built-in search paths of the
>> bootstrap compiler are not entirely disabled by using the -isysroot, -B
>> and -L flags,
>
> This could be viewed as a bug ...
It is probably a bit more complicated than that. Let me exp
Hi,
On 17 Aug 2010, at 12:32, Dimitry Andric wrote:
> Hi,
>
> Since clang has gone into the tree, there has been an effort to get head
> in a state where world can optionally be built with it.
> [...]
> Now, for building clang as the bootstrap compiler, there are basically
> two methods to make
* Dimitry Andric wrote:
> On 2010-08-17 13:40, Ed Schouten wrote:
> >> +#ifndef __FreeBSD__
> >> + AddPath(CLANG_PREFIX "/usr/local/include", System, true, false, false);
> >> +#endif
> >>
> >>// Builtin includes use #include_next directives and should be
> >> positioned
> >>// just pr
On 2010-08-17 13:40, Ed Schouten wrote:
>> +#ifndef __FreeBSD__
>> + AddPath(CLANG_PREFIX "/usr/local/include", System, true, false, false);
>> +#endif
>>
>>// Builtin includes use #include_next directives and should be positioned
>>// just prior C include dirs.
>
> Hmmm... Do we really
Hello Dimitry!
* Dimitry Andric wrote:
> @@ -408,9 +411,10 @@ static bool getWindowsSDKDir(std::string &path) {
>
> void InitHeaderSearch::AddDefaultCIncludePaths(const llvm::Triple &triple,
> const HeaderSearchOptions
> &HSOpts) {
> -#if 0 /* Remo
ood way to solve the bootstrap compiler issue.
I have also attached two patches to this mail, which can be applied to
head, to show the exact set of changes required for each method.
The "isysroot" method for building world with clang.
First of all, Makefile.inc1 is modified to build
On Tue, Jun 22, 2010 at 04:39:17PM -0400, Ryan Stone wrote:
> I saw similar behaviour a couple of years ago when I switched from
> using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
> The problem ended up being a change in the linker script used by GNU
> ld for linking kernel mod
I saw similar behaviour a couple of years ago when I switched from
using gcc 4.0.2 to gcc 4.3.0 to compile some out-of-tree KLD modules.
The problem ended up being a change in the linker script used by GNU
ld for linking kernel modules. It used to always put some magic
symbols used by the linker t
On Wednesday 31 March 2010 14:52:53 Giorgos Keramidas wrote:
> On Tue, 30 Mar 2010 15:10:58 -0400, John Baldwin wrote:
> > On Tuesday 30 March 2010 11:48:58 am Giorgos Keramidas wrote:
> >> +.It Va DEBUG_FLAGS
> >> +Defines a set of debugging flags that will be used to build all
> >> userland +bin
* Mike Bohan <[EMAIL PROTECTED]> [ Date: 2003-06-12 ]
[ w.r.t. error building world ]
> Hey there,
>
> I recently ran into a problem when building updated (via cvsup) world
> from -CURRENT.
This smells like a sed bug. Rebuild and install sed, and try again
Hey there,
I recently ran into a problem when building updated (via cvsup) world
from -CURRENT.
Some background information:
FreeBSD caboose.shortcircut.org 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Wed
Jun 4 19:39:23 EDT 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/CABOOSE i386
This is
--- Soeren Schmidt <[EMAIL PROTECTED]> wrote:
> It seems Shizuka Kudo wrote:
> >
> >
> > I have "sysctl -a" showing "hw.ata.ata_dma: 1", but "atacontrol mode" showing
> > "PIO4" for the
> > drives attached to HP370A. Setting them to mode "udma6" was just ignored.
>
> Fixed!
>
> -Søren
>
Sør
It seems Shizuka Kudo wrote:
>
> --- Bruce Cran <[EMAIL PROTECTED]> wrote:
> >
> > Just to add to this, when I run the above 'dd' command, I see top reporting 35-40%
> > interrupt
> > usage on the drive on the RAID controller, while it's
> > 3-5% for the drive on the VIA controller, and the driv
--- Bruce Cran <[EMAIL PROTECTED]> wrote:
>
> Just to add to this, when I run the above 'dd' command, I see top reporting 35-40%
> interrupt
> usage on the drive on the RAID controller, while it's
> 3-5% for the drive on the VIA controller, and the drive itself is:
>
> 0 READY ad4: 58644MB [11
On Fri, Feb 28, 2003 at 03:06:15PM +, Bruce Cran wrote:
> On Fri, Feb 28, 2003 at 04:21:51AM -0800, Shizuka Kudo wrote:
> > I recently cvsup-ped -current (I believe it was 27 Feb), and noticed that the
> > system was not
> > responsive as before when building world. Loo
On Fri, Feb 28, 2003 at 04:21:51AM -0800, Shizuka Kudo wrote:
> I recently cvsup-ped -current (I believe it was 27 Feb), and noticed that the system
> was not
> responsive as before when building world. Looking at the output of "top" showed a
> 30-60% interrupt
> usage.
I recently cvsup-ped -current (I believe it was 27 Feb), and noticed that the system
was not
responsive as before when building world. Looking at the output of "top" showed a
30-60% interrupt
usage. I believed it is related to my highpoint 370 card running at raid 1. I
detached the
Symptom:
===> sbin/ifconfig
cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
-Wmissing-prototypes -Wcast-qual -Wwrite-strings -Wnested-externs -I..-c
/usr/src/sbin/ifconfig/ifconfig.c
cc -O -pipe -DUSE_IF_MEDIA -DINET6 -DUSE_VLANS -DUSE_IEEE80211 -DNS -Wall
-Wmi
This could have been caused by (ab)using -DNOCLEAN.
On Mon, Jun 10, 2002 at 09:48:29PM +1000, Scott Penno wrote:
> Hi there,
>
> I've been attempting to build current on and off over the past few weeks with little
>success. Problems occur when making dependencies within kdump as shown below.
Hi there,
I've been attempting to build current on and off over the past few weeks with little
success. Problems occur when making dependencies within kdump as shown below.
Sources last update June 9, 2002 at 12:30 GMT. I've been through UPDATING, README and
mailling lists to no avail. Any
On Wed, 10 Jan 2001, Ruslan Ermilov wrote:
> On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote:
> > How do I remake sendmail without making a buildworld?
> >
> > I'm experimenting with cyrus-sasl and sendmail.
> >
> > cd /usr/src/contrib/sendmail && make
> >
> > doesn't work, becau
On Wed, Jan 10, 2001 at 03:22:30PM +0100, Leif Neland wrote:
> How do I remake sendmail without making a buildworld?
>
> I'm experimenting with cyrus-sasl and sendmail.
>
> cd /usr/src/contrib/sendmail && make
>
> doesn't work, because there is no Build there.
>
> I could import the original s
How do I remake sendmail without making a buildworld?
I'm experimenting with cyrus-sasl and sendmail.
cd /usr/src/contrib/sendmail && make
doesn't work, because there is no Build there.
I could import the original source from sendmail.org, but I'd rather
not; I'd prefer using the paths and fla
Ben Rosengart wrote:
>
> If I recall correctly, someone posted recently that the time is not far
> off when one will be able to make world on an older, pre-signals-change
> system.
You can already do a buildworld, but you still have to make and install
a new kernel in order to do a installworld.
If I recall correctly, someone posted recently that the time is not far
off when one will be able to make world on an older, pre-signals-change
system.
Is there going to be an announcement when that happens, or has it
perhaps happened already? I'm running an Oct 1 -current box, and I will
eventu
> In gnu/usr.bin/cc mine fails as well, but complains of a missing
> `hconfig.h`, which in turn causes a screenfull of errrors.
cd /usr/src
make cleandir ; make cleandir
then build your world normally and tell me if you still have the error.
--
-- David(obr...@nuxi.com -or- obr
> gnu/usr.bin/cc mine fails as well, but complains of a missing
> `hconfig.h`, which in turn causes a screenfull of errrors. Two days ago
I know you've heard this before WRT to cc_tools/, but... is should be
fixed now.
--
-- David(obr...@nuxi.com -or- obr...@freebsd.org)
To Unsubscribe
Dana Huggard wrote:
>
> Chris Costello wrote:
> >
> > On Fri, Apr 9, 1999, Dana Huggard wrote:
> > > I see there has been some discussions around building world. I may have
> > > missed or forgotten something, or even not read the right README. Also
> &g
On Fri, Apr 9, 1999, Dana Huggard wrote:
> I see there has been some discussions around building world. I may have
> missed or forgotten something, or even not read the right README. Also
> seen some captured text of builds and where they fail. In
> gnu/usr.bin/cc mine fails
I see there has been some discussions around building world. I may have
missed or forgotten something, or even not read the right README. Also
seen some captured text of builds and where they fail. In
gnu/usr.bin/cc mine fails as well, but complains of a missing
`hconfig.h`, which in turn causes
Hi,
The following patch makes -jn work. I don't claim it's any sort of
long-term solution.
The hack consists of simply dropping .NOTPARALLEL: into the right Makefile, but
since .NOTPARALLEL is broken (see bin/10985 for the gory details) you'll
need the attached patch for make too.
Index: src/gnu
===> lib/libcom_err
===> lib/libcom_err/doc
info2html com_err.info
info2html: not found
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
*** Error code 1
Stop.
Since when do we need a port installed to build the world?
-Matt
97 matches
Mail list logo
