docs/178286: [PATCH] document the LOCAL_* vars in build(7)

[Garrett Cooper]

>Number: 178286
>Category:   docs
>Synopsis:   [PATCH] document the LOCAL_* vars in build(7)
>Confidential:   no
>Severity:   non-critical
>Priority:   low
>Responsible:freebsd-doc
>State:  open
>Quarter:
>Keywords:   
>Date-Required:
>Class:  doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed May 01 21:30:00 UTC 2013
>Closed-Date:
>Last-Modified:
>Originator: Garrett Cooper
>Release:10-CURRENT
>Organization:
EMC Isilon
>Environment:
FreeBSD gran-tourismo.west.isilon.com 10.0-CURRENT FreeBSD 10.0-CURRENT #2 
r+ba9afe9: Fri Apr 19 20:29:10 PDT 2013 
gcoo...@gran-tourismo.west.isilon.com:/usr/obj/usr/src/sys/GRAN-TOURISMO  amd64
>Description:
Several variables were added to the build recently, but aren't documented. The 
attached patch documents their existence.
>How-To-Repeat:

>Fix:


Patch attached with submission follows:

>From 941fe31f4e33812de0355a3f51787609defe87d1 Mon Sep 17 00:00:00 2001
From: Garrett Cooper 
Date: Wed, 1 May 2013 14:13:02 -0700
Subject: [PATCH 1/2] Document the rest of the LOCAL_* vars in CURRENT

Signed-off-by: Garrett Cooper 
---
 share/man/man7/build.7 | 21 +++--
 1 file changed, 19 insertions(+), 2 deletions(-)

diff --git a/share/man/man7/build.7 b/share/man/man7/build.7
index 931b444..73f9418 100644
--- a/share/man/man7/build.7
+++ b/share/man/man7/build.7
@@ -411,8 +411,25 @@ then
 is set to the value of
 .Va KERNFAST .
 .It Va LOCAL_DIRS
-If set, this variable supplies a list of additional directories to
-build, relative to the root of the source tree.
+If set, this variable supplies a list of additional directories relative to
+the root of the source tree to build as part of the
+.Cm everything
+target.
+.It Va LOCAL_LIB_DIRS
+If set, this variable supplies a list of additional directories relative to
+the root of the source tree to build as part of the
+.Cm libraries
+target.
+.It Va LOCAL_MTREE
+If set, this variable supplies a list of additional mtrees relative to the
+root of the source tree to use as part of the
+.Cm hierarchy
+target.
+.It Va LOCAL_TOOL_DIRS
+If set, this variable supplies a list of additional directories relative to
+the root of the source tree to build as part of the
+.Cm build-tools
+target.
 .It Va PORTS_MODULES
 A list of ports with kernel modules that should be built and installed
 as part of the
-- 
1.8.2.1



>Release-Note:
>Audit-Trail:
>Unformatted:
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"

Updating a broken link in page -http://docs.lvl.ru/handbook/bibliography.html

[Dan Catana]

Hello,
I have bumped into your site while seeking for software and found your 
website very interesting :)
Just a quick note, http://www.cdrom.com/is no longer active, and 
you are linking to it from page - 
http://docs.lvl.ru/handbook/bibliography.html
I was wondering if you don't mind updating the link to the updated 
websitehttp://en.downloadastro.com - A 
great download site with more than 300K software and games, including 
professional reviews and user ratings.
We are now in a process of updating the links in websites all around the 
world and I will appreciate your cooperation.

I am sure your *users will find it useful**.*
Thanks,
Dan
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"

Re: docs/178221: Addition to handbook jails chapter: warning about make deinstall

[Brandon Thomson]

The following reply was made to PR docs/178221; it has been noted by GNATS.

From: Brandon Thomson 
To: freebsd-gnats-sub...@freebsd.org
Cc:  
Subject: Re: docs/178221: Addition to handbook jails chapter: warning about
 make deinstall
Date: Thu, 2 May 2013 04:48:04 +

 >>When setting up a machine according to the "Application of Jails"
 >>section of FreeBSD Handbook [1], one runs into a problem where "make
 >>deinstall" inside of a jail does not work as expected. There is a
 >>workaround, which probably should be noted in the chapter.
 >>
 >>Note that this only applies to ports installed in a jail. Ports
 >>installed on the base system do not need the workaround.
 >>
 >>[1] http://www.freebsd.org/doc/handbook/jails-application.html
 >>
 >>Original thread [2]: http://forums.freebsd.org/showthread.php?p=213757
 >>
 >>The workaround is to use "make deinstall PREFIX=/s/usr-local", where
 >>/s/usr-local is whatever make spits out when you type make
 >>deinstall. If you followed the handbook instructions exactly it will
 >>be /s/usr-local.
 
 >If you're actually running *inside* the jail, you shouldn't see that
 >prefix.
 
 Do you mean the directory /s/usr-local should not be visible inside the jail?
 On the jails I have set up it is, and I believe that is in accord with the
 instructions in [1].
 
 For example if /s/usr-local were not visible inside the jail, the symlink at
 /usr/local pointing to ../s/usr-local would be a broken link.
 
 So, I think the PREFIX of /s/usr-local *should* be visible inside the jail.
 
 >Where you need to run the command that way is if you're using the parent
 >system to update the port that the jail runs. But then your "make
 >install" process is not actually *in* the jail at all.
 
 I did not attempt to deinstall a port run by the jail from the parent system.
 My attempt was from inside the jail environment, using jexec.
 
 I agree that one would *also* need to adjust the PREFIX if one wanted to
 deinstall a port in the jail from the parent system. In this case, the PREFIX
 would need to be set to /usr/jails/s/myjail/usr-local or similar.
 
 However, the point of this issue is that PREFIX also needs to be set when
 running "make deinstall" *inside* the jail environment. If you don't set 
PREFIX,
 you will run into the error described in [2].
 
 Note that the host's /usr/jails/s/myjail should be mounted to /s inside the
 jail, so the PREFIX inside the jail is: /s/usr-local.
 
 Hope that makes sense! Jail paths can be really confusing :(
 
 I suppose it's also possible that both myself and the original poster in [2]
 have failed to follow the instructions in [1] correctly in some way that is
 causing this issue to arise, but that seems unlikely to me.
 
 Warm regards,
 Brandon
 
___
freebsd-doc@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-doc
To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"