- Original Message ---
On Sunday, January 29th, 2023 at 3:06 PM, qroxana
wrote:
> It appears buildworld doesn't create the obj directory for
> usr.bin/clang/llvm-objcopy in stage 2.2 after this commit.
>
> commit adc3c128c6603054586a993d117e5dd808deac17
> Author: John Baldwin j...@fre
--- Original Message ---
On Monday, January 23rd, 2023 at 1:44 PM, qroxana
wrote:
> --- Original Message ---
> On Monday, January 23rd, 2023 at 10:02 AM, Dimitry Andric d...@freebsd.org
> wrote:
>
>
>
> > On 23 Jan 2023, at 04:05, qroxana qrox...@protonmail.com wrote:
> >
--- Original Message ---
On Monday, January 23rd, 2023 at 10:02 AM, Dimitry Andric
wrote:
> On 23 Jan 2023, at 04:05, qroxana qrox...@protonmail.com wrote:
>
> > It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy.
> >
> > --- all_subdir_usr.bin ---
> > --- objwarn -
On 23 Jan 2023, at 04:05, qroxana wrote:
>
> It seems ${MAKEOBJDIR} was not created for usr.bin/clang/llvm-objcopy.
>
> --- all_subdir_usr.bin ---
> --- objwarn ---
> Warning: Object directory not changed from original
> /usr/src/usr.bin/clang/llvm-objcopy
This is usually an indication that yo
On 8/2/22 15:45, Warner Losh wrote:
On Tue, Feb 8, 2022 at 3:43 AM George Abdelmalik
wrote:
On 7/2/22 03:50, qroxana wrote:
I know running make install for
/usr/src/tools/build/test-includes can fix this,
but this still fails on a newly installed 14.0-CURRENT.
--- t
Brooks Davis wrote:
> On Tue, Feb 08, 2022 at 02:52:27PM -0800, Simon J. Gerraty wrote:
> > Brooks Davis wrote:
> > >
> > > This would be fine, but should not be necessicary. The sys subdir should
> > > be created by AUTOOBJ.
> >
> > .OBJDIR should be (and is), not .OBJDIR/sys
>
> We've had s
On Tue, Feb 08, 2022 at 02:52:27PM -0800, Simon J. Gerraty wrote:
> Brooks Davis wrote:
> >
> > This would be fine, but should not be necessicary. The sys subdir should
> > be created by AUTOOBJ.
>
> .OBJDIR should be (and is), not .OBJDIR/sys
We've had support for relative paths in SRCS since
I went ahead and committed this as 5ae6cc00111c since we chatted about it
here.
Warner
On Tue, Feb 8, 2022 at 5:10 PM Warner Losh wrote:
>
>
> On Tue, Feb 8, 2022 at 3:52 PM Simon J. Gerraty wrote:
>
>> Brooks Davis wrote:
>> >
>> > This would be fine, but should not be necessicary. The sys s
On Tue, Feb 8, 2022 at 3:52 PM Simon J. Gerraty wrote:
> Brooks Davis wrote:
> >
> > This would be fine, but should not be necessicary. The sys subdir should
> > be created by AUTOOBJ.
>
> .OBJDIR should be (and is), not .OBJDIR/sys
> making that subdir is up to the makefile and would also fix t
Brooks Davis wrote:
>
> This would be fine, but should not be necessicary. The sys subdir should
> be created by AUTOOBJ.
.OBJDIR should be (and is), not .OBJDIR/sys
making that subdir is up to the makefile and would also fix the problem,
but given the nature of what the makefile is doing just r
Warner Losh wrote:
> > Same here for me for the past couple of weeks. Haven't been able to
> > identify why it fails. My hunch was that a particular objdir wasn't
> > being created. As a workaround I edited the Makefile.inc1 to remove
> > the test-includes command (line 1128 I think).
>
> The sys
On Tue, Feb 08, 2022 at 09:56:19AM -0800, Simon J. Gerraty wrote:
> Warner Losh wrote:
> > --- sys/abi_compat.c ---
> > echo "#include " > sys/abi_compat.c
> > sh: cannot create sys/abi_compat.c: No such file or directory
> > *** [sys/abi_compat.c] Error code 2
> >
> > make[4]: stopped in /usr/sr
On Tue, Feb 8, 2022 at 10:56 AM Simon J. Gerraty wrote:
> Warner Losh wrote:
> > --- sys/abi_compat.c ---
> > echo "#include " > sys/abi_compat.c
> > sh: cannot create sys/abi_compat.c: No such file or directory
> > *** [sys/abi_compat.c] Error code 2
> >
> > make[4]: stopped in /usr/src/tools/b
Warner Losh wrote:
> --- sys/abi_compat.c ---
> echo "#include " > sys/abi_compat.c
> sh: cannot create sys/abi_compat.c: No such file or directory
> *** [sys/abi_compat.c] Error code 2
>
> make[4]: stopped in /usr/src/tools/build/test-includes
> --- sys/acct.c ---
> echo "#include " > sys/acct.c
On Tue, Feb 8, 2022 at 3:43 AM George Abdelmalik wrote:
>
> On 7/2/22 03:50, qroxana wrote:
>
>
>
> I know running make install for /usr/src/tools/build/test-includes can fix
> this,
> but this still fails on a newly installed 14.0-CURRENT.
>
> --- test-includes ---
> cd /usr/src/tools/build/test
On 7/2/22 03:50, qroxana wrote:
I know running make install for /usr/src/tools/build/test-includes can
fix this,
but this still fails on a newly installed 14.0-CURRENT.
--- test-includes ---
cd /usr/src/tools/build/test-includes; MACHINE_ARCH=aarch64
MACHINE=arm64 CPUTYPE= CC="cc -target
On 3/28/2020 4:29 AM, Brooks Davis wrote:
> On Fri, Mar 27, 2020 at 08:07:08PM +, Brooks Davis wrote:
>> On Fri, Mar 27, 2020 at 06:40:18PM +0500, Ruslan Garipov wrote:
>>> I failed to update FreeBSD 13.0-CURRENT amd64 r359231 to r359351.
>>>
>>> End of the build log:
>>>
>>> $ su root -c "make
On Fri, Mar 27, 2020 at 08:07:08PM +, Brooks Davis wrote:
> On Fri, Mar 27, 2020 at 06:40:18PM +0500, Ruslan Garipov wrote:
> > I failed to update FreeBSD 13.0-CURRENT amd64 r359231 to r359351.
> >
> > End of the build log:
> >
> > $ su root -c "make -j16 buildworld"
> > ...
> > ld: error: un
On Fri, Mar 27, 2020 at 06:40:18PM +0500, Ruslan Garipov wrote:
> I failed to update FreeBSD 13.0-CURRENT amd64 r359231 to r359351.
>
> End of the build log:
>
> $ su root -c "make -j16 buildworld"
> ...
> ld: error: unable to find library -lkyua_cli_pie
> ld: error: unable to find library -lkyua
On Fri, Jul 19, 2013 at 1:35 PM, Sam Fourman Jr. wrote:
> /usr/src/usr.bin/calendar/parsedata.c:989:17: error: null character ignored
> [-Werror,-Wnull-character]
> i = strtol (s,
>
Try looking at this file in vi. It sounds like a '\0' has somehow been
inserted into this file an
On Fri, Jul 19, 2013 at 1:53 PM, Ryan Stone wrote:
> On Fri, Jul 19, 2013 at 1:35 PM, Sam Fourman Jr. wrote:
>
>> /usr/src/usr.bin/calendar/parsedata.c:989:17: error: null character
>> ignored
>> [-Werror,-Wnull-character]
>> i = strtol (s,
>>
>
> Try looking at this file in vi.
On Thu, 30 Oct 2003, Kris Kennaway wrote:
> On Thu, Oct 30, 2003 at 08:08:08PM -0800, SteAltH FanThoM wrote:
> > yes it does!
> >
> > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
> >
> > 21.4.2 Check /etc/make.conf
> >
> > Examine the files /etc/defaults/make.conf and /
On Thu, Oct 30, 2003 at 08:08:08PM -0800, SteAltH FanThoM wrote:
> yes it does!
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
>
> 21.4.2 Check /etc/make.conf
>
> Examine the files /etc/defaults/make.conf and /etc/make.conf. The first
> contains some default defines
yes it does!
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
21.4.2 Check /etc/make.conf
Examine the files /etc/defaults/make.conf and /etc/make.conf. The first
contains some default defines - most of which are commented out. To make
use of them when you rebuild your sys
On Thu, Oct 30, 2003 at 05:03:38PM -0800, SteAltH FanThoM wrote:
> I am running 5-current the last cvs i did " 12.30 pm. today CST "
> failed on buildworld with this.
>
> ===> gnu/usr.bin/cvs/doc
> makeinfo --no-split -I /usr/src/gnu/usr.bin/cvs/doc -I
> /usr/src/gnu/usr.bin/cvs/doc/../../../.
On Mon, 9 Jun 2003 14:45:01 -0700, Marcel Moolenaar <[EMAIL PROTECTED]>
wrote:
On Mon, Jun 09, 2003 at 04:18:46PM -0500, Jeremy Messenger wrote:
I just CVSup'ed at the phk's lastest committed on UPDATING/CDD stuff. I
^^^I mean,
CCD..
di
On Mon, Jun 09, 2003 at 04:18:46PM -0500, Jeremy Messenger wrote:
> I just CVSup'ed at the phk's lastest committed on UPDATING/CDD stuff. I did
> the buildworld and it has been failed.
>
> ==
> /usr/src/contrib/binutils/bfd/targets.c -o targets.o
> In file included fro
Shizuka Kudo wrote:
> Thanks for your answer. I'm just curious why a lower
> optimization level could cause trouble than -O.
> Anyway, my -current works fine with the default
> CFLAGS. It seems that there're some commits to
> rtld-elf on today.
THe compiler is broken.
If you are that intent on c
--- Sean Chittenden <[EMAIL PROTECTED]> wrote:
>
> I ran into, what I think is the same thing as you're
> describing, a
> while ago. The short and skinny being that -O0
> doesn't compile any
> ASM which breaks things and is why you need at least
> -O to compile the
> kernel/world. ::shrug:: I
On Mon, Jun 24, 2002 at 10:09:44PM +0200, Niels Chr. Bank-Pedersen wrote:
> On Mon, Jun 24, 2002 at 11:49:02PM +0400, Sergey A. Osokin wrote:
> > Hello.
> >
> > Here is the today buildworld:
> > --
> > >>> stage 1: bootstrap tools
> > --
On Mon, Jun 24, 2002 at 11:49:02PM +0400, Sergey A. Osokin wrote:
> Hello.
>
> Here is the today buildworld:
> --
> >>> Rebuilding the temporary build tree
> --
> .
> --
> I don't know if I'm the one that observed this. Building world
> completed with default CFLAGS (-O -pipe -march=pentiumpro), but
> failed with -O0 or without optimization. /usr/src cvsupped within
> one day. Here's the error message (same for -O0 and without -O).
>
> ===> libexec/rtld-elf
> cc
On Wed, Jun 19, 2002 at 12:05:00AM +0900, Makoto Matsushita wrote:
>
> gmh003532> the fix is (yet again) to rebuild sed.
>
> Is this mean that src/usr.bin/sed should be a build-tool?
No, there was a bad commit to sed.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-cur
gmh003532> the fix is (yet again) to rebuild sed.
Is this mean that src/usr.bin/sed should be a build-tool?
-- -
Makoto `MAR' Matsushita
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On 2002.06.18 16:44:01 +, Igor Roboul wrote:
> Hello,
> I have got following error while building today's -CURRENT:
if you'd bothered to read the mailing lists a little bit more
closely you'd know that by now this issue has been discussied
in at least 2 threads already, latest one being only
-On [20010209 05:35], John Indra ([EMAIL PROTECTED]) wrote:
>Dunno whether this happens only to me, but in my machine, latest -CURRENT
>buildworld target failed with this message:
>===> share/numericdef
>make: don't know how to make nl_NL.ISO_8859-1.out. Stop
Should be fixed.
Apologies.
--
Jer
On 09-Feb-01 John Indra wrote:
> Dunno whether this happens only to me, but in my machine, latest -CURRENT
> buildworld target failed with this message:
That has been fixed, you want to cvsup and try again.
--
John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
PGP Key: http://ww
Konnichiwa wa MATSUDA-san,
-On [20010129 07:40], Munehiro Matsuda ([EMAIL PROTECTED]) wrote:
>Buildworld failed with following error:
>
>cc -O -pipe -I/usr/src/libexec/named-xfer/../../contrib/bind/port/freebsd/include
>-I/usr/src/libexec/named-xfer/../../contrib/bind/bin/named
>-I/usr/src/lib
Hi
I see no perl failure below...
M
> Hello.
> I tried make buildworld after cvsuped my source and it failed in perl
> area.
> I remove PERL_THREADED=true and tried again and it failed.
>
> ===> usr.bin/kdump
> cc -O -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace
>-I/usr/src/usr.bin/
On Sat, 26 Feb 2000, Munehiro Matsuda wrote:
> Hi all,
>
> Buildworld failed due to crypto related changes in libpam.
> With following patch, buildworld and installworld went successful for me.
This patch looks correct to me, with one change. However I think the
pam_ssh module needs to go under
40 matches
Mail list logo
