Re: Kernel Compile issue
Also I wanted to note how I got to this problem: [root@ /usr/src]# make buildkernel config=GENERIC 2 error.log [root@ /usr/src]# uname -a FreeBSD 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 [root@ /usr/src]# I also wanted to mention that I tried this with the LINT configuration and had the same result. On Mon, Mar 2, 2009 at 12:21 AM, Paige Thompson erra...@devel.ws wrote: [root@ /usr/src]# head error.log /usr/src/sys/i386/i386/genassym.c:35:23: error: sys/cdefs.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:36: error: expected declaration specifiers or '...' before string constant /usr/src/sys/i386/i386/genassym.c:36: warning: data definition has no type or storage class /usr/src/sys/i386/i386/genassym.c:36: warning: type defaults to 'int' in declaration of '__FBSDID' /usr/src/sys/i386/i386/genassym.c:36: warning: function declaration isn't a prototype /usr/src/sys/i386/i386/genassym.c:42:23: error: sys/param.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:43:23: error: sys/systm.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:44:23: error: sys/assym.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:45:21: error: sys/bio.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:46:21: error: sys/buf.h: No such file or directory [root@ /usr/src]# [root@ /usr/src]# cat sys/i386/i386/genassym.c | grep cdefs.h #include sys/cdefs.h [root@ /usr/src]# ls -lah /usr/include/sys/cdefs.h -r--r--r-- 1 root wheel18K Feb 24 2008 /usr/include/sys/cdefs.h [root@ /usr/src]# wat wat wat Not sure what I'm missing here o.O ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Kernel Compile issue
[root@ /usr/src]# head error.log /usr/src/sys/i386/i386/genassym.c:35:23: error: sys/cdefs.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:36: error: expected declaration specifiers or '...' before string constant /usr/src/sys/i386/i386/genassym.c:36: warning: data definition has no type or storage class /usr/src/sys/i386/i386/genassym.c:36: warning: type defaults to 'int' in declaration of '__FBSDID' /usr/src/sys/i386/i386/genassym.c:36: warning: function declaration isn't a prototype /usr/src/sys/i386/i386/genassym.c:42:23: error: sys/param.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:43:23: error: sys/systm.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:44:23: error: sys/assym.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:45:21: error: sys/bio.h: No such file or directory /usr/src/sys/i386/i386/genassym.c:46:21: error: sys/buf.h: No such file or directory [root@ /usr/src]# [root@ /usr/src]# cat sys/i386/i386/genassym.c | grep cdefs.h #include sys/cdefs.h [root@ /usr/src]# ls -lah /usr/include/sys/cdefs.h -r--r--r-- 1 root wheel18K Feb 24 2008 /usr/include/sys/cdefs.h [root@ /usr/src]# wat wat wat Not sure what I'm missing here o.O ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel Compile issue
Mike, I think you misread what I sent, however I noticed that you used 'KERNELCONF' instead of 'config' (as I noted) but I still get the same error. I want to say the issue must have something to do with the fact that there's no environment variables that specify the include directories. FWIW here's what I have in my env: [root@ /usr/src]# env TERM=xterm SHELL=/usr/local/bin/bash SSH_CLIENT=192.168.23.1 2436 22 SSH_TTY=/dev/ttyp0 USER=erratic ENV=/home/erratic/.shrc PAGER=more FTP_PASSIVE_MODE=YES PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/home/erratic/bin MAIL=/var/mail/erratic BLOCKSIZE=K PWD=/usr/src EDITOR=vi SHLVL=1 HOME=/root LOGNAME=erratic SSH_CONNECTION=192.168.23.1 2436 192.168.23.249 22 _=/usr/bin/env OLDPWD=/usr/obj [root@ /usr/src]# On Mon, Mar 2, 2009 at 1:14 AM, Michael Powell nightre...@verizon.netwrote: Paige Thompson wrote: Also I wanted to note how I got to this problem: [root@ /usr/src]# make buildkernel config=GENERIC 2 error.log [snip] cd /usr/obj and rm -rf usr before trying again. Then cd /usr/src and do: make buildkernel KERNCONF=nameofsomeconffile another example: make buildkernel KERNCONF=GENERIC If you have an unadulterated GENERIC conf file present and you just issue make buildkernel by itself it will select GENERIC as default. Try correct procedure first, and hope there is no problem. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Kernel Compile issue
On Mon, Mar 2, 2009 at 2:43 AM, Paige Thompson erra...@devel.ws wrote: You're right, my source tree is incomplete: # pwd /usr/src/sys # cd sys sys: No such file or directory. # Thank you that helps a lot actually, it probably has something to do with the source archives that I downloaded not being extracted properly. I'm not a big fan of sysinstall, I prefer to work without it. You know the whole thing seems like its setup to try and force me to use sysinstall. Even the ftp client gives me a lot of flack about how I use mget (IE: mget ssys.* not being a valid way to just fetch all of the files) so of course i'm left to go through and fetch each of them individually :(( and for whatever reason, Im not having any luck with ncftp which I'm sure I could figure it out but I really don't think that I should have to install an additional FTP client just so I can fetch the kernel source ._. it kind of negates the whole minimalist aspect of having multiple archive files in the first place. Am I right? On Mon, Mar 2, 2009 at 2:24 AM, Polytropon free...@edvax.de wrote: On Mon, 2 Mar 2009 01:59:43 -0800, Paige Thompson erra...@devel.ws wrote: I have followed the manual, line for line or I wouldn't have gotten this far. I'm sorry but # cat /cdrom/src/ssys.[a-d]* | tar -xzvf - # cat /cdrom/src/sbase.[a-d]* | tar -xzvf - isn't typical archiving practice by today's standards (geez was it ever?) I'd thought that you've simply used sysinstall to install the distribution src-all, would be much easier. :-) Maybe you can try this again, but prior to this try, be sure to eliminate everything that might be interfering: # rm -r /usr/src # rm -r /usr/obj As per your suggestion to check in the Makefile, I have found nothing that really eludes me as to why file cdefs.h actually does exist in /usr/include/sys yet the compiler does not see it probably because the compiler is not being given the correct include path or an include path at all for that matter. As I mentioned, I think the compile process first generates a subtree in /usr/obk according to /usr/src and uses this for the compile process. I'm not sure if the system files will then be looked at... Reiteration: make buildkernel KERNCONF=GENERIC fails due to the following: # head error.log /usr/src/sys/i386/i386/genassym.c:35:23: error: sys/cdefs.h: No such file or directory when viewing the code /usr/src/sys/i386/i386/genassym.c on line 35 I find: #include sys/cdefs.h (please note the following carefully) Note that sys/cdefs.h is enclosed in as opposed to quotations. In C this indicates that the header should be included from an include path that's passed as an argument to the compiler-- *how ever and where ever that is done is what I would like to know.* Exactly. While ... refers to $CWD, ... refers to the -I parameter of cc. This parameter is set by Makefile. Be sure that your sources are complete. Now furthermore, /usr/local/include has *nothing* and I'm almost willing to bet you anything that if I copied * from /usr/include to /usr/local/include that would fix the issue except I don't think that's how this was intended to work. No. /usr/local does ONLY contain things that do not belong to the operating system, such as things installed by ports or packages. We're talking about the operating system (and its kernel) itself, so we're completely outside of /usr/local. In such a situation, cdefs.h can be found in different places: % locate cdefs.h /usr/include/sys/cdefs.h /usr/obj/usr/src/tmp/usr/include/sys/cdefs.h /usr/src/sys/sys/cdefs.h /usr/src/usr.sbin/lpr/common_source/lp.cdefs.h The first one is the system one's. The second one belongs to the compiling process, generated by the sources. The third and forth one ARE the sources for this. Based on what I have read here: http://www.nabble.com/What-is-CPP%27s-real-default-include-path--td17057087.html (and from that please note:) GCC looks in several different places for headers. On a normal Unix system, if you do not instruct it otherwise, it will look for headers requested with `#include FILE' in: /usr/local/include I came across this thread by googling: FreeBSD Include Path As I said, that is a Linux-ism. :-) For inclusion, first come the system's directories /usr/include, then the local additions /usr/local/include. The last ones are not of any value regarding the kernel and system compilation process. To be sure, ABSOLUTELY sure, use sysinstall to get the sources from the CD, deleting any previous existence of them. Then, # cd /usr/src # make buildkernel KERNCONF=GENERIC By the way, omitting KERNCONF loads GENERIC automatically. I think - and that's a quite wild guess - your problem is caused by incomplete sources. A final question: Are you using the sources from the CD as is (which release
Re: Kernel Compile issue
On Mon, Mar 2, 2009 at 2:44 AM, Paige Thompson erra...@devel.ws wrote: PS: it seems just straight up mget * works x.x k! satisfactory enough... On Mon, Mar 2, 2009 at 2:43 AM, Paige Thompson erra...@devel.ws wrote: You're right, my source tree is incomplete: # pwd /usr/src/sys # cd sys sys: No such file or directory. # Thank you that helps a lot actually, it probably has something to do with the source archives that I downloaded not being extracted properly. I'm not a big fan of sysinstall, I prefer to work without it. You know the whole thing seems like its setup to try and force me to use sysinstall. Even the ftp client gives me a lot of flack about how I use mget (IE: mget ssys.* not being a valid way to just fetch all of the files) so of course i'm left to go through and fetch each of them individually :(( and for whatever reason, Im not having any luck with ncftp which I'm sure I could figure it out but I really don't think that I should have to install an additional FTP client just so I can fetch the kernel source ._. it kind of negates the whole minimalist aspect of having multiple archive files in the first place. Am I right? On Mon, Mar 2, 2009 at 2:24 AM, Polytropon free...@edvax.de wrote: On Mon, 2 Mar 2009 01:59:43 -0800, Paige Thompson erra...@devel.ws wrote: I have followed the manual, line for line or I wouldn't have gotten this far. I'm sorry but # cat /cdrom/src/ssys.[a-d]* | tar -xzvf - # cat /cdrom/src/sbase.[a-d]* | tar -xzvf - isn't typical archiving practice by today's standards (geez was it ever?) I'd thought that you've simply used sysinstall to install the distribution src-all, would be much easier. :-) Maybe you can try this again, but prior to this try, be sure to eliminate everything that might be interfering: # rm -r /usr/src # rm -r /usr/obj As per your suggestion to check in the Makefile, I have found nothing that really eludes me as to why file cdefs.h actually does exist in /usr/include/sys yet the compiler does not see it probably because the compiler is not being given the correct include path or an include path at all for that matter. As I mentioned, I think the compile process first generates a subtree in /usr/obk according to /usr/src and uses this for the compile process. I'm not sure if the system files will then be looked at... Reiteration: make buildkernel KERNCONF=GENERIC fails due to the following: # head error.log /usr/src/sys/i386/i386/genassym.c:35:23: error: sys/cdefs.h: No such file or directory when viewing the code /usr/src/sys/i386/i386/genassym.c on line 35 I find: #include sys/cdefs.h (please note the following carefully) Note that sys/cdefs.h is enclosed in as opposed to quotations. In C this indicates that the header should be included from an include path that's passed as an argument to the compiler-- *how ever and where ever that is done is what I would like to know.* Exactly. While ... refers to $CWD, ... refers to the -I parameter of cc. This parameter is set by Makefile. Be sure that your sources are complete. Now furthermore, /usr/local/include has *nothing* and I'm almost willing to bet you anything that if I copied * from /usr/include to /usr/local/include that would fix the issue except I don't think that's how this was intended to work. No. /usr/local does ONLY contain things that do not belong to the operating system, such as things installed by ports or packages. We're talking about the operating system (and its kernel) itself, so we're completely outside of /usr/local. In such a situation, cdefs.h can be found in different places: % locate cdefs.h /usr/include/sys/cdefs.h /usr/obj/usr/src/tmp/usr/include/sys/cdefs.h /usr/src/sys/sys/cdefs.h /usr/src/usr.sbin/lpr/common_source/lp.cdefs.h The first one is the system one's. The second one belongs to the compiling process, generated by the sources. The third and forth one ARE the sources for this. Based on what I have read here: http://www.nabble.com/What-is-CPP%27s-real-default-include-path--td17057087.html (and from that please note:) GCC looks in several different places for headers. On a normal Unix system, if you do not instruct it otherwise, it will look for headers requested with `#include FILE' in: /usr/local/include I came across this thread by googling: FreeBSD Include Path As I said, that is a Linux-ism. :-) For inclusion, first come the system's directories /usr/include, then the local additions /usr/local/include. The last ones are not of any value regarding the kernel and system compilation process. To be sure, ABSOLUTELY sure, use sysinstall to get the sources from the CD, deleting any previous existence of them. Then, # cd /usr/src # make buildkernel KERNCONF=GENERIC By the way, omitting KERNCONF loads GENERIC automatically. I think - and that's
Re: CONF DNS
or maybe since you installed from an image (not over a network) the resolv.conf was never created. heres how i create it, never tried this freebsd though: seq --format=nameserver 4.2.2.%g 1 5 /etc/resolv.conf alternatively just adding this line: nameserver 4.2.2.1 or whatever your dns server besides 4.2.2.1 if you'd rather should suffice. -Adele (sent from my gphone!) On Feb 27, 2009 12:35 AM, Ivailo Tanusheff i.tanush...@procreditbank.bg wrote: The named.conf is used only if you need to set up your owm DNS server and you do not use someone other then the default. To resolve external hosts you need to enter the dns server IP in the /etc/resolv.conf file. It is not resolvE.conf. Hope this will help you. Regards, Ivailo Tanusheff Deputy Head of IT Department ProCredit Bank (Bulgaria) AD tel. +359 2 8135 890 fax +359 2 8135 110 http://www.procreditbank.bg Disclaimer: The information contained in this message is intended solely for the use of individual or entity to whom it is addressed and other authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission of the information contained in this message nor for any delay in its receipt. Fouz Azeem fouzaze...@yahoo.com Sent by: owner-freebsd-questi...@freebsd.org 27.02.2009 08:19 To questi...@freebsd.org cc Subject CONF DNS Dear FreeBSD I have install FreeBSD 7.1 from .iso I need to configure DNS I can find the name... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
