Re: make.conf

2017-03-07 Thread Roberto Rodriguez Jr
Yes I understand it's true there are many options I will test what I can for my AMD 64 machine since it's a laptop I can probably start making some reports and also look into ZFS snapshots and tunables. Thank you very much it was helpful ___ freebsd-curre

Re: make.conf

2017-03-07 Thread Roberto Fernández
Good morning Roberto, It depends which architecture are you currently using. Ideally the tests should be run in each CPU type for each architecture and for each combination of options in the make.conf, src.conf and src-env.conf. That could last for ever. Feel free to test whatever you can. For ins

Re: make.conf and MASTER_SITE_BACKUP

2003-06-23 Thread Simon L. Nielsen
On 2003.06.23 19:42:25 +0200, Byron Schlemmer wrote: > Had a quick search around mail archives and problem reports. Did spot > anything, but it seems > > MASTER_SITE_BACKUP?= > MASTER_SITE_OVERRIDE?= > > work in make.conf for 5 however make.conf(5) doesn't seem to mention it? > Is this a featur

Re: make.conf and make.conf(5)

2002-11-26 Thread Tom Rhodes
I'll look into this ;) -- Tom Rhodes On Tue, 26 Nov 2002 10:44:29 +1100 (EST) Andy Farkas <[EMAIL PROTECTED]> wrote: > On Tue, 19 Nov 2002, Carl Schmidt wrote: > > > The following PR has two patches attached which address the lack of > > some documentation of make.conf in the manual page. It a

Re: make.conf and make.conf(5)

2002-11-25 Thread Andy Farkas
On Tue, 19 Nov 2002, Carl Schmidt wrote: > The following PR has two patches attached which address the lack of some > documentation of make.conf in the manual page. It also contains a patch > for make.conf to fix style inconsistencies and two (if I recall > correctly) items which are documented i

Re: make.conf and make.conf(5)

2002-11-20 Thread Carl Schmidt
On Wed, Nov 20, 2002 at 03:37:32PM -0500, Tom Rhodes wrote: > On Wed, 20 Nov 2002 10:10:14 -0500 > Carl Schmidt <[EMAIL PROTECTED]> wrote: > > > On Wed, Nov 20, 2002 at 09:53:35AM -0500, Tom Rhodes wrote: > > > On Wed, 20 Nov 2002 12:09:14 +0200 > > > Sheldon Hearn <[EMAIL PROTECTED]> wrote: > > >

Re: make.conf and make.conf(5)

2002-11-20 Thread Tom Rhodes
On Wed, 20 Nov 2002 10:10:14 -0500 Carl Schmidt <[EMAIL PROTECTED]> wrote: > On Wed, Nov 20, 2002 at 09:53:35AM -0500, Tom Rhodes wrote: > > On Wed, 20 Nov 2002 12:09:14 +0200 > > Sheldon Hearn <[EMAIL PROTECTED]> wrote: > > > On (2002/11/19 15:17), Carl Schmidt wrote: > > > > > > > The following

Re: make.conf and make.conf(5)

2002-11-20 Thread Carl Schmidt
On Wed, Nov 20, 2002 at 09:53:35AM -0500, Tom Rhodes wrote: > On Wed, 20 Nov 2002 12:09:14 +0200 > Sheldon Hearn <[EMAIL PROTECTED]> wrote: > > On (2002/11/19 15:17), Carl Schmidt wrote: > > > > > The following PR has two patches attached which address the lack of > > > some documentation of make.

Re: make.conf and make.conf(5)

2002-11-20 Thread Tom Rhodes
On Wed, 20 Nov 2002 12:09:14 +0200 Sheldon Hearn <[EMAIL PROTECTED]> wrote: > On (2002/11/19 15:17), Carl Schmidt wrote: > > > The following PR has two patches attached which address the lack of > > some documentation of make.conf in the manual page. It also > > contains a patch for make.conf to

Re: make.conf and make.conf(5)

2002-11-20 Thread Sheldon Hearn
On (2002/11/19 15:17), Carl Schmidt wrote: > The following PR has two patches attached which address the lack of some > documentation of make.conf in the manual page. It also contains a patch > for make.conf to fix style inconsistencies and two (if I recall > correctly) items which are documented

Re: make.conf and -CURRENT

2002-05-13 Thread Sheldon Hearn
On Fri, 10 May 2002 17:46:31 EST, "David W. Chapman Jr." wrote: > > sysctl.conf is also missing. If its not there, it doesn't get > > parsed. You only need make.conf if you wish to put stuff in there. > > same with rc.conf, except everyone puts something in rc.conf > > > N/m on the sysctl

Re: make.conf and -CURRENT

2002-05-10 Thread David W. Chapman Jr.
On Fri, May 10, 2002 at 05:40:11PM -0500, David W. Chapman Jr. wrote: > On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: > > Hello, > > > > Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps > > something that I have messed up on my end? > > I have run cvsup/merg

Re: make.conf and -CURRENT

2002-05-10 Thread Brooks Davis
On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: > Hello, > > Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps > something that I have messed up on my end? > I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that > changes nothing. /usr/src/etc/*/* d

Re: make.conf and -CURRENT

2002-05-10 Thread David W. Chapman Jr.
On Fri, May 10, 2002 at 06:37:11PM -0400, Jeff Ito wrote: > Hello, > > Is the lack of /etc/defaults/make.conf intentional? an oversite? or perhaps > something that I have messed up on my end? > I have run cvsup/mergemaster (18:30PM EST May 10. 2002), and that > changes nothing. /usr/src/etc/*/* d

Re: make.conf not in -current tree (was cvs commit: src/include stdio.h)

2001-09-21 Thread Alexander Langer
Thus spake Ruslan Ermilov ([EMAIL PROTECTED]): > IIRC, it was requested by many that this change be backed out, no? No, the discussion -arch converted to a discussion about the implementation of a "world.conf" file, which implicits this commit. Alex To Unsubscribe: send mail to [EMAIL PROTECTE

Re: make.conf not in -current tree (was cvs commit: src/include stdio.h)

2001-09-20 Thread Ruslan Ermilov
On Thu, Sep 20, 2001 at 09:26:13PM +0200, Alexander Langer wrote: > Thus spake Vincent Poy ([EMAIL PROTECTED]): > > > I was looking on the -current tree and don't see make.conf in > > either etc or etc/defaults. In previous versions, make.conf is in > > etc/defaults and then you can put your

Re: make.conf not in -current tree (was cvs commit: src/includestdio.h)

2001-09-20 Thread Vincent Poy
On Thu, 20 Sep 2001, Alexander Langer wrote: > Thus spake Vincent Poy ([EMAIL PROTECTED]): > > > I was looking on the -current tree and don't see make.conf in > > either etc or etc/defaults. In previous versions, make.conf is in > > etc/defaults and then you can put your own modifications in

Re: make.conf not in -current tree (was cvs commit: src/include stdio.h)

2001-09-20 Thread Alexander Langer
Thus spake Vincent Poy ([EMAIL PROTECTED]): > I was looking on the -current tree and don't see make.conf in > either etc or etc/defaults. In previous versions, make.conf is in > etc/defaults and then you can put your own modifications in etc. So any > chance of bringing back make.conf int

Re: make.conf INSTALL knob

2001-04-25 Thread Bruce Evans
On Wed, 25 Apr 2001, Eric D. Futch wrote: > I originally sent this to freebsd-stable but didn't get any replies. It > has been reworded. > > I ran across this while playing with the INSTALL knob in make.conf. In > almost all of the Makefiles in src/ there is either -C or -c hard coded as > an

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-12 Thread Bruce Evans
On Mon, 12 Mar 2001, Kris Kennaway wrote: > On Tue, Mar 13, 2001 at 05:32:36AM +1100, Bruce Evans wrote: > > OTOH, bsd.cpu.mk is too under-engineered to support any compiler except > > gcc. It unconditionally translates FreeBSD-specific names like k6-2 to > > gcc-specific flags like -march=k6. >

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-12 Thread Kris Kennaway
On Tue, Mar 13, 2001 at 05:32:36AM +1100, Bruce Evans wrote: > k6-2 is already over-engineered. The only difference between it and k6 > is 3dnow, but neither gcc nor any source files support 3dnow (now :-). 3dnow support exists in several ports, though. OTOH, k6-3 doesn't add any new features,

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-12 Thread David O'Brien
On Tue, Mar 13, 2001 at 05:32:36AM +1100, Bruce Evans wrote: > k6-2 is already over-engineered. The only difference between it and k6 > is 3dnow, but neither gcc nor any source files support 3dnow (now :-). Binutils 2.11.0 and GCC 3.0 will. :-) > OTOH, bsd.cpu.mk is too under-engineered to supp

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-12 Thread Bruce Evans
On Mon, 12 Mar 2001, Maxim Sobolev wrote: > Maxim Sobolev wrote: > > > On Mon, Mar 12, 2001 at 12:29:58AM -0300, Mario Sergio Fujikawa Ferreira wr= > > > ote: > > > > Hi, > > > >=20 > > > > Is there anything against adding support for > > > > k6-3 to the just added CPUTYPE mechanism? :) > > >

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-11 Thread Maxim Sobolev
Maxim Sobolev wrote: > > > > > > --AhhlLboLdkugWU4S > > Content-Type: text/plain; charset=us-ascii > > Content-Disposition: inline > > Content-Transfer-Encoding: quoted-printable > > > > On Mon, Mar 12, 2001 at 12:29:58AM -0300, Mario Sergio Fujikawa Ferreira wr= > > ote: > > > Hi, > > >=20 > > >

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-11 Thread Maxim Sobolev
> > > --AhhlLboLdkugWU4S > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Mon, Mar 12, 2001 at 12:29:58AM -0300, Mario Sergio Fujikawa Ferreira wr= > ote: > > Hi, > >=20 > > Is there anything against adding suppo

Re: make.conf lack of CPUTYPE=k6-3 support

2001-03-11 Thread Kris Kennaway
On Mon, Mar 12, 2001 at 12:29:58AM -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > Is there anything against adding support for > k6-3 to the just added CPUTYPE mechanism? :) > My little machine feels left out. Hehehhe > I made a simple patch to etc/defaults/make.conf > a

Re: make.conf fix

2000-06-21 Thread Will Andrews
On Wed, Jun 21, 2000 at 12:09:02AM -0700, Satoshi - Ports Wraith - Asami wrote: > Waitaminit. These are correct, please look at bsd.sites.mk. What > makes you think they are not working? Hmm... weird. I tried using the overrides in make.conf some time ago and they didn't work and I had to use

Re: make.conf fix

2000-06-21 Thread Satoshi - Ports Wraith - Asami
* From: Will Andrews <[EMAIL PROTECTED]> * Hi -current and -ports, * * I've noticed something that seems to have been broken for a long time. * In etc/defaults/make.conf we have several MASTER_SITE_* variables which * reference "%SUBDIR%". However, these variables do not work as expected.

Re: make.conf NO_SENDMAIL=true blown

2000-01-05 Thread Randy Bush
>> but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq, >> etc. all about /usr/sbin/mailwrapper. > Yeah, that bit me too but I forgot to post a message here. I'm using > postfix and I just changed /etc/mail/mailer.conf to this: > > sendmail/usr/local/sbin/sendmail >

Re: make.conf NO_SENDMAIL=true blown

2000-01-05 Thread Chris Piazza
On Wed, Jan 05, 2000 at 04:27:26PM -0800, Randy Bush wrote: > my /etc/make.conf has NO_SENDMAIL=true > > but current as of today is stomping on /usr/sbin/sendmail, /usr/bin/mailq, > etc. all about /usr/sbin/mailwrapper. Yeah, that bit me too but I forgot to post a message here. I'm using postfi

Re: make.conf options (was Re: package-like feature for the basedistrib (was Re: FreeSSH))

1999-10-17 Thread Mike Meyer
On Sun, 17 Oct 1999, Garrett Wollman wrote: ;->< said: ;-> ;->> This is going in the right direction, but here is a question (and I don't ;->> have the answer). Is it so much more easier to create new compile time ;->> directive than to go the extra step and use packages where they are ;->> avail

Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH))

1999-10-17 Thread Garrett Wollman
< said: > This is going in the right direction, but here is a question (and I don't > have the answer). Is it so much more easier to create new compile time > directive than to go the extra step and use packages where they are > available ? For example "bind8" is available as a package. Why not h

Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH))

1999-10-17 Thread Patrick Bihan-Faou
Hi, From: Cy Schubert - ITSD Open Systems Group <[EMAIL PROTECTED]> > > I was not talking about things that constitute the "real" core of the > > distribution (kernel, basic libraries etc.). I was more thinking about > > "userland" stuff that is included in the distribution but might not be > > r

Re: make.conf options (was Re: package-like feature for the base distrib (was Re: FreeSSH))

1999-10-16 Thread Cy Schubert - ITSD Open Systems Group
In message <011801bf159c$f80630e0$[EMAIL PROTECTED]>, "Patrick Bihan- Faou" writes: > Hi, > > From: Pierre Beyssac <[EMAIL PROTECTED]> > > > There are a _lot_ of pitfalls to this kind of approach, as I have > > discovered using Linux Debian. This would probably open a can of > > worms you have n

Re: make.conf on CURRENT question

1999-07-29 Thread Dag-Erling Smorgrav
Peter Jeremy <[EMAIL PROTECTED]> writes: > You'll also need the a.out X11 libraries, and last time I tried, > they built OK, but wouldn't work. They build OK and work fine. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: make.conf on CURRENT question

1999-07-28 Thread Peter Jeremy
"Scot W. Hetzel" <[EMAIL PROTECTED]> wrote: >You'll also want to use: > >make world -DWANT_AOUT=YES > >to have the a.out libraries built. You'll also need the a.out X11 libraries, and last time I tried, they built OK, but wouldn't work. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with

Re: make.conf on CURRENT question

1999-07-28 Thread Scot W. Hetzel
From: Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> > compat22=yes in /etc/make.conf accomplishes a.out support which we need > for netscape support. Correct? > You will also need a.out libraries from XFree86 in order to get Netscape working. > What does compat3x do however? Provide ELF compatibilit