Am 2024-11-22 19:09, schrieb Ed Maste:
On Fri, 22 Nov 2024 at 12:48, Ed Maste wrote:
On Fri, 22 Nov 2024 at 09:32, Alexander Leidinger
wrote:
>
> FORTIFY_SOURCE=2 ## <--- maybe this? if yes: regression!
Yes this is very likely -- looking
Sorry about that -- now fixed by
66439659
Am 2024-11-22 18:19, schrieb Shawn Webb:
On Fri, Nov 22, 2024 at 04:20:42PM +0100, Alexander Leidinger wrote:
Am 2024-11-22 15:31, schrieb Alexander Leidinger:
> Am 2024-11-22 14:08, schrieb Ed Maste:
> > On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
> > wrote:
> > >
> > > Hi,
> > >
> > > I
On Fri, Nov 22, 2024 at 04:20:42PM +0100, Alexander Leidinger wrote:
> Am 2024-11-22 15:31, schrieb Alexander Leidinger:
> > Am 2024-11-22 14:08, schrieb Ed Maste:
> > > On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
> > > wrote:
> > > >
> > > > Hi,
> > > >
> > > > I get:
> > > > ld: error: v
On Fri, 22 Nov 2024 at 12:48, Ed Maste wrote:
>
> On Fri, 22 Nov 2024 at 09:32, Alexander Leidinger
> wrote:
> >
> > FORTIFY_SOURCE=2 ## <--- maybe this? if yes: regression!
>
> Yes this is very likely -- looking
Sorry about that -- now fixed by 66439659982c00f66d0fe002820eaa6610f69ff1
On Fri, 22 Nov 2024 at 09:32, Alexander Leidinger
wrote:
>
> FORTIFY_SOURCE=2 ## <--- maybe this? if yes: regression!
Yes this is very likely -- looking
Am 2024-11-22 15:31, schrieb Alexander Leidinger:
Am 2024-11-22 14:08, schrieb Ed Maste:
On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
wrote:
Hi,
I get:
ld: error: version script assignment of 'FBSD_1.5' to symbol
'getentropy' failed: symbol not defined
cc: error: linker command failed w
Am 2024-11-22 14:08, schrieb Ed Maste:
On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
wrote:
Hi,
I get:
ld: error: version script assignment of 'FBSD_1.5' to symbol
'getentropy' failed: symbol not defined
cc: error: linker command failed with exit code 1 (use -v to see
invocation)
This is
On Thu, 21 Nov 2024 at 04:43, Alexander Leidinger
wrote:
>
> Hi,
>
> I get:
> ld: error: version script assignment of 'FBSD_1.5' to symbol
> 'getentropy' failed: symbol not defined
> cc: error: linker command failed with exit code 1 (use -v to see
> invocation)
>
> This is with src from 2024-11-20
Hi,
I get:
ld: error: version script assignment of 'FBSD_1.5' to symbol
'getentropy' failed: symbol not defined
cc: error: linker command failed with exit code 1 (use -v to see
invocation)
This is with src from 2024-11-20 1:39pm UTC. My last build / running
world is from 2024-11-13 18:34pm U
On 31/10/24 10:32, h v wrote:
On 31.10.24 13:50, Renato Botelho wrote:
I do incremental builds using META_MODE on this system every ~ 2 weeks
and today I got an error when I tried to build world. I considered to
just clean /usr/obj and move on but decided to report it here first
for the case
On 31/10/24 10:06, David Wolfskill wrote:
On Thu, Oct 31, 2024 at 09:50:11AM -0300, Renato Botelho wrote:
I do incremental builds using META_MODE on this system every ~ 2 weeks and
today I got an error when I tried to build world. I considered to just
clean /usr/obj and move on but decided to r
On 31.10.24 13:50, Renato Botelho wrote:
I do incremental builds using META_MODE on this system every ~ 2 weeks
and today I got an error when I tried to build world. I considered to
just clean /usr/obj and move on but decided to report it here first
for the case anyone is interested.
For m
On Thu, Oct 31, 2024 at 09:50:11AM -0300, Renato Botelho wrote:
> I do incremental builds using META_MODE on this system every ~ 2 weeks and
> today I got an error when I tried to build world. I considered to just
> clean /usr/obj and move on but decided to report it here first for the case
> anyo
I do incremental builds using META_MODE on this system every ~ 2 weeks
and today I got an error when I tried to build world. I considered to
just clean /usr/obj and move on but decided to report it here first for
the case anyone is interested.
current system is running main-n273133-419249c1ca
te:
> > > > I got the following buildworld error a recent -CURRENT
> > > >
> > > > ===> stand/i386/pxeldr (all)
> > > > `kldstat.o' is up to date.
> > > > -14152 bytes available
> > > >
> > > > The same ha
te:
> > > > I got the following buildworld error a recent -CURRENT
> > > >
> > > > ===> stand/i386/pxeldr (all)
> > > > `kldstat.o' is up to date.
> > > > -14152 bytes available
> > > >
> > > > The same ha
Gordon Bergling writes:
> But I wonder why I am the only person, who hits that problem since it
> is a very plain -CURRENT build on a Hyper-V instance.
You enabled BearSSL (and consequently Veriexec), that's pretty far from
a plain build. The fact that you don't realize this leads me to suspect
t; > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling
> wrote:
> > > > > I got the following buildworld error a recent -CURRENT
> > > > >
> > > > > ===> stand/i386/pxeldr (all)
> > > > > `kldstat.o' is up to date.
> > &g
Hi Warner,
On Sat, Aug 24, 2024 at 03:21:16PM -0600, Warner Losh wrote:
> On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote:
> > On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> > > >
On Sat, Aug 24, 2024 at 1:39 PM Gordon Bergling wrote:
> Hi Warner,
>
> On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> > On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> > > I got the following buildworld error a recent -CURRENT
> > >
Hi Warner,
On Sat, Aug 24, 2024 at 01:29:55PM -0600, Warner Losh wrote:
> On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> > I got the following buildworld error a recent -CURRENT
> >
> > ===> stand/i386/pxeldr (all)
> > `kldstat.o' is up to date.
>
On Sat, Aug 24, 2024, 1:14 PM Gordon Bergling wrote:
> Hi folks,
>
> I got the following buildworld error a recent -CURRENT
>
> ===> stand/i386/pxeldr (all)
> `kldstat.o' is up to date.
> -14152 bytes available
>
> The same happens on stable/14:
>
> ==
Hi folks,
I got the following buildworld error a recent -CURRENT
===> stand/i386/pxeldr (all)
`kldstat.o' is up to date.
-14152 bytes available
The same happens on stable/14:
===> stand/i386/pxeldr (all)
-22344 bytes available
===> share/misc (all)
--- loader ---
*** [loader
On Tue, 28 Feb 2023 00:23:59 -0800 (PST), "Jeffrey Bouquet"
wrote:
> in src.conf:
>
> WITHOUT_TFTP=
>
> nevertheless, the buildworld halts in building tftp-proxy...
>
> ..
> OR it halts with too may of the below errors: the buildworld doesn't inform
> which process stopped it.
>
> l
in src.conf:
WITHOUT_TFTP=
nevertheless, the buildworld halts in building tftp-proxy...
..
OR it halts with too may of the below errors: the buildworld doesn't inform
which process stopped it.
ld.lld error: undefined symbol FreeBSD_nvlist_* [ many undefined symbols each
starting with th
> On Mar 11, 2017, at 18:24, Ngie Cooper (yaneurabeya)
> wrote:
Hi Roberto,
The sbin/setkey issue should be resolved by r315181. Thank you for the
report!
Cheers,
-Ngie
signature.asc
Description: Message signed with OpenPGP using GPGMail
In message
, Roberto Rodriguez Jr writes:
> Hey,
>
> Even with a fresh checkout of sources ( today 935am EST). Buildworld/kernel
> fail 10 seconds into build.
Can you post output, please?
--
Cheers,
Cy Schubert
FreeBSD UNIX: Web: http://www.FreeBSD.org
The need of the many outw
In message <1c4e6a09-86ad-4dc7-aa65-336a1643e...@freebsd.org>, Dimitry
Andric w
rites:
>
>
> --Apple-Mail=_41B95E0F-96E1-4E0A-A996-DE3C34E4B13B
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain;
> charset=us-ascii
>
> On 12 Mar 2017, at 02:46, Cy Schubert wrote:
> >
> > In me
Hey,
Even with a fresh checkout of sources ( today 935am EST). Buildworld/kernel
fail 10 seconds into build.
Thanks
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
Am Sat, 11 Mar 2017 19:37:32 -0700
Ian Lepore schrieb:
> On Sun, 2017-03-12 at 13:27 +1100, Lawrence Stewart wrote:
> > Hi Ian,
> >
> > On 12/03/2017 10:29, Ian Lepore wrote:
> > >
> > > On Sun, 2017-03-12 at 10:22 +1100, Lawrence Stewart wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I'm
On 12 Mar 2017, at 02:46, Cy Schubert wrote:
>
> In message <5cb065b0-5a7d-4a50-a722-8ea579a67...@freebsd.org>, Dimitry
> Andric w
> rites:
>>
>>
>> --Apple-Mail=_A0AD1F4B-1279-4DA7-85F9-FB9846A878D7
>> Content-Transfer-Encoding: quoted-printable
>> Content-Type: text/plain;
>> charset=us-
On 12/03/2017 13:37, Ian Lepore wrote:
> On Sun, 2017-03-12 at 13:27 +1100, Lawrence Stewart wrote:
>> Hi Ian,
>>
>> On 12/03/2017 10:29, Ian Lepore wrote:
>>>
>>> On Sun, 2017-03-12 at 10:22 +1100, Lawrence Stewart wrote:
Hi all,
I'm unable to complete buildworld with 2 recent
On Sun, 2017-03-12 at 13:27 +1100, Lawrence Stewart wrote:
> Hi Ian,
>
> On 12/03/2017 10:29, Ian Lepore wrote:
> >
> > On Sun, 2017-03-12 at 10:22 +1100, Lawrence Stewart wrote:
> > >
> > > Hi all,
> > >
> > > I'm unable to complete buildworld with 2 recent svn revs I've
> > > tried
> > > (r31
> On Mar 11, 2017, at 18:27, Lawrence Stewart wrote:
>
> Hi Ian,
…
>> The MAKEOBJDIRPREFIX variable must be set in the environment, not in
>> make.conf or on the make command line (documented in build(7)).
>
> Your assertion seems at odds with my past experience and my reading of
> the man pa
Hi Ian,
On 12/03/2017 10:29, Ian Lepore wrote:
> On Sun, 2017-03-12 at 10:22 +1100, Lawrence Stewart wrote:
>> Hi all,
>>
>> I'm unable to complete buildworld with 2 recent svn revs I've tried
>> (r314838 and r315059). I'm building for a slightly resource
>> constrained
>> production system so am
> On Mar 11, 2017, at 15:51, Roberto Rodriguez Jr
> wrote:
>
> I figured the script command... here is the new error r315090
>
> --- .depend ---
> echo setkey.full: /usr/obj/usr/src/tmp/usr/lib/libc.a
> /usr/obj/usr/src/tmp/usr/lib/libl.a
> /usr/obj/usr/src/tmp/usr/lib/liby.a
> /usr/obj/usr/sr
In message <5cb065b0-5a7d-4a50-a722-8ea579a67...@freebsd.org>, Dimitry
Andric w
rites:
>
>
> --Apple-Mail=_A0AD1F4B-1279-4DA7-85F9-FB9846A878D7
> Content-Transfer-Encoding: quoted-printable
> Content-Type: text/plain;
> charset=us-ascii
>
> On 12 Mar 2017, at 01:55, Roberto Rodriguez Jr
Thanks!
Rechecking out src tree. It seems my errors are like u said about 'make
delete-old'
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr.
On 12 Mar 2017, at 01:55, Roberto Rodriguez Jr wrote:
>
> Now...
> make buildworld
...
> In file included from /usr/src/contrib/llvm/lib/Support/APInt.cpp:15:
> In file included from /usr/src/contrib/llvm/include/llvm/ADT/APInt.h:20:
> In file included from
> /usr/src/contrib/llvm/include/llvm/Su
Now...
make buildworld
root@krsna:/usr/src # time make buildworld
--
>>> World build started on Sun Mar 12 00:52:52 UTC 2017
--
--
/groff] Error code 2
make[2]: stopped in /usr/src
--- _bootstrap-tools-lib/clang/libllvmminimal ---
--- Support/APInt.o ---
1 error generated.
*** [Support/APInt.o] Error code 1
make[3]: stopped in /usr/src/lib/clang/libllvmminimal
--- Support/CommandLine.o ---
1 error generated.
*** [Support/Com
gt;
> make[4]: stopped in /usr/src/secure/lib
> 1 error
>
> make[4]: stopped in /usr/src/secure/lib
> *** [all_subdir_secure/lib] Error code 2
>
> make[3]: stopped in /usr/src/secure
> 1 error
>
> make[3]: stopped in /usr/src/secure
> *** [all_subdir_secure]
[1]: stopped in /usr/src
1 error
make[1]: stopped in /usr/src
*** [buildworld] Error code 2
make: stopped in /usr/src
1 error
make: stopped in /usr/src
1551.754u 434.064s 17:54.86 184.7% 12598+328k 113045+55926io 25455pf+14w
___
freebsd-current@free
On Sun, 2017-03-12 at 10:22 +1100, Lawrence Stewart wrote:
> Hi all,
>
> I'm unable to complete buildworld with 2 recent svn revs I've tried
> (r314838 and r315059). I'm building for a slightly resource
> constrained
> production system so am specifying custom settings and a different
> obj
> tree
Hi all,
I'm unable to complete buildworld with 2 recent svn revs I've tried
(r314838 and r315059). I'm building for a slightly resource constrained
production system so am specifying custom settings and a different obj
tree location so I can copy it to the target system. The error persists
after a
hello,
buildworld currently breaks while building kerberos5. Sorry i cant post the
error still managing to learn how script works.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
On Mon, 7 Nov 2016 20:53:46 -0500
Ryan Stone wrote:
> I just got the following error attempting to build r308430 with my
> source tree on a read-only NFS mount. I can work around it for now,
> but shouldn't the source tree be untouched during a buildworld?
>
> $ make -j4 buildworld buildkernel
I just got the following error attempting to build r308430 with my source
tree on a read-only NFS mount. I can work around it for now, but shouldn't
the source tree be untouched during a buildworld?
$ make -j4 buildworld buildkernel
--- buildworld ---
make[1]: "/repos/users/rstone/freebsd/Makefil
Index: addrtoname.c
===
--- addrtoname.c (revision 259658)
+++ addrtoname.c (working copy)
@@ -33,9 +33,11 @@
#endif
#ifdef __FreeBSD__
+#ifdef HAVE_LIBCAPSICUM
#include
#include
#endif
+#endif
#include
#ifdef USE_ETHER
ping !
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
/usr/src/usr.sbin/tcpdump/tcpdump/../../../contrib/tcpdump/addrtoname.c:36:10:
fatal error: 'libcapsicum.h' file not found
#include
I have, notably, WITHOUT_CAPSICUM=1 in /etc/src.conf.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd
Em Thu, 14 Nov 2013 13:51:59 +0100, Dimitry Andric escreveu
> On 14 Nov 2013, at 00:23, Nilton Jose Rizzo
> wrote: ...
> > ===> lib/libc++ (all)
> > c++ -O2 -pipe -I/usr/src/lib/libc++/../../contrib/libc++/include -
I/usr/src/li
> > b/libc++/../../contrib/libcxxrt -nostdlib -DLIBCXXRT -Qunused-
On 14 Nov 2013, at 00:23, Nilton Jose Rizzo wrote:
...
> ===> lib/libc++ (all)
> c++ -O2 -pipe -I/usr/src/lib/libc++/../../contrib/libc++/include
> -I/usr/src/li
> b/libc++/../../contrib/libcxxrt -nostdlib -DLIBCXXRT -Qunused-arguments
> -fstack-
> protector -Wno-empty-body -Wno-string-plus-in
Hi all, I have some problens with -current:
building shared library librpcsvc.so.5
===> lib/libsbuf (all)
===> lib/libtacplus (all)
===> lib/libutil (all)
===> lib/libypclnt (all)
===> lib/libcxxrt (all)
===> lib/libc++ (all)
c++ -O2 -pipe -I/usr/src/lib/libc++/../../contrib/libc++/incl
Hi all!
I have a error when try to update my system to latest -HEAD, getting
through svnup.
uname -a:
FreeBSD MYBSD 10.0-CURRENT FreeBSD 10.0-CURRENT #0: Mon Aug 12 22:31:24
MSK 2013 xmy@MYBSD:/usr/obj/usr/src/sys/MYBSD amd64
/etc/src.conf
WITHOUT_ACCT=YES
#WITHOUT_A
l)
> >>>>> ===> lib/clang/libllvmexecutionengine (all)
> >>>>> ===> lib/clang/libllvminterpreter (all)
> >>>>> ===> lib/clang/libllvmjit (all)
> >>>>> ===> lib/clang/libllvmmcdisassembler (all)
>
ine (all)
>>>>> ===> lib/clang/libllvminterpreter (all)
>>>>> ===> lib/clang/libllvmjit (all)
>>>>> ===> lib/clang/libllvmmcdisassembler (all)
>>>>> ===> lib/clang/libllvmmcjit (all)
>>>&g
t;> ===> lib/clang/libllvmx86utils (all)
>>>> ===> lib/clang/libllvmdebuginfo (all)
>>>> ===> lib/clang/libllvmexecutionengine (all)
>>>> ===> lib/clang/libllvminterpreter (all)
>>>> ===> lib/clang/libllvmjit (all)
>>>> ==
libllvmexecutionengine (all)
>>> ===> lib/clang/libllvminterpreter (all)
>>> ===> lib/clang/libllvmjit (all)
>>> ===> lib/clang/libllvmmcdisassembler (all)
>>> ===> lib/clang/libllvmmcjit (all)
>>> ===> lib/clang/libllvmruntimedyld (all)
> ===> lib/clang/libllvmmcdisassembler (all)
>> ===> lib/clang/libllvmmcjit (all)
>> ===> lib/clang/libllvmruntimedyld (all)
>> ===> lib/clang/include (all)
>> 1 error
>> *** [everything] Error code 2
>> 1 error
>> *** [buildworld] Error
lib/clang/libllvmmcdisassembler (all)
===> lib/clang/libllvmmcjit (all)
===> lib/clang/libllvmruntimedyld (all)
===> lib/clang/include (all)
1 error
*** [everything] Error code 2
1 error
*** [buildworld] Error code 2
1 error
Because you are making buildworld with -j, the actual error message is
n
ll)
===> lib/clang/libllvmmcjit (all)
===> lib/clang/libllvmruntimedyld (all)
===> lib/clang/include (all)
1 error
*** [everything] Error code 2
1 error
*** [buildworld] Error code 2
1 error
___
freebsd-current@freebsd.org mailing list
http://lists.fr
> curr...@freebsd.org] On Behalf Of Anton Shterenlikht
> Sent: Sunday, May 13, 2012 11:54 PM
> To: freebsd-current@freebsd.org
> Subject: [clang] r234928 amd64 buildworld error
>
> clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-
> protector
> -Wsystem-headers
clang -O2 -pipe -DSORT_THREADS -std=gnu99 -Qunused-arguments -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict
-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwri
te-strings -Wswitch -Wshadow -Wunused-parameter -Wcast-al
"make -j4 buildworld " error
--
>>> World build started on Tue Apr 24 21:32:26 CST 2012
--
--
On Sat, 1 Oct 2011 07:55:34 -0500
Greg Miller wrote:
> On 9/30/11, Conrad J. Sabatier wrote:
> > On Wed, 28 Sep 2011 19:57:55 -0500
> > Greg Miller wrote:
> >
> >> On a fresh install of 9.0B2, I've updated my source to RELENG_9
> >> with csup, and I get the following when I try to make buildwor
On 9/30/11, Conrad J. Sabatier wrote:
> On Wed, 28 Sep 2011 19:57:55 -0500
> Greg Miller wrote:
>
>> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
>> csup, and I get the following when I try to make buildworld:
>>
>> *
>> [0] /usr/src # m
On Wed, 28 Sep 2011 19:57:55 -0500
Greg Miller wrote:
> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
> csup, and I get the following when I try to make buildworld:
>
> *
> [0] /usr/src # make clean buildworld
> find: /usr/src/sys/sys/pa
On 9/29/11, Greg Miller wrote:
> On 9/28/11, Adrian Chadd wrote:
>> On 29 September 2011 08:57, Greg Miller wrote:
>>> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
>>> csup, and I get the following when I try to make buildworld:
>>
>> Good, is this reproducable? There's a
On 9/28/11, Adrian Chadd wrote:
> On 29 September 2011 08:57, Greg Miller wrote:
>> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
>> csup, and I get the following when I try to make buildworld:
>
> Good, is this reproducable? There's a patch to csup that may help you
> out
On 29 September 2011 08:57, Greg Miller wrote:
> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
> csup, and I get the following when I try to make buildworld:
Good, is this reproducable? There's a patch to csup that may help you
out with this.
Index: src/usr.bin/csup/fixups
On 9/28/11, Garrett Cooper wrote:
> On Wed, Sep 28, 2011 at 8:54 PM, Greg Miller wrote:
>> On 9/28/11, Garrett Cooper wrote:
>>> On Wed, Sep 28, 2011 at 5:57 PM, Greg Miller
>>> wrote:
On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
csup, and I get the following w
On Wed, Sep 28, 2011 at 8:54 PM, Greg Miller wrote:
> On 9/28/11, Garrett Cooper wrote:
>> On Wed, Sep 28, 2011 at 5:57 PM, Greg Miller wrote:
>>> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
>>> csup, and I get the following when I try to make buildworld:
>
> [snip]
>
>>
On 9/28/11, Garrett Cooper wrote:
> On Wed, Sep 28, 2011 at 5:57 PM, Greg Miller wrote:
>> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
>> csup, and I get the following when I try to make buildworld:
[snip]
> If you do ls /usr/src/sys , it's probably missing.
[0] /usr/s
On Wed, Sep 28, 2011 at 5:57 PM, Greg Miller wrote:
> On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
> csup, and I get the following when I try to make buildworld:
>
> *
> [0] /usr/src # make clean buildworld
> find: /usr/src/sys/sys/param.
On a fresh install of 9.0B2, I've updated my source to RELENG_9 with
csup, and I get the following when I try to make buildworld:
*
[0] /usr/src # make clean buildworld
find: /usr/src/sys/sys/param.h: No such file or directory
"/usr/src/Makefile", line 217: warn
I am seeing the following error and no amount of cvsup will help it.
http://ns2.wananchi.com/~wash/5.1-REL/WORLD.txt
Advise appreciated.
-Wash
--
|\ _,,,---,,_ | Odhiambo Washington<[EMAIL PROTECTED]>
Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com
|,
On Sun, Nov 09, 2003 at 07:32:57PM -0500, Jason wrote:
> Ok, here is the last section of output and the error. After this if I
> do ethier gzip command I get an error, but if I enter the makeinfo
> commands first the gzip command then works. Could this be some kind of
> schedualling problem be
Ok, here is the last section of output and the error. After this if I
do ethier gzip command I get an error, but if I enter the makeinfo
commands first the gzip command then works. Could this be some kind of
schedualling problem because I normally use the command $time make -j4
buildworld.
Date: Sat, 1 Nov 2003 12:23:37 -0800 (PST)
From: Jean-Marc Zucconi <[EMAIL PROTECTED]>
Subject: Re: buildworld error: rm: tar: is a directory
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
eculp writes:
> Mensaje citado por Ruslan Ermilov &l
In message: <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
: Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>:
:
: | cvs update -PAd
: |
: | Pruning is very important.
:
: Warner,
:
: It hadn't even dawned on me but, after several days of suffering with this
: problem, I couldn
Mensaje citado por "M. Warner Losh" <[EMAIL PROTECTED]>:
| cvs update -PAd
|
| Pruning is very important.
Warner,
It hadn't even dawned on me but, after several days of suffering with this
problem, I couldn't agree more. I am converted, believe me. I will be doing
that more often. I've become
Mensaje citado por Jean-Marc Zucconi <[EMAIL PROTECTED]>:
| > eculp writes:
|
| > Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>:
| > | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
| > | > I'm having problems with current buildworld in gnu now on two
| differen
cvs update -PAd
Pruning is very important.
Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
> eculp writes:
> Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>:
> | On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
> | > I'm having problems with current buildworld in gnu now on two different
> | > machines in current(today). The latest is the following:
>
Mensaje citado por Ruslan Ermilov <[EMAIL PROTECTED]>:
| On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
| > I'm having problems with current buildworld in gnu now on two different
| > machines in current(today). The latest is the following:
| >
| > rm: tar: is a directory
| >
On Sat, Nov 01, 2003 at 04:48:42AM -0800, [EMAIL PROTECTED] wrote:
> I'm having problems with current buildworld in gnu now on two different
> machines in current(today). The latest is the following:
>
> rm: tar: is a directory
> *** Error code 1
>
> Stop in /usr/src/gnu/usr.bin/tar.
> *** Error
I'm having problems with current buildworld in gnu now on two different
machines in current(today). The latest is the following:
rm: tar: is a directory
*** Error code 1
Stop in /usr/src/gnu/usr.bin/tar.
*** Error code 1
Stop in /usr/src/gnu/usr.bin/tar.
*** Error code 1
Stop in /usr/src/gnu/u
At 2:29 PM -0500 6/11/03, Scot W. Hetzel wrote:
From: "Munehiro Matsuda" <[EMAIL PROTECTED]>
> I was having the same compile error, until I commeted out
> the BDECFLAGS definition from /etc/make.conf.
>
> Looking into the problematic Makefiles, I've found that
> following Makefiles do referenc
From: "Munehiro Matsuda" <[EMAIL PROTECTED]>
> I was having the same compile error, until I commeted out the
> BDECFLAGS definition from /etc/make.conf.
>
> Looking into the problematic Makefiles, I've found that following
> Makefiles do references BDECFLAGS, which matches errors I was getting:
>
>
Hi all,
On Tue Jun 10, 2003 at 07:50PM -0400, Garance A Drosihn wrote:
> At 9:42 PM +0200 6/10/03, Gordon Bergling wrote:
> >Since I disable BDECFLAGS in /etc/make.conf this problem goes
> >away. I don't know if this effects the build process in any
> >other way. I had enable them around 4.5-RELEA
Hi all,
From: Garance A Drosihn <[EMAIL PROTECTED]>
Date: Tue, 10 Jun 2003 19:50:08 -0400
::At 9:42 PM +0200 6/10/03, Gordon Bergling wrote:
::>Hi all,
::>
::>Since I disable BDECFLAGS in /etc/make.conf this problem goes
::>away. I don't know if this effects the build process in any
::>other way.
On Tue, Jun 10, 2003 at 10:57:19PM +0200, Gordon Bergling wrote:
> <-From /etc/make.conf -->
> # BDECFLAGS are a set of gcc warning settings that Bruce Evans has
> # suggested
> # for use in developing FreeBSD and testing changes. They can be used
>
At 9:42 PM +0200 6/10/03, Gordon Bergling wrote:
Hi all,
Since I disable BDECFLAGS in /etc/make.conf this problem goes
away. I don't know if this effects the build process in any
other way. I had enable them around 4.5-RELEASE or so. ;)
I'm not sure what you mean by that. Did you remove a line
wh
On Tue Jun 10, 2003 at 01:17PM -0700, Kris Kennaway wrote:
> > Since I disable BDECFLAGS in /etc/make.conf this problem goes away. I
> > don't know if this effects the build process in any other way. I had
> > enable them around 4.5-RELEASE or so. ;)
>
> That's entirely expected. Whatever gave yo
On Tue, Jun 10, 2003 at 09:42:08PM +0200, Gordon Bergling wrote:
> Hi all,
>
> On Mon Jun 09, 2003 at 11:09PM +0200, Gordon Bergling wrote:
> > On Mon Jun 09, 2003 at 11:06PM +0300, Ruslan Ermilov wrote:
> > > On Mon, Jun 09, 2003 at 06:42:11PM +0200, Gordon Bergling wrote:
> > > > since a few day
Hi all,
On Mon Jun 09, 2003 at 11:09PM +0200, Gordon Bergling wrote:
> On Mon Jun 09, 2003 at 11:06PM +0300, Ruslan Ermilov wrote:
> > On Mon, Jun 09, 2003 at 06:42:11PM +0200, Gordon Bergling wrote:
> > > since a few days I getting a curious error when I try to build the
> > > world. Iam using -C
On Mon Jun 09, 2003 at 11:06PM +0300, Ruslan Ermilov wrote:
> On Mon, Jun 09, 2003 at 06:42:11PM +0200, Gordon Bergling wrote:
> > since a few days I getting a curious error when I try to build the
> > world. Iam using -CURRENT, with sources from a few minutes ago.
> > The first error with full err
On Mon, Jun 09, 2003 at 06:42:11PM +0200, Gordon Bergling wrote:
> Hi folks,
>
> since a few days I getting a curious error when I try to build the
> world. Iam using -CURRENT, with sources from a few minutes ago.
> The first error with full error messages can be found on
> http://www.0xfce3.net/e
Hi folks,
since a few days I getting a curious error when I try to build the
world. Iam using -CURRENT, with sources from a few minutes ago.
The first error with full error messages can be found on
http://www.0xfce3.net/error.txt. It seems that src/usr.sbin/config was
broken. After the commit of t
1 - 100 of 115 matches
Mail list logo
