Re: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.ec638ti...@x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 12:48:20 Mark Andrews wrote: In message 3506767.fvm2kmt...@x220.ovitrap.com, Erich writes: On 05 June 2012 11:24:25 Mark Andrews wrote: It's already there. If you want the ports as of FreeBSD 4.x EOL then the tag is RELEASE_4_EOL. If you want ports as of FreeBSD 9.0 then the tag is RELEASE_9_9_0. I did not know this. Do you have a link for this? I never read about it. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. Erich ___ 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: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. mcl ___ 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: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. It's not particularly easy to see this on cvsweb. But let's take a look at a random Mk/bsd.*.mk file via 'cvs log': RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v Working file: bsd.apache.mk head: 1.36 branch: locks: strict access list: symbolic names: RELEASE_8_3_0: 1.35 RELEASE_9_0_0: 1.33 RELEASE_7_4_0: 1.26 RELEASE_8_2_0: 1.26 RELEASE_6_EOL: 1.26 [...] RELEASE_6_1_0: 1.9 RELEASE_5_5_0: 1.9 keyword substitution: kv total revisions: 36;selected revisions: 36 description: revision 1.36 date: 2012/05/23 08:17:48; author: miwi; state: Exp; lines: +2 -2 - Remove emacs mode, -*- mode: ...; -*- [1] - Comments for BUILD_ and RUN_DEPENDS fail to mention alternate means to specify dependencie [2] - Fix make reinstall [3] - Trivial comment change for PORTDATA [4] [...] and so forth. The line RELEASE_8_3_0: 1.35 tells you the version of this file as of tag RELEASE_8_3_0 was r1.35. So that's what's on the 8.3R distribution media. mcl ___ 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
[head tinderbox] failure on ia64/ia64
TB --- 2012-06-05 05:13:41 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-06-05 05:13:41 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-05 05:13:41 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-06-05 05:13:41 - cleaning the object tree TB --- 2012-06-05 05:13:41 - cvsupping the source tree TB --- 2012-06-05 05:13:41 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-06-05 05:14:45 - building world TB --- 2012-06-05 05:14:45 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 05:14:45 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 05:14:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 05:14:45 - SRCCONF=/dev/null TB --- 2012-06-05 05:14:45 - TARGET=ia64 TB --- 2012-06-05 05:14:45 - TARGET_ARCH=ia64 TB --- 2012-06-05 05:14:45 - TZ=UTC TB --- 2012-06-05 05:14:45 - __MAKE_CONF=/dev/null TB --- 2012-06-05 05:14:45 - cd /src TB --- 2012-06-05 05:14:45 - /usr/bin/make -B buildworld World build started on Tue Jun 5 05:14:46 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Jun 5 06:47:39 UTC 2012 TB --- 2012-06-05 06:47:39 - generating LINT kernel config TB --- 2012-06-05 06:47:39 - cd /src/sys/ia64/conf TB --- 2012-06-05 06:47:39 - /usr/bin/make -B LINT TB --- 2012-06-05 06:47:39 - cd /src/sys/ia64/conf TB --- 2012-06-05 06:47:39 - /usr/sbin/config -m LINT TB --- 2012-06-05 06:47:39 - building LINT kernel TB --- 2012-06-05 06:47:39 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 06:47:39 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 06:47:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 06:47:39 - SRCCONF=/dev/null TB --- 2012-06-05 06:47:39 - TARGET=ia64 TB --- 2012-06-05 06:47:39 - TARGET_ARCH=ia64 TB --- 2012-06-05 06:47:39 - TZ=UTC TB --- 2012-06-05 06:47:39 - __MAKE_CONF=/dev/null TB --- 2012-06-05 06:47:39 - cd /src TB --- 2012-06-05 06:47:39 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Jun 5 06:47:39 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] ln -sf /obj/ia64.ia64/src/sys/LINT/opt_compat.h opt_compat.h ln -sf /obj/ia64.ia64/src/sys/LINT/opt_capsicum.h opt_capsicum.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/ia64.ia64/src/sys/LINT -std=iso9899:1999 /src/sys/modules/filemon/../../dev/filemon/filemon.c In file included from /src/sys/modules/filemon/../../dev/filemon/filemon.c:114: /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:664:2: error: #error Machine type not supported /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:710:2: error: #error Machine type not supported mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/filemon. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-05 06:50:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-05 06:50:27 - ERROR: failed to build LINT kernel TB --- 2012-06-05 06:50:27 - 4306.14 user 660.46 system 5805.88 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ 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: Why Are You NOT Using FreeBSD?
On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.EC638TI0j3 at x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 12:48:20 Mark Andrews wrote: In message 3506767.Fvm2KmtnYf at x220.ovitrap.com, Erich writes: On 05 June 2012 11:24:25 Mark Andrews wrote: It's already there. If you want the ports as of FreeBSD 4.x EOL then the tag is RELEASE_4_EOL. If you want ports as of FreeBSD 9.0 then the tag is RELEASE_9_9_0. I did not know this. Do you have a link for this? I never read about it. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. I sent a long reply to your earlier message on freebsd-ports explaining exactly this -- how each Ports tree snapshot has a version number: the date spec. Also, how a few special snapshots also have a second version number: the release tag. I also explained how to find and use these, with and without cvs. Am I wasting my time by trying to answer your questions, E.? b. ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:01:37 Mark Linimon wrote: On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. this is the problem. I would like to be able to go back to the last release in case of a problem and restart from there. When it is possible to tag the EOL, it should be as easy to tag the SOL (start of life). This would save a lot of time for many people. Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. It's not particularly easy to see this on cvsweb. But let's take a look at a random Mk/bsd.*.mk file via 'cvs log': here we are. I never found this. RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v Working file: bsd.apache.mk head: 1.36 branch: locks: strict access list: symbolic names: RELEASE_8_3_0: 1.35 RELEASE_9_0_0: 1.33 RELEASE_7_4_0: 1.26 RELEASE_8_2_0: 1.26 RELEASE_6_EOL: 1.26 [...] RELEASE_6_1_0: 1.9 RELEASE_5_5_0: 1.9 If this list would make it into the documentation, all I asked would be already there. I could write this but my English will need some corrections. If you could give a link to how to do this properly, I would do it then. But is this true for apache only or for the whole ports tree? Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 3:08:17 b. f. wrote: On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.EC638TI0j3 at x220.ovitrap.com, Erich writes: Hi, All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. I sent a long reply to your earlier message on freebsd-ports explaining exactly this -- how each Ports tree snapshot has a version number: the date spec. Also, how a few special snapshots also have a second version number: the release tag. I also explained how to find and use these, with and without cvs. Am I wasting my time by trying to answer your questions, E.? I think that you missed my point. The point is that this has to be made available for beginners. As long as the handbook states that this does not apply to the ports tree, at least beginners will stop there. Erich ___ 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: Why Are You NOT Using FreeBSD?
On 6/5/12, Erich erichfreebsdl...@ovitrap.com wrote: Hi, On 05 June 2012 3:08:17 b. f. wrote: On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.EC638TI0j3 at x220.ovitrap.com, Erich writes: Hi, All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. I sent a long reply to your earlier message on freebsd-ports explaining exactly this -- how each Ports tree snapshot has a version number: the date spec. Also, how a few special snapshots also have a second version number: the release tag. I also explained how to find and use these, with and without cvs. Am I wasting my time by trying to answer your questions, E.? I think that you missed my point. The point is that this has to be made available for beginners. As long as the handbook states that this does not apply to the ports tree, at least beginners will stop there. If you had hoped to make your point by feigning ignorance of something that you had just been told on another list, then, yes, I missed your point -- it was a decidedly subtle one. You write in this thread: I did not know this. Do you have a link for this? I never read about it. Despite the fact that I explained it to you earlier, with an example: http://lists.freebsd.org/pipermail/freebsd-ports/2012-June/075491.html The part of the Handbook that you cited above, at: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvs-tags.html is the introduction to A.7.1. It refers only to branch tags, and not to the release tags discussed in A.7.2, where the ports release tags are mentioned. This was also in my earlier message, along with the comment that A.7.2 could be improved. As far as the version numbers are concerned, I do not understand what you want. I already told you how you could use the existing version numbers with a one-line modification to a sup file, or via cvs. Do you want the date spec of the ports tree to be included in the name of the port tarballs distributed on the FreeBSD server? Or that you want portsnap to get a feature to selectively roll-back to earlier ports tree snapshots? Or that you simply want changes to the documentation, explaining how to roll back? As I told you, I'm a bit skeptical that your hypothetical beginner, after having encountered a problem building a port, would usually be able to diagnose the problem and find the right snapshot to use. And those that aren't beginners could probably figure out how to do so with the documentation that already exists. But I suppose that the document committers would consider a proposal to add an example of how to perform a roll-back. If you want to discuss this further, please move it to a new topic on the freebsd-ports or freebsd-doc lists, which seem more appropriate. b. ___ 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: Why Are You NOT Using FreeBSD?
On Jun 5, 2012 3:07 AM, Erich erichfreebsdl...@ovitrap.com wrote: Hi, On 05 June 2012 11:24:25 Mark Andrews wrote: Version tagging is just a convient way to get a snapshot at a particular point in time unless you create branches that are them we do not ask for more. There should be only one difference to a snapshot. As snapshot has a date. No matter in what state the ports tree was, it is in that state in the ports tree. If user - especially the one not so fit in this aspect - want to use a snapshot, it will be difficult to impossible to figure out which one they need. If version numbers would be introduced, it would be ok to use the version number of the FreeBSD and have only version available which reflect the release version of the ports tree. People here want to make always a perfect system. People like me want to have some small things in there available with a click. As the ports trees are there anyway, only the direct link to the snapshot of that day or a version number in the ports tree would be needed to make this available for people who just want to use FreeBSD. Please note, I do not want any extra work spend here to make this perfect. I only want a simple way to fall back to a big net which is not that old from which the user can restart. I and most others will purposely refuse to document this in any official capacity, but I'll give you a hint. Look for the date tag in man csup. Chris ___ 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: Why Are You NOT Using FreeBSD?
On 5 June 2012 09:25, Erich erichfreebsdl...@ovitrap.com wrote: Hi, On 05 June 2012 3:08:17 b. f. wrote: On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.EC638TI0j3 at x220.ovitrap.com, Erich writes: Hi, All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. I sent a long reply to your earlier message on freebsd-ports explaining exactly this -- how each Ports tree snapshot has a version number: the date spec. Also, how a few special snapshots also have a second version number: the release tag. I also explained how to find and use these, with and without cvs. Am I wasting my time by trying to answer your questions, E.? I think that you missed my point. The point is that this has to be made available for beginners. As long as the handbook states that this does not apply to the ports tree, at least beginners will stop there. Beginners should be using packages anyway. It is absolutely a bad idea for beginners to be using tagged/dated ports trees-- they are not supported and will lead to many complaints about problems that were solved since the tag. Chris ___ 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
[head tinderbox] failure on sparc64/sparc64
TB --- 2012-06-05 09:16:45 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-06-05 09:16:45 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-05 09:16:45 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-06-05 09:16:45 - cleaning the object tree TB --- 2012-06-05 09:18:35 - cvsupping the source tree TB --- 2012-06-05 09:18:35 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2012-06-05 09:19:31 - building world TB --- 2012-06-05 09:19:31 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 09:19:31 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 09:19:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 09:19:31 - SRCCONF=/dev/null TB --- 2012-06-05 09:19:31 - TARGET=sparc64 TB --- 2012-06-05 09:19:31 - TARGET_ARCH=sparc64 TB --- 2012-06-05 09:19:31 - TZ=UTC TB --- 2012-06-05 09:19:31 - __MAKE_CONF=/dev/null TB --- 2012-06-05 09:19:31 - cd /src TB --- 2012-06-05 09:19:31 - /usr/bin/make -B buildworld World build started on Tue Jun 5 09:19:32 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Jun 5 10:18:04 UTC 2012 TB --- 2012-06-05 10:18:04 - generating LINT kernel config TB --- 2012-06-05 10:18:04 - cd /src/sys/sparc64/conf TB --- 2012-06-05 10:18:04 - /usr/bin/make -B LINT TB --- 2012-06-05 10:18:04 - cd /src/sys/sparc64/conf TB --- 2012-06-05 10:18:04 - /usr/sbin/config -m LINT TB --- 2012-06-05 10:18:04 - building LINT kernel TB --- 2012-06-05 10:18:04 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 10:18:04 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 10:18:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 10:18:04 - SRCCONF=/dev/null TB --- 2012-06-05 10:18:04 - TARGET=sparc64 TB --- 2012-06-05 10:18:04 - TARGET_ARCH=sparc64 TB --- 2012-06-05 10:18:04 - TZ=UTC TB --- 2012-06-05 10:18:04 - __MAKE_CONF=/dev/null TB --- 2012-06-05 10:18:04 - cd /src TB --- 2012-06-05 10:18:04 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Jun 5 10:18:05 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] ln -sf /obj/sparc64.sparc64/src/sys/LINT/opt_compat.h opt_compat.h ln -sf /obj/sparc64.sparc64/src/sys/LINT/opt_capsicum.h opt_capsicum.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/sparc64.sparc64/src/sys/LINT -std=iso9899:1999 /src/sys/modules/filemon/../../dev/filemon/filemon.c In file included from /src/sys/modules/filemon/../../dev/filemon/filemon.c:114: /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:664:2: error: #error Machine type not supported /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:710:2: error: #error Machine type not supported mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/filemon. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64.sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-05 10:19:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-05 10:19:40 - ERROR: failed to build LINT kernel TB --- 2012-06-05 10:19:40 - 2986.82 user 522.80 system 3774.77 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ 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: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. mcl ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the location where this information is missing for beginners. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I simply cannot believe that beginners would expect this information to find this in the section for updating the kernel. Erich ___ 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: 10-CURRENT r235646 open-vm-tools-8.6.0-425873
El día Thursday, May 31, 2012 a las 11:34:55AM -0400, John Baldwin escribió: cc1: warnings being treated as errors if_vxn.c: In function 'vxn_load_multicast': if_vxn.c:719: warning: implicit declaration of function 'IF_ADDR_LOCK' if_vxn.c:719: warning: nested extern declaration of 'IF_ADDR_LOCK' [-Wnested-ext erns] if_vxn.c:746: warning: implicit declaration of function 'IF_ADDR_UNLOCK' if_vxn.c:746: warning: nested extern declaration of 'IF_ADDR_UNLOCK' [-Wnested-e xterns] *** [if_vxn.o] Error code 1 It should be using if_mcast_rlock() and if_mcast_runlock() instead of using those macros directly. This works all the way back to 8.0. Thanks for your patch proposal; but using this it can't find the if_mcast_rlock() and if_mcast_runlock() functions declaration (and I don't see them in /usr/src/... ); based on the SVN diff of the kernel: http://svnweb.freebsd.org/base/head/sys/net/if_var.h?r1=231229r2=233202pathrev=233202 I came up with another proposal: *** modules/freebsd/vmxnet/net_compat.h.origWed Sep 21 20:25:15 2011 --- modules/freebsd/vmxnet/net_compat.h Tue Jun 5 15:13:55 2012 *** *** 170,178 #if __FreeBSD_version 505000 # define VXN_IF_ADDR_LOCK(_ifp) # define VXN_IF_ADDR_UNLOCK(_ifp) #else ! # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_LOCK((_ifp)) ! # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_UNLOCK((_ifp)) #endif #endif /* _VXN_NET_COMPAT_H_ */ --- 170,181 #if __FreeBSD_version 505000 # define VXN_IF_ADDR_LOCK(_ifp) # define VXN_IF_ADDR_UNLOCK(_ifp) + #elif __FreeBSD_version 80 + # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_LOCK((_ifp)) + # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_UNLOCK((_ifp)) #else ! # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_WLOCK((_ifp)) ! # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_WUNLOCK((_ifp)) #endif #endif /* _VXN_NET_COMPAT_H_ */ and using this it compiles fine; but later on it has another problem: # make install clean ... Making all in modules make VM_UNAME=10.0-CURRENT MV=mv RM=rm OVT_SOURCE_DIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873 MODULEBUILDDIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd -C /usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmmemctl make VM_UNAME=10.0-CURRENT MV=mv RM=rm OVT_SOURCE_DIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873 MODULEBUILDDIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd -C /usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmxnet make VM_UNAME=10.0-CURRENT MV=mv RM=rm OVT_SOURCE_DIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873 MODULEBUILDDIR=/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd -C /usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmblock Warning: Object directory not changed from original /usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmblock cc -O2 -pipe -Wall -Werror -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/lib/include -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/shared -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmblock -I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/shared/vmblock -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c vnops.c vnops.c: In function 'VMBlockVopInactive': vnops.c:1373: error: too many arguments to function 'vrecycle' *** [vnops.o] Error code 1 Thanks for another hint matthias -- Matthias Apitz e g...@unixarea.de - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ 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: 10-CURRENT r235646 open-vm-tools-8.6.0-425873
El día Tuesday, June 05, 2012 a las 03:27:51PM +0200, Matthias Apitz escribió:
cc -O2 -pipe -Wall -Werror -fno-strict-aliasing -Werror -D_KERNEL
-DKLD_MODULE -nostdinc
-I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/lib/include
-I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/shared
-I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/freebsd/vmblock
-I/usr/ports/emulators/open-vm-tools/work/open-vm-tools-8.6.0-425873/modules/shared/vmblock
-I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100
--param large-function-growth=1000 -fno-common -mno-align-long-strings
-mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls
-Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith
-Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions
-Wmissing-include-dirs -fdiagnostics-show-option -c vnops.c
vnops.c: In function 'VMBlockVopInactive':
vnops.c:1373: error: too many arguments to function 'vrecycle'
*** [vnops.o] Error code 1
got it finally compiled and installed as
# make install WITHOUT_FUSE=yes
with this additional patch:
*** modules/freebsd/vmblock/vnops.c.origWed Sep 21 20:25:15 2011
--- modules/freebsd/vmblock/vnops.c Tue Jun 5 16:01:45 2012
***
*** 1362,1368
*/
{
struct vnode *vp = ap-a_vp;
-struct thread *td = ap-a_td;
vp-v_object = NULL;
--- 1362,1367
***
*** 1370,1376
* If this is the last reference, then free up the vnode so as not to
* tie up the lower vnode.
*/
!vrecycle(vp, td);
return 0;
}
--- 1369,1375
* If this is the last reference, then free up the vnode so as not to
* tie up the lower vnode.
*/
!vrecycle(vp);
return 0;
}
--
Matthias Apitz
e g...@unixarea.de - w http://www.unixarea.de/
UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5
___
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: 10-CURRENT r235646 open-vm-tools-8.6.0-425873
On Tuesday, June 05, 2012 9:27:51 am Matthias Apitz wrote: El día Thursday, May 31, 2012 a las 11:34:55AM -0400, John Baldwin escribió: cc1: warnings being treated as errors if_vxn.c: In function 'vxn_load_multicast': if_vxn.c:719: warning: implicit declaration of function 'IF_ADDR_LOCK' if_vxn.c:719: warning: nested extern declaration of 'IF_ADDR_LOCK' [-Wnested-ext erns] if_vxn.c:746: warning: implicit declaration of function 'IF_ADDR_UNLOCK' if_vxn.c:746: warning: nested extern declaration of 'IF_ADDR_UNLOCK' [-Wnested-e xterns] *** [if_vxn.o] Error code 1 It should be using if_mcast_rlock() and if_mcast_runlock() instead of using those macros directly. This works all the way back to 8.0. Thanks for your patch proposal; but using this it can't find the if_mcast_rlock() and if_mcast_runlock() functions declaration (and I don't see them in /usr/src/... ); Sorry, they are if_maddr_rlock() and if_maddr_runlock(). They are in if_var.h right below the macro you looked at. :) quote /* * Locks for address lists on the network interface. */ #define IF_ADDR_LOCK_INIT(if) rw_init((if)-if_addr_lock, if_addr_lock) #define IF_ADDR_LOCK_DESTROY(if)rw_destroy((if)-if_addr_lock) #define IF_ADDR_WLOCK(if) rw_wlock((if)-if_addr_lock) #define IF_ADDR_WUNLOCK(if) rw_wunlock((if)-if_addr_lock) #define IF_ADDR_RLOCK(if) rw_rlock((if)-if_addr_lock) #define IF_ADDR_RUNLOCK(if) rw_runlock((if)-if_addr_lock) #define IF_ADDR_LOCK_ASSERT(if) rw_assert((if)-if_addr_lock, RA_LOCKED) #define IF_ADDR_WLOCK_ASSERT(if) rw_assert((if)-if_addr_lock, RA_WLOCKED) /* * Function variations on locking macros intended to be used by loadable * kernel modules in order to divorce them from the internals of address list * locking. */ voidif_addr_rlock(struct ifnet *ifp); /* if_addrhead */ voidif_addr_runlock(struct ifnet *ifp); /* if_addrhead */ voidif_maddr_rlock(struct ifnet *ifp); /* if_multiaddrs */ voidif_maddr_runlock(struct ifnet *ifp);/* if_multiaddrs */ /quote based on the SVN diff of the kernel: http://svnweb.freebsd.org/base/head/sys/net/if_var.h?r1=231229r2=233202pathrev=233202 I came up with another proposal: *** modules/freebsd/vmxnet/net_compat.h.origWed Sep 21 20:25:15 2011 --- modules/freebsd/vmxnet/net_compat.h Tue Jun 5 15:13:55 2012 *** *** 170,178 #if __FreeBSD_version 505000 # define VXN_IF_ADDR_LOCK(_ifp) # define VXN_IF_ADDR_UNLOCK(_ifp) #else ! # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_LOCK((_ifp)) ! # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_UNLOCK((_ifp)) #endif #endif /* _VXN_NET_COMPAT_H_ */ --- 170,181 #if __FreeBSD_version 505000 # define VXN_IF_ADDR_LOCK(_ifp) # define VXN_IF_ADDR_UNLOCK(_ifp) + #elif __FreeBSD_version 80 + # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_LOCK((_ifp)) + # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_UNLOCK((_ifp)) #else ! # define VXN_IF_ADDR_LOCK(_ifp) IF_ADDR_WLOCK((_ifp)) ! # define VXN_IF_ADDR_UNLOCK(_ifp) IF_ADDR_WUNLOCK((_ifp)) #endif #endif /* _VXN_NET_COMPAT_H_ */ and using this it compiles fine; but later on it has another problem: No, we do not wish to expose those to drivers as we do not want the locks part of the ABI. Plus, you should be using read-locks for this anyway. -- John Baldwin ___ 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
[head tinderbox] failure on ia64/ia64
TB --- 2012-06-05 14:23:10 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-06-05 14:23:10 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-05 14:23:10 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-06-05 14:23:10 - cleaning the object tree TB --- 2012-06-05 14:24:33 - cvsupping the source tree TB --- 2012-06-05 14:24:33 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-06-05 14:26:05 - building world TB --- 2012-06-05 14:26:05 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 14:26:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 14:26:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 14:26:05 - SRCCONF=/dev/null TB --- 2012-06-05 14:26:05 - TARGET=ia64 TB --- 2012-06-05 14:26:05 - TARGET_ARCH=ia64 TB --- 2012-06-05 14:26:05 - TZ=UTC TB --- 2012-06-05 14:26:05 - __MAKE_CONF=/dev/null TB --- 2012-06-05 14:26:05 - cd /src TB --- 2012-06-05 14:26:05 - /usr/bin/make -B buildworld World build started on Tue Jun 5 14:26:06 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Jun 5 15:56:56 UTC 2012 TB --- 2012-06-05 15:56:56 - generating LINT kernel config TB --- 2012-06-05 15:56:56 - cd /src/sys/ia64/conf TB --- 2012-06-05 15:56:56 - /usr/bin/make -B LINT TB --- 2012-06-05 15:56:56 - cd /src/sys/ia64/conf TB --- 2012-06-05 15:56:56 - /usr/sbin/config -m LINT TB --- 2012-06-05 15:56:56 - building LINT kernel TB --- 2012-06-05 15:56:56 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 15:56:56 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 15:56:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 15:56:56 - SRCCONF=/dev/null TB --- 2012-06-05 15:56:56 - TARGET=ia64 TB --- 2012-06-05 15:56:56 - TARGET_ARCH=ia64 TB --- 2012-06-05 15:56:56 - TZ=UTC TB --- 2012-06-05 15:56:56 - __MAKE_CONF=/dev/null TB --- 2012-06-05 15:56:56 - cd /src TB --- 2012-06-05 15:56:56 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Jun 5 15:56:57 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] ln -sf /obj/ia64.ia64/src/sys/LINT/opt_compat.h opt_compat.h ln -sf /obj/ia64.ia64/src/sys/LINT/opt_capsicum.h opt_capsicum.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/ia64.ia64/src/sys/LINT -std=iso9899:1999 /src/sys/modules/filemon/../../dev/filemon/filemon.c In file included from /src/sys/modules/filemon/../../dev/filemon/filemon.c:114: /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:664:2: error: #error Machine type not supported /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:710:2: error: #error Machine type not supported mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/filemon. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-05 15:59:52 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-05 15:59:52 - ERROR: failed to build LINT kernel TB --- 2012-06-05 15:59:52 - 4303.02 user 667.22 system 5802.86 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full ___ 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
est man page
I note that x86/cpufreq/est.c has some tuneables and I have processors that seem to be not supported by est even though they appear to have Speedstep features: p4tcc0: CPU Frequency Thermal Control on cpu0 est1: Enhanced SpeedStep Frequency Control on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 15 device_attach: est1 attach returned 6 1. How do I generate new speed tables for est? 2. Any objections to an est(4) man page? Sean ___ 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
[head tinderbox] failure on sparc64/sparc64
TB --- 2012-06-05 18:14:30 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-06-05 18:14:30 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2012-06-05 18:14:30 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-06-05 18:14:30 - cleaning the object tree TB --- 2012-06-05 18:15:43 - cvsupping the source tree TB --- 2012-06-05 18:15:43 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2012-06-05 18:16:20 - building world TB --- 2012-06-05 18:16:20 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 18:16:20 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 18:16:20 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 18:16:20 - SRCCONF=/dev/null TB --- 2012-06-05 18:16:20 - TARGET=sparc64 TB --- 2012-06-05 18:16:20 - TARGET_ARCH=sparc64 TB --- 2012-06-05 18:16:20 - TZ=UTC TB --- 2012-06-05 18:16:20 - __MAKE_CONF=/dev/null TB --- 2012-06-05 18:16:20 - cd /src TB --- 2012-06-05 18:16:20 - /usr/bin/make -B buildworld World build started on Tue Jun 5 18:16:21 UTC 2012 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Tue Jun 5 19:14:56 UTC 2012 TB --- 2012-06-05 19:14:56 - generating LINT kernel config TB --- 2012-06-05 19:14:56 - cd /src/sys/sparc64/conf TB --- 2012-06-05 19:14:56 - /usr/bin/make -B LINT TB --- 2012-06-05 19:14:56 - cd /src/sys/sparc64/conf TB --- 2012-06-05 19:14:56 - /usr/sbin/config -m LINT TB --- 2012-06-05 19:14:56 - building LINT kernel TB --- 2012-06-05 19:14:56 - CROSS_BUILD_TESTING=YES TB --- 2012-06-05 19:14:56 - MAKEOBJDIRPREFIX=/obj TB --- 2012-06-05 19:14:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-06-05 19:14:56 - SRCCONF=/dev/null TB --- 2012-06-05 19:14:56 - TARGET=sparc64 TB --- 2012-06-05 19:14:56 - TARGET_ARCH=sparc64 TB --- 2012-06-05 19:14:56 - TZ=UTC TB --- 2012-06-05 19:14:56 - __MAKE_CONF=/dev/null TB --- 2012-06-05 19:14:56 - cd /src TB --- 2012-06-05 19:14:56 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Jun 5 19:14:56 UTC 2012 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies [...] ln -sf /obj/sparc64.sparc64/src/sys/LINT/opt_compat.h opt_compat.h ln -sf /obj/sparc64.sparc64/src/sys/LINT/opt_capsicum.h opt_capsicum.h rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq -I/obj/sparc64.sparc64/src/sys/LINT -std=iso9899:1999 /src/sys/modules/filemon/../../dev/filemon/filemon.c In file included from /src/sys/modules/filemon/../../dev/filemon/filemon.c:114: /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:664:2: error: #error Machine type not supported /src/sys/modules/filemon/../../dev/filemon/filemon_wrapper.c:710:2: error: #error Machine type not supported mkdep: compile failed *** Error code 1 Stop in /src/sys/modules/filemon. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/sparc64.sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-06-05 19:16:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-06-05 19:16:31 - ERROR: failed to build LINT kernel TB --- 2012-06-05 19:16:31 - 2983.86 user 528.06 system 3720.91 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full ___ 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: est man page
On Tue, 2012-06-05 at 11:55 -0700, Sean Bruno wrote: I note that x86/cpufreq/est.c has some tuneables and I have processors that seem to be not supported by est even though they appear to have Speedstep features: p4tcc0: CPU Frequency Thermal Control on cpu0 est1: Enhanced SpeedStep Frequency Control on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 15 device_attach: est1 attach returned 6 *ACTUALLY* this was caused by the Dell r410 that I was using having its Power Managment control set to Advanced Power Management and not OS Control. After I set that, the acpi methods in est attached correctly. Sean ___ 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
Unable to buildworld with ccache
Hi,
Buildworld completes successfully with ccache switched off, it fails
otherwise, system was built WITH_CLANG_IS_CC previously.
/usr/local/libexec/ccache/world/cc -O2 -fno-strict-aliasing -pipe
-march=core2 -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64
-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/jemalloc/include
-DMALLOC_PRODUCTION -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 -Qunused-arguments -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -c
/usr/src/lib/libc/net/gethostbynis.c -o gethostbynis.o
/usr/local/libexec/ccache/world/cc -fpic -DPIC -O2 -fno-strict-aliasing
-pipe -march=core2 -I/usr/src/lib/libc/include
-I/usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64
-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/jemalloc/include
-DMALLOC_PRODUCTION -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 -Qunused-arguments -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized
-Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int
-Wno-tautological-compare -Wno-unused-value -Wno-parentheses-equality
-Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enum -c
/usr/src/lib/libc/net/gethostbynis.c -o gethostbynis.So
In file included from /usr/src/lib/libc/net/getaddrinfo.c:1:
/usr/src/lib/libc/net/getaddrinfo.c:467:15: error: explicitly assigning
a variable of type 'int' to itself [-Werror,-Wself-assign]
do { error = (error); goto bad; } while ( 0);
~ ^ ~
1 error generated.
*** [getaddrinfo.o] Error code 1
In file included from /usr/src/lib/libc/net/getaddrinfo.c:1:
/usr/src/lib/libc/net/getaddrinfo.c:467:15: error: explicitly assigning
a variable of type 'int' to itself [-Werror,-Wself-assign]
do { error = (error); goto bad; } while ( 0);
~ ^ ~
1 error generated.
*** [getaddrinfo.So] Error code 1
2 errors
*** [lib/libc__L] Error code 2
1 error
*** [libraries] Error code 2
1 error
*** [_libraries] Error code 2
1 error
*** [buildworld] Error code 2
1 error
Any pointers appreciated
Sevan / Venture37
___
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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the point in which all normal users will give up: The handbook states this: Which version(s) of them do you want? 'With CVSup, you can receive virtually any version of the sources that ever existed. That is possible because the cvsupd server works directly from the CVS repository, which contains all of the versions. You specify which one of them you want using the tag= and date= value fields. Warning: Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. In particular, use only tag=. for the ports-* collections.' Why should a normal user continue to search for a tag when the handbook is so clear on this? Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 10:55:57 Chris Rees wrote: On 5 June 2012 09:25, Erich erichfreebsdl...@ovitrap.com wrote: On 05 June 2012 3:08:17 b. f. wrote: On 05 June 2012 15:33:16 Mark Andrews wrote: In message 2490439.EC638TI0j3 at x220.ovitrap.com, Erich writes: Hi, All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. I understand this that I can use these tags on the FreeBSD sources but not on the ports. I never tried this on the ports. I sent a long reply to your earlier message on freebsd-ports explaining exactly this -- how each Ports tree snapshot has a version number: the date spec. Also, how a few special snapshots also have a second version number: the release tag. I also explained how to find and use these, with and without cvs. Am I wasting my time by trying to answer your questions, E.? I think that you missed my point. The point is that this has to be made available for beginners. As long as the handbook states that this does not apply to the ports tree, at least beginners will stop there. Beginners should be using packages anyway. when are then allowed to use the ports? The first time they will use the ports, they are beginners again. It is absolutely a bad idea for beginners to be using tagged/dated ports trees-- they are not supported and will lead to many complaints about problems that were solved since the tag. How do they fall back when things went wrong? The handbook states that there is no fall back option. Their fall back option has a name: Windows. Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 05 June 2012 7:13:47 Mark Linimon wrote: On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. my problem with this is that the documentation states something very different: From the handbook at the location where beginners will look for it: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html 'Which version(s) of them do you want? With CVSup, you can receive virtually any version of the sources that ever existed. That is possible because the cvsupd server works directly from the CVS repository, which contains all of the versions. You specify which one of them you want using the tag= and date= value fields. Warning: Be very careful to specify any tag= fields correctly. Some tags are valid only for certain collections of files. If you specify an incorrect or misspelled tag, CVSup will delete files which you probably do not want deleted. In particular, use only tag=. for the ports-* collections.' I think that this states very clearly that there are no tags. So, after we learned that every thing I am asking is there anyway in an official and supported way, only the documentation has to be changed. Erich ___ 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: Why Are You NOT Using FreeBSD?
Hi, On 06 June 2012 0:42:47 Mark Andrews wrote: In message 1541214.zfrdxxb...@x220.ovitrap.com, Erich writes: Hi, On 05 June 2012 1:09:50 Mark Linimon wrote: On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. I found now the location where this information is missing for beginners. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html I simply cannot believe that beginners would expect this information to find this in the section for updating the kernel. Erich Because, while you believe it is better to roll back to the release point it really isn't. The ports tree is rarely broken for long. When it is broken people will tell you to roll back to a good date and give you the date to use. I've had to roll back a couple of times in 11+ years of updating and never to a release point. What is there is good advice. Use a up-to-date ports tree. If it is broken wait a days or so and try again. If it is still broken report the problem using send-pr. you will find thousands of notes that people should not run bleeding edge when it comes to the kernel. But people are forced to run bleeding edge on the ports. The documentation than even states that there is no fall back. You state it as being just normal to wait for a week or more until the problem is solved. I cannot imagine that people who come to FreeBSD and get trapped somehow will stick to it then. They might will ask on this list just to learn that there is no help available. Just wait. People who have to make decisions what operating system should be used on their workplaces will not like this and stick with whatever they have. I believe that this is a very good user repellent. Erich ___ 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
