On Saturday, January 27, 2018 06:54:03 PM Per Gunnarsson wrote:
> I am back with new build errors. If I post too frequently, please inform me.
These all look like you have stale sources in your tree somehow (e.g.
sys/compat/freebsd/freebsd32_misc.c doesn't seem to match
sys/compat/freebsd/freebsd3
[ Charset UTF-8 unsupported, converting... ]
> Hello!
>
> I am trying to build the kernel with revision 328463.
>
> It halts with this error:
>
> /usr/src/sys/cam/scsi/scsi_da.c:1514:9: error: 'CAM_PERIPH_PRINT' macro
> redefined [-Werror,-Wmacro-redefined]
> #define CAM_PERIPH_PRINT(p, msg, arg
I am back with new build errors. If I post too frequently, please inform me.
/usr/src/sys/compat/freebsd32/freebsd32_misc.c:122:1: error:
static_assert failed "compile-time assertion failed"
CTASSERT(sizeof(struct kevent32) == 20);
^ ~
/usr/src/sys/sys/systm.h:10
Hello!
I am trying to build the kernel with revision 328463.
It halts with this error:
/usr/src/sys/cam/scsi/scsi_da.c:1514:9: error: 'CAM_PERIPH_PRINT' macro
redefined [-Werror,-Wmacro-redefined]
#define CAM_PERIPH_PRINT(p, msg, args...)
^
/usr/src/sys/cam/cam_periph.h:263:9: note: prev
On Thu, May 02, 2013 at 04:12:36PM +0200, Davide Italiano wrote:
> On Thu, May 2, 2013 at 3:42 PM, Andrey Chernov wrote:
> > On 02.05.2013 14:06, Davide Italiano wrote:
> >>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning:
> >>> 'map' may be used uninitialized in this funct
On Thu, May 2, 2013 at 3:42 PM, Andrey Chernov wrote:
> On 02.05.2013 14:06, Davide Italiano wrote:
>>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning:
>>> 'map' may be used uninitialized in this function
>>> *** [hwpmc_core.o] Error code 1
>
>> You can find a patch attache
On 02.05.2013 14:06, Davide Italiano wrote:
>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning: 'map'
>> may be used uninitialized in this function
>> *** [hwpmc_core.o] Error code 1
> You can find a patch attached at the end of this mail that should fix
> the problem.
Than
On Thu, May 2, 2013 at 3:10 PM, Dimitry Andric wrote:
> On 2013-05-02 12:06, Davide Italiano wrote:
>>
>> On Thu, May 2, 2013 at 8:43 AM, Andrey Chernov wrote:
>>>
>>> cc1: warnings being treated as errors
>>> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c: In function
>>> 'iap_allocate_
On 2013-05-02 12:06, Davide Italiano wrote:
On Thu, May 2, 2013 at 8:43 AM, Andrey Chernov wrote:
cc1: warnings being treated as errors
/usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c: In function
'iap_allocate_pmc':
/usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning
On Thu, May 2, 2013 at 8:43 AM, Andrey Chernov wrote:
> cc1: warnings being treated as errors
> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c: In function
> 'iap_allocate_pmc':
> /usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning: 'map'
> may be used uninitialized in
cc1: warnings being treated as errors
/usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c: In function
'iap_allocate_pmc':
/usr/src/sys/modules/hwpmc/../../dev/hwpmc/hwpmc_core.c:1935: warning: 'map'
may be used uninitialized in this function
*** [hwpmc_core.o] Error code 1
--
bitcoin:13fGi
Beech Rintoul <[EMAIL PROTECTED]> writes:
> Today's -current build fails on my box with the following:
I think it's safe to say, as a general rule, that whenever you hit a
build error (as opposed to a run-time bug) you should wait a couple of
hours, re-cvsup, rebuild, and check that the problem i
On 26-Oct-01 Beech Rintoul wrote:
> Today's -current build fails on my box with the following:
>
> linking kernel
> vm_fault.o: In function `vm_fault1':
> vm_fault.o(.text+0x941): undefined reference to
> `vm_object_set_writeable_dirty'
> vm_page.o In function `vm_page_insert':
> vm_page.o(.tex
Today's -current build fails on my box with the following:
linking kernel
vm_fault.o: In function `vm_fault1':
vm_fault.o(.text+0x941): undefined reference to
`vm_object_set_writeable_dirty'
vm_page.o In function `vm_page_insert':
vm_page.o(.text+0x4c2): undefined reference to `vm_object_set_wri
After the following commit, my kernel fail to build with following errors:
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-g -nostdinc -I- -I. -I../.. -I../../../include
-I../../contrib
...
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions
-ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include
opt_global.h -elf -mpreferred-stack-boundary=2 ../../i4b/driver/i4b_c
On Sat, 27 May 2000, Jake Burkholder wrote:
> > I got following kernel build error.
> > When I run 'make includes', the error has gone away.
`make includes' tends to cause errors like this. It updates /usr/include
to match the sources. This may make /usr/include
> Hi all,
>
> I got following kernel build error.
> When I run 'make includes', the error has gone away.
>
> Why does kernel build process depend on installed system files,
> such as /usr/include?
It shouldn't.
This seems to be primarily aic7xxx, although j
Hi all,
I got following kernel build error.
When I run 'make includes', the error has gone away.
Why does kernel build process depend on installed system files,
such as /usr/include?
Thank you,
Haro
---
jkpc
19 matches
Mail list logo
