Re: make.conf Question
On 22/01/06, Adam Stroud [EMAIL PROTECTED] wrote: All: I have been playing around with make.conf and I see that it is possible to to use the NO_OPENSSH variable to not build openssh when updating fbsd from source. I also noticed in the /etc/defaults/rc.conf file that there is a sshd_program entry that can be used to adjust where the installation of sshd is. I am assuming that this means that I can install openssh from the ports exclusively and use the rc.conf file to launch the ports sshd on startup. Here are my questions about this: 1. Is my assumption correct? 2. Does this also apply to things like kerberos and openssl 3. Does this impose any notable side effects to the system (possibly with stability/security)? Thanks A ___ Yes it should be fine I use it but I keep kerberos and openssl base enabled since it is used by various things within the base system, make sure prior to doing this if you are remote administrating the system you already have the ports version of openssh installed enabled and configured. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make.conf Question
All: I have been playing around with make.conf and I see that it is possible to to use the NO_OPENSSH variable to not build openssh when updating fbsd from source. I also noticed in the /etc/defaults/rc.conf file that there is a sshd_program entry that can be used to adjust where the installation of sshd is. I am assuming that this means that I can install openssh from the ports exclusively and use the rc.conf file to launch the ports sshd on startup. Here are my questions about this: 1. Is my assumption correct? 2. Does this also apply to things like kerberos and openssl 3. Does this impose any notable side effects to the system (possibly with stability/security)? Thanks A ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf Question
On Jan 21, 2006, at 4:54 PM, Adam Stroud wrote: All: I have been playing around with make.conf and I see that it is possible to to use the NO_OPENSSH variable to not build openssh when updating fbsd from source. I also noticed in the /etc/defaults/rc.conf file that there is a sshd_program entry that can be used to adjust where the installation of sshd is. I am assuming that this means that I can install openssh from the ports exclusively and use the rc.conf file to launch the ports sshd on startup. Here are my questions about this: 1. Is my assumption correct? 2. Does this also apply to things like kerberos and openssl 3. Does this impose any notable side effects to the system (possibly with stability/security)? Thanks A According to man make.conf, NO_OPENSSH is the variable which defines whether or not to build OpenSSH. This doesn't have anything to do with fetching OpenSSH. NO_OPENSSL=yes implies NO_KERBEROS=yes and NO_OPENSSH=yes, since both things depend upon the existence of Openssl. However, I highly suggest that you keep OpenSSL since it's important for most software on various levels (ie how can you go online to certain websites and login if you don't have SSL support?!). Read man make.conf for more info on some of the variables that you can define for your system via make.conf. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make.conf - question
Hello, where can I found ALL parameters suited for /etc/make.conf ? For example, I wanted install some software from ports without X11, but man 5 make.conf doesn`t include WITHOUT_X11 option. Fortunatelly I found this page http://www.gsp.com/cgi-bin/man.cgi?section=5topic=make.conf and included some necessary parameters into my make.conf. Ok, I found this --- man make.conf --- The purpose of make.conf is not to run commands or perform compilation actions directly. Instead, it is included by the various makefiles in /usr/src, /usr/ports and /usr/doc which conditionalize their internal actions according to the settings found there. --- cut --- in man page, but im not sure where exactly should I look ? (OS: 5.4-RELEASE FreeBSD 5.4-RELEASE ) Thank you, Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf - question
On 10/31/05, Vladimir Dvorak [EMAIL PROTECTED] wrote: Hello, where can I found ALL parameters suited for /etc/make.conf ? For example, I wanted install some software from ports without X11, but man 5 make.conf doesn`t include WITHOUT_X11 option. Fortunatelly I found this page http://www.gsp.com/cgi-bin/man.cgi?section=5topic=make.conf and included some necessary parameters into my make.conf. Ok, I found this --- man make.conf --- The purpose of make.conf is not to run commands or perform compilation actions directly. Instead, it is included by the various makefiles in /usr/src, /usr/ports and /usr/doc which conditionalize their internal actions according to the settings found there. --- cut --- in man page, but im not sure where exactly should I look ? (OS: 5.4-RELEASE FreeBSD 5.4-RELEASE ) Thank you, Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] You can only find *most* of parameters by reading system mk files carefully. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf - question
At 01:53 AM 10/31/2005, Vladimir Dvorak wrote: Hello, where can I found ALL parameters suited for /etc/make.conf ? For example, I wanted install some software from ports without X11, but man 5 make.conf doesn`t include WITHOUT_X11 option. Fortunatelly I found this page http://www.gsp.com/cgi-bin/man.cgi?section=5topic=make.conf and included some necessary parameters into my make.conf. Ok, I found this --- man make.conf --- The purpose of make.conf is not to run commands or perform compilation actions directly. Instead, it is included by the various makefiles in /usr/src, /usr/ports and /usr/doc which conditionalize their internal actions according to the settings found there. --- cut --- in man page, but im not sure where exactly should I look ? As stated above, make.conf applies to building things in /usr/src /usr/ports and /usr/doc. Anything you can control with environment variables when building in those dirs can be added to make.conf. If you're looking for general settings that can be changed in ports for example, you'll find info in the ports(7) man page. Additionally, individual ports my have additional settings. -Glenn (OS: 5.4-RELEASE FreeBSD 5.4-RELEASE ) Thank you, Vladimir ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Mon, 11 Apr 2005, Kris Kennaway [EMAIL PROTECTED] wrote: On Mon, Apr 11, 2005 at 02:05:00PM +0200, Piotr Gnyp wrote: # certain code (currently only OpenSSL) as well as modifying the value ^^ It does exactly what it says it does. What is your confusion? My mistake, didn`t read it carefully ; Sorry. -- How fortunate the man with none. --Dead Can Dance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make.conf question
Hi. My 4.11 boxes: uname -r 4.11-RELEASE-p1 CPU: 1. CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.30-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE, SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs 2. CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2798.66-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE make.conf: CPUTYPE=p4 During build i can see: -march=pentiumpro instead of pentium4. On my 5.3 box everything works great. Is this setting not working on FreeBSD 4.x? Or maybe i should set it somewhere else also. -- How fortunate the man with none. --Dead Can Dance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Mon, Apr 11, 2005 at 11:27:22AM +0200, Piotr Gnyp wrote: Hi. My 4.11 boxes: uname -r 4.11-RELEASE-p1 CPU: 1. CPU: Intel(R) Xeon(TM) CPU 2.40GHz (2392.30-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf27 Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE, SSE2,SS,HTT,TM,PBE Hyperthreading: 2 logical CPUs 2. CPU: Intel(R) Pentium(R) 4 CPU 2.80GHz (2798.66-MHz 686-class CPU) Origin = GenuineIntel Id = 0xf29 Stepping = 9 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE make.conf: CPUTYPE=p4 During build i can see: -march=pentiumpro instead of pentium4. On my 5.3 box everything works great. Is this setting not working on FreeBSD 4.x? Or maybe i should set it somewhere else also. The version of gcc that comes with FreeBSD 4.x can't do better than this, i.e. it doesn't know about optimizations for newer CPUs. In practise this isn't important. Kris pgpczl5kyf0Yo.pgp Description: PGP signature
Re: make.conf question
On Mon, 11 Apr 2005, Kris Kennaway [EMAIL PROTECTED] wrote: The version of gcc that comes with FreeBSD 4.x can't do better than this, i.e. it doesn't know about optimizations for newer CPUs. In practise this isn't important. Ok, so why this: # The CPUTYPE variable controls which processor should be targeted for # generated code. This controls processor-specific optimizations in # certain code (currently only OpenSSL) as well as modifying the value # of CFLAGS to contain the appropriate optimization directive to gcc. # The automatic setting of CFLAGS may be overridden using the # NO_CPU_CFLAGS variable below. # Currently the following CPU types are recognized: # Intel x86 architecture: # (AMD CPUs) k7 k6-2 k6 k5 # (Intel CPUs)p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 # # If you experience any problems after setting this flag, please unset # it again before submitting a bug report or attempting to modify code. # It may be that certain types of software will become unstable after being # compiled with processor-specific (or higher - see below) optimization flags. # If in doubt, do not set CPUTYPE or CFLAGS to non-default values. # #CPUTYPE=i686 is in /etc/defaults/make.conf in 4.x? -- How fortunate the man with none. --Dead Can Dance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Mon, Apr 11, 2005 at 02:05:00PM +0200, Piotr Gnyp wrote: # The CPUTYPE variable controls which processor should be targeted for # generated code. This controls processor-specific optimizations in # certain code (currently only OpenSSL) as well as modifying the value # of CFLAGS to contain the appropriate optimization directive to gcc. # The automatic setting of CFLAGS may be overridden using the # NO_CPU_CFLAGS variable below. # Currently the following CPU types are recognized: # Intel x86 architecture: # (AMD CPUs) k7 k6-2 k6 k5 # (Intel CPUs)p4 p3 p2 i686 i586/mmx i586 i486 i386 # Alpha/AXP architecture: ev6 pca56 ev56 ev5 ev45 ev4 is in /etc/defaults/make.conf in 4.x? It does exactly what it says it does. What is your confusion? Kris pgpUXuoMohHtG.pgp Description: PGP signature
make.conf question
I have a P4 2.4G Intel proc on an Asus P4S533 motherboard running FreeBSD 5.1-RELEASE-p17. /usr/src/sys/conf/newvers.sh is showing Release now and not RC1 so I thought I'd give it a shot. I'm trying to figure out what are the best/appropriate flags to use in /etc/make.conf I had the following; CPUTYPE=p4 CFLAGS= -O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized but after running make buildworld it crashed on the (-fmemoize-lookups -fsave-memoized) flags so I commented them and I'm rerunning make buildworld (stupid me, I didn't copy the error when it failed). So far there have been no errors. How does one know what flags to use in /etc/make.conf? I thought I had the right ones. Regards, Mark -- NetAdmin for the FoxChat.Net IRC Network. The FoxSurfer Group signature.asc Description: This is a digitally signed message part
Re: make.conf question
make.conf(5) has some info for you Michael On Oct 24, 2004, at 2:30 PM, NetAdmin wrote: I have a P4 2.4G Intel proc on an Asus P4S533 motherboard running FreeBSD 5.1-RELEASE-p17. /usr/src/sys/conf/newvers.sh is showing Release now and not RC1 so I thought I'd give it a shot. I'm trying to figure out what are the best/appropriate flags to use in /etc/make.conf I had the following; CPUTYPE=p4 CFLAGS= -O -pipe CXXFLAGS+= -fmemoize-lookups -fsave-memoized but after running make buildworld it crashed on the (-fmemoize-lookups -fsave-memoized) flags so I commented them and I'm rerunning make buildworld (stupid me, I didn't copy the error when it failed). So far there have been no errors. How does one know what flags to use in /etc/make.conf? I thought I had the right ones. Regards, Mark -- NetAdmin for the FoxChat.Net IRC Network. The FoxSurfer Group ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Sun, 24 Oct 2004 14:30:51 -0400, NetAdmin [EMAIL PROTECTED] wrote: snip How does one know what flags to use in /etc/make.conf? I thought I had the right ones. The right one is very much relative to the user and the purpose of the system. For example on a development system I would enable CFLAGS=-O3 and try to figure out what goes wrong if something fails to work. On a the other hand I would never go over CFLAGS=-O on a production box. /etc/defaults/make.conf and man make.conf prove to be very good resources. Regards S. -- Subhro Sankha Kar School of Information Technology Block AQ-13/1 Sector V ZIP 700091 India ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make.conf question
Hi! 1) Can I put any make option into make.conf that can be applied to ports (like inmake WITH_CALENDAR=yes install clean) or is this restricted to system ressources? 2) If yes - would this be advisable? - Or is there a big chance to produce some sort of mess? 3) Is make.conf also applied to gmake (used by many ports)? Thanks, Uli. +---+ |Peter Ulrich Kruppa| | Wuppertal | | Germany | +---+ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Tue, 26 Aug 2003 10:41:34 + (UTC) in lucky.freebsd.questions, Peter Ulrich
Kruppa [EMAIL PROTECTED] wrote:
Hi!
1) Can I put any make option into make.conf that can be applied
to ports (like inmake WITH_CALENDAR=yes install clean)
or is this restricted to system ressources?
2) If yes - would this be advisable? - Or is there a big chance
to produce some sort of mess?
I use following in /etc/make.conf:
.if ${.CURDIR:N*/ports/news/tin} ==
WITH_TIN_NNTP_ONLY=yes
#WITH_TIN_METAMAIL=yes
WITH_TIN_ISPELL=yes
.endif
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make.conf question
On Tue, Aug 26, 2003 at 12:54:25PM +0200, Peter Ulrich Kruppa [EMAIL PROTECTED] wrote: 1) Can I put any make option into make.conf that can be applied to ports (like in make WITH_CALENDAR=yes install clean) or is this restricted to system ressources? Yes, you can put ports specific options into /etc/make.conf You can also put a Makefile.inc into a specific port directory which will be read in automatically -- I think there are a few ports that may happen to overwrite that file, but they are few and far between. See also /usr/local/etc/pkgtools.conf if you're a portupgrade(1) user. 2) If yes - would this be advisable? - Or is there a big chance to produce some sort of mess? No, this is what /etc/make.conf is designed to do. Generally it will work well, but occasional problems creep in. Eg. if you put: A4=YES into /etc/make.conf at the moment, then I believe that triggers a bug in the print/ghostscript-gnu port which makes the build fall over at unexpected moments (ports/54848). Slightly inconvenient for the large chunk of the world that uses metric paper sizes. 3) Is make.conf also applied to gmake (used by many ports)? No, /etc/make.conf won't be read in by *any* of the Makefiles (gmake or otherwise) that come with the source code of the port. It's only used by the Makefiles in the port directory, and it's up to them to run the port's configure script with the required options or to apply patches to the source code or do whatever else is required to achive the desired result as indicated by the make options. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
