Date: Sat, 22 Apr 2000 21:57:05 GMT From: attila! <attila@hun.org> To: freebsd-current@freebsd.org Subject: __func__ not declared for kernel build (5.0-CURRENT) Message-ID: <200004222157.VAA55016@hun.org>
next in thread | raw e-mail | index | archive | help
...trying to upgrade from 4.0-CURRENT (last update 21 Jul 99) to 5.0-CURRENT (22 Apr at 0419 UCT) using cvsup over 56K. I know, I know, I fell behind, but it was doing its thing --ran for 272 days without even restarting X although the aux generator fired up during a couple power failures before the backup batteries gave up the ghost. 272 days: that's reliability! -- '...only shut down to change the hardware or software'. In my notes, sometime in the fall, the signal list was changed to accommodate more than 32 signals; and, if I remember correctly, it was necessary to generate the kernel _before_ doing 'build world', etc. I 'glimpse'd for the instructions in 'current', 'commit', and the manual, but came up empty handed. '__func__ is not found for either the 'GENERIC' or 'hun' target. ../../i386/i386/in_cksum.c: In function `in_cksum': ../../i386/i386/in_cksum.c:239: `__func__' undeclared (first use in this function) ../../i386/i386/in_cksum.c:239: (Each undeclared identifier is reported only once ../../i386/i386/in_cksum.c:239: for each function it appears in.) ../../i386/i386/in_cksum.c: In function `in_cksum_skip': ../../i386/i386/in_cksum.c:427: `__func__' undeclared (first use in this function) *** Error code 1 I can not find __func__ declared in any '.[chsS]' files in 5.0-CURRENT /usr/src/sys, /usr/src/include files, or any 4.0-CURRENT include files. I presume it is generated on the fly somewhere? What did I miss during RTFM and RTFS (source)? Is my procedure correct by compiling the kernel before 'build world', etc.? I suppose I could (but I would rather not) have 'cvsup' retreat to a "safe" date after the signal change, build the kernel, 'make world', and then upgrade to 5.0-CURRENT... if so, what date? -- Caveat: No Microsoft programs or processes were used in the creation or distribution of this message. If you are using a Microsoft program to view this message, please be advised I am not responsible for any harm you may suffer as a result. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200004222157.VAA55016>