Re: problem with buildworld

2018-02-05 Thread Dimitry Andric 
On 5 Feb 2018, at 18:48, Filippo Moretti  wrote:
> 
> Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr 
> but I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: 
> /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug:
>  Bad file descriptorrm: 
> /usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not 
> emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not 
> emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: 
> /usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: 
> /usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: 
> Directory not emptyrm: /usr/obj/usr: Directory not empty[root@sting 
> /usr/src]# Any help would be appreciatedsincerelyFilippo

Try rebooting into single user mode, and running "fsck -f -y" until all
your filesystems are completely clean.

Also, please switch to a mail client that does not completely mangle
your messages.

-Dimitry



signature.asc
Description: Message signed with OpenPGP

problem with buildworld

2018-02-05 Thread Filippo Moretti 
Buildworld failed with libpam/modules error.I tried to delete /usr/obj/usr but 
I get the following error[root@sting /usr/src]# rm -rf /usr/obj/usrrm: 
/usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess/pam_opieaccess.so.6.debug:
 Bad file descriptorrm: 
/usr/obj/usr/src/i386.i386/lib/libpam/modules/pam_opieaccess: Directory not 
emptyrm: /usr/obj/usr/src/i386.i386/lib/libpam/modules: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386/lib/libpam: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386/lib: Directory not emptyrm: 
/usr/obj/usr/src/i386.i386: Directory not emptyrm: /usr/obj/usr/src: Directory 
not emptyrm: /usr/obj/usr: Directory not empty[root@sting /usr/src]# Any help 
would be appreciatedsincerelyFilippo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Problem with buildworld (Stop in /usr/src/lib/csu/i386-elf.)

2010-08-07 Thread Николай 
Hi  
I want to update my FreeBSD system from 7.2-RELEASE-p4 to 8.1-RELEASE  
When I try to run make buildworld, process stopped with error.  
  
=  
=== lib/csu/i386-elf (obj,depend,all,install)  
rm -f .depend  
mkdep -f .depend -a    -I/usr/src/lib/csu/i386-elf/../common 
-I/usr/src/lib/csu/i386-elf/../../libc/include /usr/src/lib/csu/i386-elf/crti.S 
/usr/src/lib/csu/i386-elf/crtn.S  
cc -O2 -pipe  -I/usr/src/lib/csu/i386-elf/../common  
-I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99  -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings 
-Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wno-pointer-sign -c 
/usr/src/lib/csu/i386-elf/crti.S  
cc -O2 -pipe  -I/usr/src/lib/csu/i386-elf/../common  
-I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99  -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings 
-Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wno-pointer-sign -c 
/usr/src/lib/csu/i386-elf/crtn.S  
cc -O2 -pipe  -I/usr/src/lib/csu/i386-elf/../common  
-I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99  -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings 
-Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wno-pointer-sign -DGCRT -c -o gcrt1_c.o 
/usr/src/lib/csu/i386-elf/crt1_c.c  
cc -O2 -pipe  -I/usr/src/lib/csu/i386-elf/../common  
-I/usr/src/lib/csu/i386-elf/../../libc/include -std=gnu99  -Wsystem-headers 
-Werror -Wall -Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes 
-Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings 
-Wswitch -Wshadow -Wcast-align -Wunused-parameter -Wchar-subscripts -Winline 
-Wnested-externs -Wredundant-decls -Wno-pointer-sign -c 
/usr/src/lib/csu/i386-elf/crt1_s.S  
ld -Wl,--rpath -Wl,LIBDIR -o gcrt1.o -r crt1_s.o gcrt1_c.o  
ld: unrecognized option '-Wl,--rpath'  
ld: use the --help option for usage information  
*** Error code 1  
  
Stop in /usr/src/lib/csu/i386-elf.  
*** Error code 1  
  
Stop in /usr/src.  
*** Error code 1  
  
Stop in /usr/src.  
*** Error code 1  
  
Stop in /usr/src.  
*** Error code 1  
  
Stop in /usr/src.  
=  
  
/etc/make.conf is clean  
  
Thanks for the help!  
___
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

Re: Problem with buildworld with CLANG

2010-06-24 Thread Tom Evans 
On Wed, Jun 23, 2010 at 4:52 PM, Cristiano Deana
cristiano.de...@gmail.com wrote:
 On Wed, Jun 23, 2010 at 3:15 PM, Tom Evans tevans...@googlemail.com wrote:

 Top of the '[TESTING] Clang..' email:

 hi,

 ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to 
 import
 into HEAD in roughly a week. We would like the initial import to be as 
 painless
 as possible and therefore we ask you to test ClangBSD to assure that the 
 revision
 we are importing does not have some really embarassing bugs.

 How to do it (on i386 and amd64):

 1) svn co http://svn.freebsd.org/base/projects/clangbsd src

 i already did it and it worked, two weeks ago.
 now i wanted to try with clan in system

 2) echo NO_WERROR=  /etc/src.conf ; echo WERROR=  /etc/src.conf

 So uncomment your src.conf lines that are incompatible.

 forgot to tell before. i tried with and without those lines.


The error in your first email was clearly a warning being promoted to
an error, so either you had a different error on your build with
NO_WERROR/WERROR, or your NO_WERROR/WERROR settings were not being
respected. Please retry with NO_WERROR/WERROR set in /etc/src.conf,
and show the resulting error.

Cheers

Tom
___
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

Re: Problem with buildworld with CLANG

2010-06-24 Thread Cristiano Deana 
On Thu, Jun 24, 2010 at 11:24 AM, Tom Evans tevans...@googlemail.com wrote:

 The error in your first email was clearly a warning being promoted to
 an error, so either you had a different error on your build with
 NO_WERROR/WERROR, or your NO_WERROR/WERROR settings were not being
 respected. Please retry with NO_WERROR/WERROR set in /etc/src.conf,
 and show the resulting error.

Last lines:

/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:2:
error: unsupported inline asm: input with type 'unsigned long'
matching output with type
  'unsigned int'
R1(D,A,B,C,X( 4), 5,0x5A827999L);
^~~~
In file included from
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:60:
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_locl.h:108:4:
note: instantiated from:
a=ROTATE(a,s); };\
  ^
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:2:
note: instantiated from:
R1(D,A,B,C,X( 4), 5,0x5A827999L);
^  ~
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:5:
note: instantiated from:
R1(D,A,B,C,X( 4), 5,0x5A827999L);
   ^
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:2:
error: unsupported inline asm: input with type 'unsigned long'
matching output with type
  'unsigned int'
R1(C,D,A,B,X( 8), 9,0x5A827999L);
^~~~
In file included from
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:60:
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_locl.h:108:4:
note: instantiated from:
a=ROTATE(a,s); };\
  ^
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:2:
note: instantiated from:
R1(C,D,A,B,X( 8), 9,0x5A827999L);
^  ~
/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:5:
note: instantiated from:
R1(C,D,A,B,X( 8), 9,0x5A827999L);
   ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
4 warnings and 20 errors generated.
*** Error code 1

Stop in /usr/src/secure/lib/libcrypto.
*** Error code 1


-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
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

Re: Problem with buildworld with CLANG

2010-06-24 Thread Dimitry Andric 
On 2010-06-24 15:33, Cristiano Deana wrote:
 Last lines:
 
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:2:
 error: unsupported inline asm: input with type 'unsigned long'
 matching output with type
   'unsigned int'
 R1(D,A,B,C,X( 4), 5,0x5A827999L);
 ^~~~

Don't try building head with clang, it is not possible yet.  Use
clangbsd instead. :)
___
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

Re: Problem with buildworld with CLANG

2010-06-24 Thread Tom Evans 
On Thu, Jun 24, 2010 at 2:33 PM, Cristiano Deana
cristiano.de...@gmail.com wrote:
 On Thu, Jun 24, 2010 at 11:24 AM, Tom Evans tevans...@googlemail.com wrote:

 The error in your first email was clearly a warning being promoted to
 an error, so either you had a different error on your build with
 NO_WERROR/WERROR, or your NO_WERROR/WERROR settings were not being
 respected. Please retry with NO_WERROR/WERROR set in /etc/src.conf,
 and show the resulting error.

 Last lines:

 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:2:
 error: unsupported inline asm: input with type 'unsigned long'
 matching output with type
      'unsigned int'
        R1(D,A,B,C,X( 4), 5,0x5A827999L);
        ^~~~
 In file included from
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:60:
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_locl.h:108:4:
 note: instantiated from:
        a=ROTATE(a,s); };\
          ^
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:2:
 note: instantiated from:
        R1(D,A,B,C,X( 4), 5,0x5A827999L);
        ^  ~
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:135:5:
 note: instantiated from:
        R1(D,A,B,C,X( 4), 5,0x5A827999L);
           ^
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:2:
 error: unsupported inline asm: input with type 'unsigned long'
 matching output with type
      'unsigned int'
        R1(C,D,A,B,X( 8), 9,0x5A827999L);
        ^~~~
 In file included from
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:60:
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_locl.h:108:4:
 note: instantiated from:
        a=ROTATE(a,s); };\
          ^
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:2:
 note: instantiated from:
        R1(C,D,A,B,X( 8), 9,0x5A827999L);
        ^  ~
 /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/md4/md4_dgst.c:136:5:
 note: instantiated from:
        R1(C,D,A,B,X( 8), 9,0x5A827999L);
           ^
 fatal error: too many errors emitted, stopping now [-ferror-limit=]
 4 warnings and 20 errors generated.
 *** Error code 1

 Stop in /usr/src/secure/lib/libcrypto.
 *** Error code 1



So thats a completely different error than you had been reporting. I'm
afraid I don't know enough about clang to help with that one.

Cheers

Tom
___
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

Problem with buildworld with CLANG

2010-06-23 Thread Cristiano Deana 
# uname -a
FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
CEST 2010 r...@test:/usr/obj/usr/src/sys/GENERIC  amd64

# cat /etc/src.conf
#NO_WERROR=
#WERROR=
CC= clang
CXX=clang++

sources from this morning, i got this error:

clang -O2 -pipe  -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS
-D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa
-DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv
-D_ACL_PRIVATE -DPOSIX_MISTAKE
-I/usr/src/lib/libc/../../contrib/tzcode/stdtime
-I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES
-DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING
-DSYMBOL_VERSIONING -std=gnu99  -Wsystem-headers -Werror -Wall
-Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
/usr/src/lib/libc/sys/stack_protector.c
/usr/src/lib/libc/sys/stack_protector.c:88:19: error: format string is
not a string literal (potentially insecure) [-Wformat-security]
syslog(LOG_CRIT, msg);
 ^~~
1 error generated.
*** Error code 1

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
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

Re: Problem with buildworld with CLANG

2010-06-23 Thread René Ladan 
2010/6/23 Cristiano Deana cristiano.de...@gmail.com:
 # uname -a
 FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
 CEST 2010     r...@test:/usr/obj/usr/src/sys/GENERIC  amd64

 # cat /etc/src.conf
 #NO_WERROR=
 #WERROR=
 CC=     clang
 CXX=    clang++

 sources from this morning, i got this error:

[.. error ..]

If you are using HEAD sources, then an error-free build with clang is
not guaranteed.
There is a separate branch of HEAD, clangbsd, which can be built (almost)
completely with clang, see http://wiki.freebsd.org/BuildingFreeBSDWithClang

Rene
___
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

Re: Problem with buildworld with CLANG

2010-06-23 Thread Tom Evans 
On Wed, Jun 23, 2010 at 1:38 PM, Cristiano Deana
cristiano.de...@gmail.com wrote:
 # uname -a
 FreeBSD test 9.0-CURRENT FreeBSD 9.0-CURRENT #3: Tue Jun 22 16:04:38
 CEST 2010     r...@test:/usr/obj/usr/src/sys/GENERIC  amd64

 # cat /etc/src.conf
 #NO_WERROR=
 #WERROR=
 CC=     clang
 CXX=    clang++

 sources from this morning, i got this error:

 clang -O2 -pipe  -I/usr/src/lib/libc/include
 -I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS
 -D__DBINTERFACE_PRIVATE -I/usr/src/lib/libc/../../contrib/gdtoa
 -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv
 -D_ACL_PRIVATE -DPOSIX_MISTAKE
 -I/usr/src/lib/libc/../../contrib/tzcode/stdtime
 -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -DBROKEN_DES
 -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING
 -DSYMBOL_VERSIONING -std=gnu99  -Wsystem-headers -Werror -Wall
 -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c
 /usr/src/lib/libc/sys/stack_protector.c
 /usr/src/lib/libc/sys/stack_protector.c:88:19: error: format string is
 not a string literal (potentially insecure) [-Wformat-security]
        syslog(LOG_CRIT, msg);
                         ^~~
 1 error generated.
 *** Error code 1


Top of the '[TESTING] Clang..' email:

 hi,

 ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to 
 import
 into HEAD in roughly a week. We would like the initial import to be as 
 painless
 as possible and therefore we ask you to test ClangBSD to assure that the 
 revision
 we are importing does not have some really embarassing bugs.

 How to do it (on i386 and amd64):

 0) install fresh devel/llvm-devel port

 1) svn co http://svn.freebsd.org/base/projects/clangbsd src

 2) echo NO_WERROR=  /etc/src.conf ; echo WERROR=  /etc/src.conf

 3) cd src  make buildworld

So uncomment your src.conf lines that are incompatible.

Cheers

Tom
___
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

Re: Problem with buildworld with CLANG

2010-06-23 Thread Cristiano Deana 
On Wed, Jun 23, 2010 at 3:15 PM, Tom Evans tevans...@googlemail.com wrote:

 Top of the '[TESTING] Clang..' email:

 hi,

 ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to 
 import
 into HEAD in roughly a week. We would like the initial import to be as 
 painless
 as possible and therefore we ask you to test ClangBSD to assure that the 
 revision
 we are importing does not have some really embarassing bugs.

 How to do it (on i386 and amd64):

 1) svn co http://svn.freebsd.org/base/projects/clangbsd src

i already did it and it worked, two weeks ago.
now i wanted to try with clan in system

 2) echo NO_WERROR=  /etc/src.conf ; echo WERROR=  /etc/src.conf

 So uncomment your src.conf lines that are incompatible.

forgot to tell before. i tried with and without those lines.

-- 
Cris, member of G.U.F.I
Italian FreeBSD User Group
http://www.gufi.org/
___
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

Problem with buildworld: what is major really supposed to be?

2002-02-23 Thread David Wolfskill 

Trying to make buildworld for today's -CURRENT, I get:

 stage 4: building libraries
--
...
=== doc
cc -fpic -DPIC -O -pipe  -DLIBC_SCCS -I/usr/src/lib/libkvm  -c 
/usr/src/lib/libkvm/kvm_file.c -o kvm_file.So
In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40,
 from /usr/src/lib/libkvm/kvm_file.c:54:
/usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `('
*** Error code 1


After enough tinkering with copies of the files to demonstrate to
my satisfaction that my C skills are pretty rusty, I noticed that:

* The lines in systm.h look like (starting at line 301):

/*
 * Common `dev_t' stuff are declared here to avoid #include poisoning
 */

int major(dev_t x);
int minor(dev_t x);
dev_t makedev(int x, int y);
udev_t dev2udev(dev_t x);
dev_t udev2dev(udev_t x, int b);
int uminor(udev_t dev);
int umajor(udev_t dev);
udev_t makeudev(int x, int y);


  so it looks as if we're declaring major as a function returning int.

* But sys/sys/file.h, starting at line 49 reads:

#ifdef _KERNEL
#include sys/types.h
#include sys/queue.h
#include sys/_lock.h
#include sys/_mutex.h

  which is OK, except that sys/sys/types.h, starting at line 113 reads:

/*
 * minor() gives a cookie instead of an index since we don't want to
 * change the meanings of bits 0-15 or waste time and space shifting
 * bits 16-31 for devices that don't use them.
 */
#define major(x)((int)(((u_int)(x)  8)0xff)) /* major number */
#define minor(x)((int)((x)0x00ff)) /* minor number */
#define makedev(x,y)((dev_t)(((x)  8) | (y))) /* create dev_t */


  and this appears to be a bit of a problem, because by the time the C
  compiler gets to the int major(dev_t x); line in sys/sys/systm.h,
  major has been replaced, so the line looks like:

int ((int)(((u_int)( dev_t x )  8)0xff)) ;

  which is pretty non-ideal, any way you look at it.


In case it's of interest/value, recent CVSup history is:
freebeast(5.0-C)[44] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002
CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002
CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002
CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002
CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002
freebeast(5.0-C)[45] 


So:  how should this be resolved?  Or am I just confused (again)?


Thanks,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Problem with buildworld: what is major really supposed to be?

2002-02-23 Thread Poul-Henning Kamp 


Yeah, I'm chasing that one right now.

I'm not yet quite sure which commit has broken this, nor what the right
fix is...

Poul-Henning

In message [EMAIL PROTECTED], David Wolfskill w
rites:
Trying to make buildworld for today's -CURRENT, I get:

 stage 4: building libraries
--
...
=== doc
cc -fpic -DPIC -O -pipe  -DLIBC_SCCS -I/usr/src/lib/libkvm  -c 
/usr/src/lib/libkvm/kvm_file.c -o kvm_file.So
In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40,
 from /usr/src/lib/libkvm/kvm_file.c:54:
/usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `('
*** Error code 1


After enough tinkering with copies of the files to demonstrate to
my satisfaction that my C skills are pretty rusty, I noticed that:

* The lines in systm.h look like (starting at line 301):

/*
 * Common `dev_t' stuff are declared here to avoid #include poisoning
 */

int major(dev_t x);
int minor(dev_t x);
dev_t makedev(int x, int y);
udev_t dev2udev(dev_t x);
dev_t udev2dev(udev_t x, int b);
int uminor(udev_t dev);
int umajor(udev_t dev);
udev_t makeudev(int x, int y);


  so it looks as if we're declaring major as a function returning int.

* But sys/sys/file.h, starting at line 49 reads:

#ifdef _KERNEL
#include sys/types.h
#include sys/queue.h
#include sys/_lock.h
#include sys/_mutex.h

  which is OK, except that sys/sys/types.h, starting at line 113 reads:

/*
 * minor() gives a cookie instead of an index since we don't want to
 * change the meanings of bits 0-15 or waste time and space shifting
 * bits 16-31 for devices that don't use them.
 */
#define major(x)((int)(((u_int)(x)  8)0xff)) /* major number */
#define minor(x)((int)((x)0x00ff)) /* minor number */
#define makedev(x,y)((dev_t)(((x)  8) | (y))) /* create dev_t */


  and this appears to be a bit of a problem, because by the time the C
  compiler gets to the int major(dev_t x); line in sys/sys/systm.h,
  major has been replaced, so the line looks like:

int ((int)(((u_int)( dev_t x )  8)0xff)) ;

  which is pretty non-ideal, any way you look at it.


In case it's of interest/value, recent CVSup history is:
freebeast(5.0-C)[44] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002
CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002
CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002
CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002
CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002
freebeast(5.0-C)[45] 


So:  how should this be resolved?  Or am I just confused (again)?


Thanks,
david
-- 
David H. Wolfskill [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Problem with buildworld: what is major really supposed to be?

2002-02-23 Thread Poul-Henning Kamp 


Ok, found it:

This is the culprit:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/sys/file.h.diff?r1=1.39r2=1.40


In message [EMAIL PROTECTED], Poul-Henning Kamp writes:

Yeah, I'm chasing that one right now.

I'm not yet quite sure which commit has broken this, nor what the right
fix is...

Poul-Henning

In message [EMAIL PROTECTED], David Wolfskill w
rites:
Trying to make buildworld for today's -CURRENT, I get:

 stage 4: building libraries
--
...
=== doc
cc -fpic -DPIC -O -pipe  -DLIBC_SCCS -I/usr/src/lib/libkvm  -c 
/usr/src/lib/libkvm/kvm_file.c -o kvm_file.So
In file included from /usr/obj/usr/src/i386/usr/include/sys/file.h:40,
 from /usr/src/lib/libkvm/kvm_file.c:54:
/usr/obj/usr/src/i386/usr/include/sys/systm.h:305: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:306: syntax error before `int'
/usr/obj/usr/src/i386/usr/include/sys/systm.h:307: syntax error before `('
*** Error code 1


After enough tinkering with copies of the files to demonstrate to
my satisfaction that my C skills are pretty rusty, I noticed that:

* The lines in systm.h look like (starting at line 301):

/*
 * Common `dev_t' stuff are declared here to avoid #include poisoning
 */

int major(dev_t x);
int minor(dev_t x);
dev_t makedev(int x, int y);
udev_t dev2udev(dev_t x);
dev_t udev2dev(udev_t x, int b);
int uminor(udev_t dev);
int umajor(udev_t dev);
udev_t makeudev(int x, int y);


  so it looks as if we're declaring major as a function returning int.

* But sys/sys/file.h, starting at line 49 reads:

#ifdef _KERNEL
#include sys/types.h
#include sys/queue.h
#include sys/_lock.h
#include sys/_mutex.h

  which is OK, except that sys/sys/types.h, starting at line 113 reads:

/*
 * minor() gives a cookie instead of an index since we don't want to
 * change the meanings of bits 0-15 or waste time and space shifting
 * bits 16-31 for devices that don't use them.
 */
#define major(x)((int)(((u_int)(x)  8)0xff)) /* major number */
#define minor(x)((int)((x)0x00ff)) /* minor number */
#define makedev(x,y)((dev_t)(((x)  8) | (y))) /* create dev_t */


  and this appears to be a bit of a problem, because by the time the C
  compiler gets to the int major(dev_t x); line in sys/sys/systm.h,
  major has been replaced, so the line looks like:

int ((int)(((u_int)( dev_t x )  8)0xff)) ;

  which is pretty non-ideal, any way you look at it.


In case it's of interest/value, recent CVSup history is:
freebeast(5.0-C)[44] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Tue Feb 19 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Feb 19 03:53:36 PST 2002
CVSup begin from cvsup14.freebsd.org at Wed Feb 20 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Wed Feb 20 04:00:08 PST 2002
CVSup begin from cvsup14.freebsd.org at Thu Feb 21 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Thu Feb 21 03:53:29 PST 2002
CVSup begin from cvsup14.freebsd.org at Fri Feb 22 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Fri Feb 22 03:54:26 PST 2002
CVSup begin from cvsup14.freebsd.org at Sat Feb 23 04:35:13 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Feb 23 04:42:37 PST 2002
freebeast(5.0-C)[45] 


So:  how should this be resolved?  Or am I just confused (again)?


Thanks,
david
-- 
David H. Wolfskill[EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message


-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message