f17c Anyone use /etc/make.conf ? - The FreeBSD Forums
The FreeBSD Forums  

Go Back   The FreeBSD Forums > Base System > General
Reload this Page Anyone use /etc/make.conf ?
Register FAQ Calendar Search Today's Posts Mark Forums Read

General General questions about the FreeBSD operating system. Ask here if your question does not fit elsewhere.

Reply
 
Thread Tools Display Modes
  #1  
Old April 16th, 2009, 07:41
johnblue johnblue is offline
Member
  
Join Date: Jan 2009
Location: O-o-o-o-o-o-o-klahoma
Posts: 176
Thanks: 11
Thanked 17 Times in 15 Posts
Default Anyone use /etc/make.conf ?
What are some default options that you would set in /etc/make.conf for a fresh install?
Reply With Quote
  #2  
Old April 16th, 2009, 07:47
vermaden's Avatar
vermaden vermaden is offline
Giant Locked
  
Join Date: Nov 2008
Location: pl_PL.lodz
Posts: 2,191
Thanks: 59
Thanked 632 Times in 349 Posts
Default
Like that one for example:
http://toya.net.pl/~vermaden/text/make.conf
__________________
Religions, worst damnation of mankind.
"FreeBSD has always been the operating system that GNU/Linux should have been." Frank Pohlmann, IBM
http://vermaden.blogspot.com
Reply With Quote
The Following User Says Thank You to vermaden For This Useful Post:
gnemmi (April 20th, 2009)
  #3  
Old April 16th, 2009, 08:48
ctaranotte ctaranotte is offline
Junior Member
  
Join Date: Nov 2008
Posts: 85
Thanks: 3
Thanked 16 Times in 9 Posts
Default
And if you are building world for a jail only (and not for your host), the one below might be useful:

Code:
NO_ACPI=       true    # do not build acpiconf(8) and related programs
NO_BOOT=       true    # do not build boot blocks and loader
NO_BLUETOOTH=  true    # do not build Bluetooth related stuff
NO_FORTRAN=    true    # do not build g77 and related libraries
NO_GDB=        true    # do not build GDB
NO_GPIB=       true    # do not build GPIB support
NO_I4B=        true    # do not build isdn4bsd package
NO_IPFILTER=   true    # do not build IP Filter package
NO_PF=         true    # do not build PF firewall package
NO_AUTHPF=     true    # do not build and install authpf (setuid/gid)
NO_KERBEROS=   true    # do not build and install Kerberos 5 (KTH Heimdal)
NO_LPR=        true    # do not build lpr and related programs
NO_MAILWRAPPER=true    # do not build the mailwrapper(8) MTA selector
NO_MODULES=    true    # do not build modules with the kernel
NO_NETCAT=     true    # do not build netcat
NO_NIS=        true    # do not build NIS support and related programs
NO_SENDMAIL=   true    # do not build sendmail and related programs
NO_SHAREDOCS=  true    # do not build the 4.4BSD legacy docs
NO_USB=        true    # do not build usbd(8) and related programs
NO_VINUM=      true    # do not build Vinum utilities
NO_ATM=        true    # do not build ATM related programs and libraries
NO_CRYPT=      true    # do not build any crypto code
NO_GAMES=      true    # do not build games (games/ subdir)
NO_INFO=       true    # do not make or install info files
NO_MAN=        true    # do not build manual pages
NO_PROFILE=    true    # Avoid compiling profiled libraries

# BIND OPTIONS
NO_BIND=               true    # Do not build any part of BIND
NO_BIND_DNSSEC=        true    # Do not build dnssec-keygen, dnssec-signzone
NO_BIND_ETC=           true    # Do not install files to /etc/namedb
NO_BIND_LIBS_LWRES=    true    # Do not install the lwres library
NO_BIND_MTREE=         true    # Do not run mtree to create chroot directories
NO_BIND_NAMED=         true    # Do not build named, rndc, lwresd, etc.
This is taken from Creating a FreeBSD Jail
Reply With Quote
  #4  
Old April 16th, 2009, 09:58
DutchDaemon's Avatar
DutchDaemon DutchDaemon is offline
Administrator
  
Join Date: Nov 2008
Location: Rotterdam, the Netherlands
Posts: 9,823
Thanks: 30
Thanked 1,884 Times in 1,330 Posts
Default
Don't confuse make.conf(5) and src.conf(5).

make.conf:
Code:
The primary purpose of make.conf is to control the compilation of the
     FreeBSD sources, documentation, and ported applications, which are usu-
     ally found in /usr/src, /usr/doc, and /usr/ports.  As a rule, the system
     administrator creates make.conf when the values of certain control vari-
     ables need to be changed from their defaults.
src.conf:
Code:
The only purpose of src.conf is to control the compilation of the FreeBSD
     source code, which is usually located in /usr/src.  As a rule, the system
     administrator creates src.conf when the values of certain control vari-
     ables need to be changed from their defaults.
If you're looking for a way not to build stuff with the base system (e.g. WITHOUT_INET6), use src.conf.
__________________
FreeBSD Forums: Information for New Members | FreeBSD Forums Rules
FreeBSD Resources: The FreeBSD Handbook | Manuals | FAQ | Wiki
Before you post: How to ask questions the smart way
If you must know .. So, what does an Adminstrator/Moderator do?
---> Do not PM me with FreeBSD questions. I do not work here. <---
Reply With Quote
The Following User Says Thank You to DutchDaemon For This Useful Post:
garrych (August 16th, 2011)
  #5  
Old April 16th, 2009, 11:17
SirDice's Avatar
SirDice SirDice is offline
Moderator
  
Join Date: Nov 2008
Location: Rotterdam, Netherlands
Posts: 13,694
Thanks: 47
Thanked 2,021 Times in 1,860 Posts
Default
The only options I have in make.conf are:
Code:
KERNCONF=MOLLY

OVERRIDE_LINUX_BASE_PORT=f8
OVERRIDE_LINUX_NONBASE_PORTS=f8

WITH_GECKO=libxul
Reply With Quote
  #6  
Old April 16th, 2009, 14:37
Mel_Flynn Mel_Flynn is offline
Member
  
Join Date: Nov 2008
Location: Drachten, Netherlands
Posts: 379
Thanks: 7
Thanked 74 Times in 57 Posts
Default
Quote:
Originally Posted by DutchDaemon View Post
src.conf:
Code:
The only purpose of src.conf is to control the compilation of the FreeBSD
     source code, which is usually located in /usr/src.  As a rule, the system
     administrator creates src.conf when the values of certain control vari-
     ables need to be changed from their defaults.
If you're looking for a way not to build stuff with the base system (e.g. WITHOUT_INET6), use src.conf.
Actually, src.conf is turned off by ports, but anyone using /usr/share/mk/* files other then *.ports.* is subject to src.conf and everything built by make(1) is subject to make.conf. This can create surprises for example when you set WITH_OPENLDAP=yes in /etc/make.conf, as krb5 (in /usr/src) will then be built with ldap support as well.
It's therefore best to wrap port specific settings like so:
Code:
.if !empty(.CURDIR:M/usr/ports/*)
# settings go here
.endif
Especially CFLAGS and related.
__________________
The core concept of freedom is the lack of rules, even those made to "protect freedom".
Last edited by Mel_Flynn; April 16th, 2009 at 14:38. Reason: Specify krb5 in /usr/src
Reply With Quote
The Following User Says Thank You to Mel_Flynn For This Useful Post:
gnemmi (April 20th, 2009)
Reply

« Previous Thread | Next Thread »
Thread Tools
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[Solved] upgrade 7.0 to 7.1 problem with rc.conf rdunkle Installing & Upgrading 2 April 6th, 2009 13:26
Problem with login.conf Markand General 12 February 28th, 2009 07:41
sysctl.conf lumiwa General 5 January 11th, 2009 03:31
What different tuning from kernel, sysctl.conf, rc.conf and loader.conf? darkstar General 3 November 24th, 2008 11:48
1.0GHz VIA C7® Processor... make.conf... holo System Hardware 3 November 21st, 2008 19:57


All times are GMT +1. The time now is 21:56.

Contact Us - FreeBSD - Archive - Top

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2013, vBulletin Solutions, Inc.
The mark FreeBSD is a registered trademark of The FreeBSD Foundation and is used by The FreeBSD Project with the permission of The FreeBSD Foundation.
Web protection and acceleration provided by CloudFlare
0