On December 21, 2007 10:01:39 am Jason George wrote: > >oOOps.... > > > >It seems someone else has the same error > > > >http://archives.neohapsis.com/archives/openbsd/2007-12/1903.html > > > >One solution: > > > >"However... It seems to work as it should from the > > anoncvs1.usa.openbsd.org mirror but *NOT* from my most used mirror which > > is > >anoncvs1.ca.openbsd.org. " > > > >From the OpenBSD site: > > > >" NOTE: If you are updating a source tree that you initially fetched > >from a different server, or from a CD, you *must* add the /-d > >[EMAIL PROTECTED]:/cvs/ options to cvs. > > > > # *cd /usr/src* > > # *cvs -d [EMAIL PROTECTED]:/cvs -q up -Pd"* > > > >Is it possible to update the tree fetched from the CD with this server > >(broken?), or do I need to use the .usa server for the entire download? > > If anoncvs1.ca is broken, then I would expect that we would all have > serious problems with our trees, since that is the machine that > redistributes cvs.openbsd.org, which is located in Theo's basement. When > cvs is really broken, it usually just lasts a few hours. The likelihood > that the whole tree has been busted for a week with no developers noticing > is pretty slim. > > And if you are on Shaw's network as a customer, the University of Alberta > is on-net with Shaw. Just check out whatever tag you want freshly and > don't worry about it. > > But if you are having issues building, then you are probably having a > source/binary synchronization issue.
I am not sure whether this has any relation to this problem. I initially assumed that the mistake was mine (it usually is) and probably due to some misconfiguration or path problem on my build machine. But it looks like I am not able to compile -current downloaded recently but -current from a couple of weeks ago (Dec 6, 2007) works without any problems. To doubly verify this I installed a fresh version of OpenBSD from the 4.2 CD on a new server and when I tried to build the kernel (-current source downloaded from ftp.ca.openbsd.org) I got the same error as on my build machine. I get the following when I do a cd /usr/src/sys/arch/i386/conf config GENERIC ../../../../conf/files:1001: syntax error ../../../../conf/files:1002: syntax error ../../../../conf/files:1003: syntax error ../../../../conf/files:1004: syntax error ../../../../conf/files:1005: syntax error ../../../../conf/files:1006: syntax error ../../../../conf/files:1007: syntax error ../../../../conf/files:1008: syntax error ../../../../conf/files:1009: syntax error ../../../../conf/files:1010: syntax error ../../../../conf/files:1011: syntax error ../../../../conf/files:1012: syntax error ../../../../conf/files:1013: syntax error ../../../../conf/files:1014: syntax error ../../../../conf/files:1015: syntax error ../../../../conf/files:1016: syntax error ../../../../conf/files:1017: syntax error ../../../../conf/files:1018: syntax error ../../../../conf/files:1019: syntax error ../../../../conf/files:1020: syntax error ../../../../conf/files:1021: syntax error ../../../../conf/files:1022: syntax error ../../../../conf/files:1023: syntax error ../../../../conf/files:1024: syntax error ../../../../conf/files:1025: syntax error ../../../../conf/files:1026: syntax error ../../../../conf/files:1027: syntax error ../../../../conf/files:1028: syntax error ../../../../conf/files:1029: syntax error ../../../../conf/files:1030: syntax error ../../../../conf/files:1031: syntax error ../../../../conf/files:1032: syntax error ../../../../conf/files:1033: syntax error ../../../../conf/files:1034: syntax error I did not have any problem building the kernel when I copied the source from CD3 on this new server. The files all appear to be in the right places and the paths look OK. My previous download from ftp.ca.openbsd.org was on Dec 6, 2007 and at that time I had no problems compiling the kernel. If anyone has insight into why this error occurs please let me know. Thanks very much, Vijay -- Vijay Sankar, M.Eng., P.Eng. President & CEO ForeTell Technologies Limited 59 Flamingo Avenue, Winnipeg, MB Canada R3J 0X6 Phone: +1 204 885 9535, E-Mail: [EMAIL PROTECTED]
