The only solution that I found was to delete /usr/obj/... and build from
scratch.
Cheers
David Wolfskill escreveu (segunda, 21/10/2024 à(s)
21:36):
> On Mon, Oct 21, 2024 at 08:02:50PM +0100, void wrote:
> > On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:
> >
> > > This is in m
On Mon, Oct 21, 2024 at 08:02:50PM +0100, void wrote:
> On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:
>
> > This is in meta-mode, on a 32x2 Epyc running "make -j 112 buildworld".
>
> I'm just guessing here - but ISTR that with large -j that sometimes a build
> failure can occur
On Sun, Oct 20, 2024 at 05:14:29AM -0700, David Wolfskill wrote:
This is in meta-mode, on a 32x2 Epyc running "make -j 112 buildworld".
I'm just guessing here - but ISTR that with large -j that sometimes a build
failure can occur. I've just had one where I forgot where I was and ran a -j10
bui
Hello,
Same here with meta-mode on a i7 laptop.
David Wolfskill escreveu (domingo, 20/10/2024 à(s)
13:15):
> Running:
> FreeBSD freebeast.catwhisker.org 15.0-CURRENT FreeBSD 15.0-CURRENT #5
> main-n273063-4ad443a106d3: Sat Oct 19 10:38:11 UTC 2024
> r...@freebeast.catwhisker.org:/common/S4/obj/
On 07/30/2024 9:25 am, Larry Rosenman wrote:
On 07/30/2024 9:22 am, Ed Maste wrote:
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
I'm getting the following on an up2date checkout:
Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
ld: warning:
/usr/obj/usr/src/amd64.a
On 07/30/2024 9:22 am, Ed Maste wrote:
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
I'm getting the following on an up2date checkout:
Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
ld: warning: /usr/obj/usr/src/amd64.amd64/lib/clang/libllvm/libllvm.a:
archive membe
On Mon, 29 Jul 2024 at 19:54, Larry Rosenman wrote:
>
> I'm getting the following on an up2date checkout:
> Building /usr/obj/usr/src/amd64.amd64/usr.bin/clang/clang/clang.full
> ld: warning: /usr/obj/usr/src/amd64.amd64/lib/clang/libllvm/libllvm.a:
> archive member 'FaultMaps.o' is neither ET_REL
Nice to see that upstream chose the more correct solution. :)
-Dimitry
> On 2 May 2024, at 11:57, Nuno Teixeira wrote:
>
> Hello Dimitry,
>
> I've quoted your words in upstream PR and it solved with:
>
> Stop using namespace std
> https://github.com/amsynth/amsynth/commit/6fb79100a6254220e5ad
Hello Dimitry,
I've quoted your words in upstream PR and it solved with:
Stop using namespace std
https://github.com/amsynth/amsynth/commit/6fb79100a6254220e5adc69a1428572539ecc377
I'm using patch globally that unbreak main and rest of supported releases
don't complaint about it.
Thanks!
Dimit
On 30 Apr 2024, at 14:26, Nuno Teixeira wrote:
>
> I'm lost on build failure of audio/amsynth (updated to version 1.13.3) on
> recent main.
> Thre strange thing is if I use llvm from ports, USES+=llvm, it fails with
> same error so I suspect that something related to main.
>
> Any help is welc
> > > This could be a dependency issue; would you check if removing the
> > > following $OBJTOP subdirs addresses the issue:
> > >
> > > secure/lib/libcrypto
> > > secure/lib/libssl
> > > obj-lib32/secure/lib/libcrypto
> > > obj-lib32/secure/lib/libssl
> > >
> The build was successful; after the re
On Sat, Jun 24, 2023 at 09:09:00AM -0700, David Wolfskill wrote:
> On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote:
> > ...
> > > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level"
> > > # error "OPENSSL_API_COMPAT expresses an impossible API compatibility
> > > level
On Sat, Jun 24, 2023 at 10:39:57AM -0400, Ed Maste wrote:
> ...
> > : "OPENSSL_API_COMPAT expresses an impossible API compatibility level"
> > # error "OPENSSL_API_COMPAT expresses an impossible API compatibility
> > level"
> >^
>
> This could be a dependency issue; would you check if removi
On Sat, 24 Jun 2023 at 07:11, David Wolfskill wrote:
>
> Running:
> FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #405
> main-n263767-764464af4968: Fri Jun 23 11:42:14 UTC 2023
> r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64 140009
On Wed, May 24, 2023 at 01:39:26PM +0200, Dimitry Andric wrote:
> On 24 May 2023, at 13:25, David Wolfskill wrote:
> >
> > This is from an in-place source update from main-n263073-634a770a5e16 to
> > main-n263112-ad513b4dba3e:
> >
> > ...
> > Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/
On 24 May 2023, at 13:25, David Wolfskill wrote:
>
> This is from an in-place source update from main-n263073-634a770a5e16 to
> main-n263112-ad513b4dba3e:
>
> ...
> Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test
> Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/n
David Wolfskill wrote:
> This is from an in-place source update from main-n263073-634a770a5e16 to
> main-n263112-ad513b4dba3e:
>
> ...
> Building /common/S4/obj/usr/src/amd64.amd64/lib/libc/tests/stdio/scanf_test
> Building /common/S4/obj/usr/src/amd64.amd64/usr.bin/ncurses/dump_entry.o
> Building
On Thu, 12 Jan 2023 10:37:34 -0700
Warner Losh wrote:
> On Thu, Jan 12, 2023 at 4:44 AM David Wolfskill
> wrote:
>
> > > I had this problem also. After deleting obj/usr the buildworld
> succeeded.
> > >
> >
>
> > >
> >
> > Empirically:
> > rm -fr /usr/obj/usr/src/amd64.amd64/u
On Thu, Jan 12, 2023 at 4:44 AM David Wolfskill
wrote:
> On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote:
> > looks like we may need another 'unclean' workaround for this?
> >
> > Warner
> >
> > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote:
> > ...
> > > I had this problem al
On Fri, 13 Jan 2023 01:31:59 +0900
Tomoaki AOKI wrote:
> On Thu, 12 Jan 2023 14:41:19 +
> Gary Jennejohn wrote:
>
[SNIP]
> >
> > I installed the new world on my tower this morning. Now I see a new
> > problem.
> >
> > I don't know whether this new problem is related to the new tzcode, but
>
On Thu, 12 Jan 2023 14:41:19 +
Gary Jennejohn wrote:
> On Thu, 12 Jan 2023 03:44:03 -0800
> David Wolfskill wrote:
>
> > On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote:
> > > looks like we may need another 'unclean' workaround for this?
> > >
> > > Warner
> > >
> > > On Wed, Ja
On Thu, 12 Jan 2023 03:44:03 -0800
David Wolfskill wrote:
> On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote:
> > looks like we may need another 'unclean' workaround for this?
> >
> > Warner
> >
> > On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote:
> > ...
> > > I had this problem
On Wed, Jan 11, 2023 at 07:12:46AM -0700, Warner Losh wrote:
> looks like we may need another 'unclean' workaround for this?
>
> Warner
>
> On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote:
> ...
> > I had this problem also. After deleting obj/usr the buildworld succeeded.
> >
>
Empi
looks like we may need another 'unclean' workaround for this?
Warner
On Wed, Jan 11, 2023 at 6:32 AM Gary Jennejohn wrote:
> On Wed, 11 Jan 2023 04:05:43 -0800
> David Wolfskill wrote:
>
> > Running:
> > FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275
> main-n259988-48d
On Wed, 11 Jan 2023 04:05:43 -0800
David Wolfskill wrote:
> Running:
> FreeBSD freebeast.catwhisker.org 14.0-CURRENT FreeBSD 14.0-CURRENT #275
> main-n259988-48dc9150ac36: Tue Jan 10 12:20:47 UTC 2023
> r...@freebeast.catwhisker.org:/common/S4/obj/usr/src/amd64.amd64/sys/GENERIC
> amd64
>
On Fri, 17 Dec 2021 09:44:20 -0800
Chuck Tuffli wrote:
> When building current from git, I keep hitting the error below. This
> is with meta-mode, but I've also tried deleting the object directory.
> The system also has a couple of tweaks to src-env.conf that were an
> attempt to avoid building a
On Tue, Oct 20, 2020 at 07:15:16AM +, you (marco) sent the following to
[freebsd-current] :
> >
>
> I checked out 05b104834ae7 (r366780) from
> https://cgit-beta.freebsd.org/src.git and ran a 'make -j4 builworld and make
> -j4 buildkernel'
> for GENERIC-NODEBUG which also failed (buildworld
On Sat, Oct 03, 2020 at 10:36:30AM +0200, you (Emmanuel Vadot) sent the
following to [freebsd-current] :
> On Fri, 2 Oct 2020 19:53:44 -0500
> Patrick McMunn wrote:
>
> > I update the sources today and ran "make -j24 buildworld buildkernel
> > KERNCONF=GENERIC-NODEBUG", and the build failed. I m
On Fri, 2 Oct 2020 19:53:44 -0500
Patrick McMunn wrote:
> I update the sources today and ran "make -j24 buildworld buildkernel
> KERNCONF=GENERIC-NODEBUG", and the build failed. I made sure to "make
> clean" and "make cleanworld" and try again, and I got the same result.
>
> --
> Patrick McMunn
On Tue, Dec 5, 2017 at 2:03 PM, Ryan Stone wrote:
> So I don't fully understand why this build failure happened, but I did
> manage to find root cause. It turns out that there was a bug in make
> that caused our build infrastructure to write objects and other build
> output to the srcdir rather
So I don't fully understand why this build failure happened, but I did
manage to find root cause. It turns out that there was a bug in make
that caused our build infrastructure to write objects and other build
output to the srcdir rather than the objdir in certain cases when
using make -C. I have
Oh, and one more btw, can you cd stand; cd ` make -V .OBJDIR ` ; find .
-name machine | xargs ls -l
The only way I can see this happening is if we're doing a 32-bit build, but
pulling in the amd64 header files for some bogus reason...
Finally, what's the host OS?
Warner
On Mon, Dec 4, 2017 at
Also, can you make the full logs available? I can't recreate this with or
without DEBUG_FLAGS or CFLAGS setting in my make.conf file.
Warner
On Mon, Dec 4, 2017 at 3:59 PM, Warner Losh wrote:
> Please remove the DEBUG_FLAGS and try again. Trying to see if that's the
> culprit. It works for me w
Please remove the DEBUG_FLAGS and try again. Trying to see if that's the
culprit. It works for me with the default build.
Warner
On Mon, Dec 4, 2017 at 3:32 PM, Ryan Stone wrote:
> I'm seeing the following build failure when doing a buildworld of head:
>
> In file included from
> /repos/users/r
On Fri, Oct 20, 2017 at 3:52 PM, Michael Butler
wrote:
> If SMP is not defined, as it isn't on my last remaining i386 platform, the
> build fails with:
>
> Building /usr/obj/usr/src/sys/SARAH/kern_mutex.o
> --- kern_mutex.o ---
> /usr/src/sys/kern/kern_mutex.c:313:3: error: implicit declaration o
David Wolfskill wrote:
> On Thu, May 25, 2017 at 05:07:19AM -0700, David Wolfskill wrote:
> > This is on my "build machine"; running GENERIC/amd64 built yesterday:
> >
> > FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #353
> > r318739M/318739:1200031: Wed May 24 10:00:20 P
On Thu, May 25, 2017 at 05:07:19AM -0700, David Wolfskill wrote:
> This is on my "build machine"; running GENERIC/amd64 built yesterday:
>
Nevermind. Replacing /usr/src with a fresh checkout resolved the issue.
Peace,
davdi
--
David H. Wolfskill da...@catwhiske
On Thu, May 25, 2017 at 05:07:19AM -0700, David Wolfskill wrote:
> This is on my "build machine"; running GENERIC/amd64 built yesterday:
>
> FreeBSD freebeast.catwhisker.org 12.0-CURRENT FreeBSD 12.0-CURRENT #353
> r318739M/318739:1200031: Wed May 24 10:00:20 PDT 2017
> r...@freebeast.catwh
On Thu, May 25, 2017 at 05:07:19AM -0700, David Wolfskill wrote:
> ...
> I have attached a copy of the meta file in question.
>
Bah. Really attaching this time.
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
"[T]he president’s improper efforts to influ
On Wed, Jan 18, 2017 at 1:21 PM, Dimitry Andric wrote:
> On 18 Jan 2017, at 14:42, Magnus Ringman wrote:
>>
>> On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky
>> wrote:
> ...
>>> And the error popped out. I'm not observing this error when building a
>>> 12-current kernel from an 11-stable i
On 18 Jan 2017, at 14:42, Magnus Ringman wrote:
>
> On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky
> wrote:
...
>> And the error popped out. I'm not observing this error when building a
>> 12-current kernel from an 11-stable install.
>
>
> Isn't it all bets are off if going to -current f
On 18 Jan 2017, at 14:16, Hans Petter Selasky wrote:
>
> On 01/18/17 14:13, Dimitry Andric wrote:
>> On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote:
>>>
>>> I'm seeing the following build-error trying to build 12-current from
>>> 10-stable:
>>>
>>> xxx/freebsd/sys/crypto/aesni/aesni_ghas
On Wed, Jan 18, 2017 at 2:16 PM, Hans Petter Selasky
wrote:
> On 01/18/17 14:13, Dimitry Andric wrote:
>
>> On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote:
>>
>>>
>>> I'm seeing the following build-error trying to build 12-current from
>>> 10-stable:
>>>
>>> xxx/freebsd/sys/crypto/aesni/aes
On 01/18/17 14:13, Dimitry Andric wrote:
On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote:
I'm seeing the following build-error trying to build 12-current from 10-stable:
xxx/freebsd/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h'
file not found
#include
Missing header
On 18 Jan 2017, at 13:36, Hans Petter Selasky wrote:
>
> I'm seeing the following build-error trying to build 12-current from
> 10-stable:
>
> xxx/freebsd/sys/crypto/aesni/aesni_ghash.c:75:10: fatal error: 'wmmintrin.h'
> file not found
> #include
>
> Missing header exists:
>
> xxx/freebsd/
On Thu, Dec 03, 2015 at 10:34:10PM -0500, Daniel Eischen wrote:
> On Mon, 30 Nov 2015, Konstantin Belousov wrote:
>
> > On Sun, Nov 29, 2015 at 12:27:40PM -0500, Daniel Eischen wrote:
> >> On Sun, 29 Nov 2015, Konstantin Belousov wrote:
> >>
> >>> On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel E
On Mon, 30 Nov 2015, Konstantin Belousov wrote:
On Sun, Nov 29, 2015 at 12:27:40PM -0500, Daniel Eischen wrote:
On Sun, 29 Nov 2015, Konstantin Belousov wrote:
On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel Eischen wrote:
So I found out that sometime in the last year or so, symbol version
On Sun, Nov 29, 2015 at 12:27:40PM -0500, Daniel Eischen wrote:
> On Sun, 29 Nov 2015, Konstantin Belousov wrote:
>
> > On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel Eischen wrote:
> >> On Fri, 27 Nov 2015, Daniel Eischen wrote:
> >>
> >>> Damn, please use deisc...@freebsd.org for replies.
> >>
On Sun, 29 Nov 2015, Konstantin Belousov wrote:
On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel Eischen wrote:
On Fri, 27 Nov 2015, Daniel Eischen wrote:
Damn, please use deisc...@freebsd.org for replies.
On Fri, 27 Nov 2015, Daniel Eischen wrote:
On Fri, 27 Nov 2015, Daniel Eischen wrote
On Sun, Nov 29, 2015 at 01:23:04AM -0500, Daniel Eischen wrote:
> On Fri, 27 Nov 2015, Daniel Eischen wrote:
>
> > Damn, please use deisc...@freebsd.org for replies.
> >
> > On Fri, 27 Nov 2015, Daniel Eischen wrote:
> >
> >> On Fri, 27 Nov 2015, Daniel Eischen wrote:
> >>
> >>> $ uname -a
> >>>
On Fri, 27 Nov 2015, Daniel Eischen wrote:
Damn, please use deisc...@freebsd.org for replies.
On Fri, 27 Nov 2015, Daniel Eischen wrote:
On Fri, 27 Nov 2015, Daniel Eischen wrote:
$ uname -a
FreeBSD vega 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277320: Mon Jan 19
09:02:50 EST 2015
deischen@v
Damn, please use deisc...@freebsd.org for replies.
On Fri, 27 Nov 2015, Daniel Eischen wrote:
On Fri, 27 Nov 2015, Daniel Eischen wrote:
$ uname -a
FreeBSD vega 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277320: Mon Jan 19
09:02:50 EST 2015
deischen@vega:/usr/FreeBSD/svn/obj/usr/FreeBSD/svn/src/
On Fri, 27 Nov 2015, Daniel Eischen wrote:
$ uname -a
FreeBSD vega 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r277320: Mon Jan 19
09:02:50 EST 2015
deischen@vega:/usr/FreeBSD/svn/obj/usr/FreeBSD/svn/src/sys/vega amd64
Upgrading to today's current, 'rm -rf /usr/obj/*; make -j8 buildworld'
fails he
On Mon, 7 Jul 2014 14:55:33 -0500 (CDT)
Dan Mack wrote:
> FYI.
>
> This is from : 268370 during 'make buildkernel' with GENERIC options:
>
> --- buildkernel ---
> --- buildkernel ---
> --
> >>> Kernel build for GENERIC started on Mon J
On 7 липня 2014 р. 22:55:33 GMT+03:00, Dan Mack wrote:
>FYI.
>
>This is from : 268370 during 'make buildkernel' with GENERIC options:
>
>--- buildkernel ---
>--- buildkernel ---
>--
Kernel build for GENERIC started on Mon Jul 7 14:4
On Apr 4, 2014, at 4:13 PM, David Chisnall wrote:
> It turns out that tomorrow happened 12 minutes after this email...
>
> The attached diff lets it build with -Werror for me with FreeBSD clang and
> gcc (with -fblocks and -fno-blocks) and with ports gcc 4.7.3 and doesn't
> clutter the code.
It turns out that tomorrow happened 12 minutes after this email...
The attached diff lets it build with -Werror for me with FreeBSD clang and gcc
(with -fblocks and -fno-blocks) and with ports gcc 4.7.3 and doesn't clutter
the code. Please can you test it with Juniper's gcc?
David
Index: stdl
Hi Marcel,
This error is a warning for me with gcc 4.7.3 when I try. With 4.2.1 in the
tree, it appears to be silenced by something (or possibly we're using the
native blocks code path with gcc and clang doesn't emit that warning in
non-blocks mode). We could pull out the structure definition
We already have PR for this issue :)
http://www.freebsd.org/cgi/query-pr.cgi?pr=187074
On Wed, 5 Mar 2014 03:57:00 +0400
Gleb Smirnoff wrote:
> John-Mark,
>
> On Wed, Feb 26, 2014 at 01:20:17PM -0800, John-Mark Gurney wrote:
> J> Justin Hibbits wrote this message on Wed, Feb 26, 2014 at 11:1
John-Mark,
On Wed, Feb 26, 2014 at 01:20:17PM -0800, John-Mark Gurney wrote:
J> Justin Hibbits wrote this message on Wed, Feb 26, 2014 at 11:12 -0800:
J> > On Wed, Feb 26, 2014 at 10:32 AM, Justin Hibbits
wrote:
J> > > Building on PowerPC I see the following failure:
J> > >
J> > > cc1: warning
On Wed, Feb 26, 2014 at 01:20:17PM -0800, John-Mark Gurney wrote:
J> Justin Hibbits wrote this message on Wed, Feb 26, 2014 at 11:12 -0800:
J> > On Wed, Feb 26, 2014 at 10:32 AM, Justin Hibbits
wrote:
J> > > Building on PowerPC I see the following failure:
J> > >
J> > > cc1: warnings being treate
On Wed, Feb 26, 2014 at 1:20 PM, John-Mark Gurney wrote:
> Justin Hibbits wrote this message on Wed, Feb 26, 2014 at 11:12 -0800:
>> On Wed, Feb 26, 2014 at 10:32 AM, Justin Hibbits
>> wrote:
>> > Building on PowerPC I see the following failure:
>> >
>> > cc1: warnings being treated as errors
>>
Justin Hibbits wrote this message on Wed, Feb 26, 2014 at 11:12 -0800:
> On Wed, Feb 26, 2014 at 10:32 AM, Justin Hibbits
> wrote:
> > Building on PowerPC I see the following failure:
> >
> > cc1: warnings being treated as errors
> >
> > /home/chmeee/freebsd/head/sys/modules/pf/../../netpfil/pf/p
On Wed, Feb 26, 2014 at 10:32 AM, Justin Hibbits wrote:
> Building on PowerPC I see the following failure:
>
> cc1: warnings being treated as errors
>
> /home/chmeee/freebsd/head/sys/modules/pf/../../netpfil/pf/pf_ioctl.c:
> In function 'pfioctl':
> /home/chmeee/freebsd/head/sys/modules/pf/../../n
On Tue, Sep 18, 2012 at 3:17 PM, Kim Culhan wrote:
> Ah right sorry about that, take 2:
>
> clang -pg -O2 -pipe -DTERMIOS -DANSI_SOURCE
> -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl -I/
> usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto
> -I/usr/obj/usr/src/secure/lib/libc
On Tue, Sep 18, 2012 at 3:05 PM, Garrett Cooper wrote:
> On Tue, Sep 18, 2012 at 11:52 AM, Kim Culhan wrote:
>> Seeing this on a clean checkout of r240669
>
> ...
>
>> 1 error
>> *** [everything] Error code 2
>> 1 error
>> *** [buildworld] Error code 2
>> 1 error
>
> This isn't helpful. Eithe
On Tue, Sep 18, 2012 at 11:52 AM, Kim Culhan wrote:
> Seeing this on a clean checkout of r240669
...
> 1 error
> *** [everything] Error code 2
> 1 error
> *** [buildworld] Error code 2
> 1 error
This isn't helpful. Either compile with -j1 or capture everything
to a log and look for " Error
On 26 June 2011 19:55, Dimitry Andric wrote:
> On 2011-06-26 20:43, Chris Rees wrote:
> ...
>>
>> cd /usr/cursrc/src
>> make KERNCONF=CERBERUS DESTDIR=/mnt world kernel
>
> ...
>>
>>
>> /usr/obj/cursrc/src/usr.bin/clang/clang/../../../lib/clang/libllvmcodegen/libllvmcodegen.a:
>> could not read sy
On 2011-06-26 20:43, Chris Rees wrote:
...
cd /usr/cursrc/src
make KERNCONF=CERBERUS DESTDIR=/mnt world kernel
...
/usr/obj/cursrc/src/usr.bin/clang/clang/../../../lib/clang/libllvmcodegen/libllvmcodegen.a:
could not read symbols: File format not recognized
...
Any ideas please???
The file
In the last episode (Dec 05), Marcel Moolenaar said:
> Gang,
>
> Anyone seen the following build failure?
>
> cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
>-g -nostdinc -I- -I
On Tuesday 10 September 2002 10:11 am, Kris Kennaway wrote:
> On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote:
> > I was trying to update linux_base and got the following build failure:
>
> Known problem; see the list archives for a patch.
>
> Kris
Already applied those patches, sti
On Tue, Sep 10, 2002 at 08:21:31AM -0800, Beech Rintoul wrote:
> I was trying to update linux_base and got the following build failure:
Known problem; see the list archives for a patch.
Kris
msg42849/pgp0.pgp
Description: PGP signature
On Fri, 22 Feb 2002, John Hay wrote:
> > >
> > > >Date: Fri, 22 Feb 2002 08:09:28 -0900
> > > >
> > > >Last night's build for -current failed with the following:
> > >
> > > I got -CURRENT built today without problem. Recent CVSup history:
> > >
> > (snip history)
> > >
> > > Might try updatin
the probkem is that phk didn't test a buildworld before making the
following change to proc.h:
revision 1.204
date: 2002/02/22 13:32:01; author: phk; state: Exp; lines: +1 -1
Convert p->p_runtime and PCPU(switchtime) to bintime format.
> >
> > >Date: Fri, 22 Feb 2002 08:09:28 -0900
> > >
> > >Last night's build for -current failed with the following:
> >
> > I got -CURRENT built today without problem. Recent CVSup history:
> >
> (snip history)
> >
> > Might try updating again
>
> Already did that. The update was about 15
On Friday 22 February 2002 08:14 am, David Wolfskill wrote:
> From: Beech Rintoul <[EMAIL PROTECTED]>
>
> >Date: Fri, 22 Feb 2002 08:09:28 -0900
> >
> >Last night's build for -current failed with the following:
>
> I got -CURRENT built today without problem. Recent CVSup history:
>
(snip history)
>From: Beech Rintoul <[EMAIL PROTECTED]>
>Date: Fri, 22 Feb 2002 08:09:28 -0900
>Last night's build for -current failed with the following:
I got -CURRENT built today without problem. Recent CVSup history:
freebeast(5.0-C)[1] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org
age-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> [EMAIL PROTECTED]
> Sent: Monday, 18 December 2000 11:02
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Build failure in -current
>
>
> "Chris Knight" &
Howdy,
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Jordan Hubbard
> Sent: Monday, 18 December 2000 10:54
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Build failure in -current
>
>
"Chris Knight" <[EMAIL PROTECTED]> writes:
> I've been noticing this on my daily builds for the last five days. I've just
> tried the attached patch, which works for me.
But it does only solve the problem for `make release'. Please upgrade
so that you have sys/ufs/ffs/ffs_softdep_stub.c 1.15 whi
> I've been noticing this on my daily builds for the last five days. I've just
> tried the attached patch, which works for me.
Well, that's a fix, just not the right one. :) There should be no
"dangling references" to soft updates if SOFTUPDATES is not defined.
- Jordan
To Unsubscribe: send m
Howdy,
I've been noticing this on my daily builds for the last five days. I've just
tried the attached patch, which works for me.
Regards,
Chris Knight
Systems Administrator
AIMS Independent Computer Professionals
Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795
Web: http://www.a
On 15-Mar-00 Kent Hauser wrote:
>
> make world fails:
>
> cvsup from 3/15/00 14:00 GMT or so.
>
>
>
> ===> sys/boot/i386/libi386
> cc -O -pipe -I/usr/src/sys/boot/i386/libi386/../../common
>-I/usr/src/sys/boot/i386/libi386/../btx/lib
> -I/usr/src/sys/boot/i386/libi386/../../.. -I. -DCOMPORT
Somebody sent a message to -questions today about trying "make world"
under 3.1-STABLE, but the make died in modules/vinum. Unfortunately,
I accidentally deleted the message, so I can't remember who it was.
I've checked this out, and I think I can safely say:
1. There's nothing wrong with the bu
84 matches
Mail list logo
