: Notes and patches against 7-CURRENT are at
: http://www.gsicomp.on.ca/projects/freebsd/configdep.html.
How would you encode ed's dependencies? The ed driver only depends on
mii when built with pccard enabled.
Warner
___
freebsd-hackers@freebsd.org ma
On Fri, Jan 20, 2006 at 08:36:17PM -0500, Sergey Babkin wrote:
> > If (as I said) you impose the correct dependency information.
> > Currently there is no such information provided.
>
> Ah, so we don't have any reliable information about dependencies
> between the ports either (not just between
Kris Kennaway wrote:
>
> On Fri, Jan 20, 2006 at 04:54:33PM -0500, Sergey Babkin wrote:
> > Kris Kennaway wrote:
> > >
> > > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote:
> > > > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <[EMAIL PROTECTED]>
> > > >
> > > > >Gary Thorpe <[EMAIL
On Fri, 2006-Jan-20 16:54:33 -0500, Sergey Babkin wrote:
>Kris Kennaway wrote:
>> It's harder than that, because you need to impose dependency
>> information and mutual exclusion between different makes. e.g. they
>> can't both be compiling the same port at the same time, which will
>> happen if y
On Fri, Jan 20, 2006 at 03:28:08PM -0800, Gayn Winters wrote:
> > [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway
> > Sent: Friday, January 20, 2006 11:47 AM
> > To: Gary Thorpe
> > Cc: Wesley Shields; Ashok Shrestha; Brandon Flowers; Kris
> > Kennaway; Mike Meyer; freebsd-hackers@freebsd.org
> [mailto:[EMAIL PROTECTED] On Behalf Of Kris Kennaway
> Sent: Friday, January 20, 2006 11:47 AM
> To: Gary Thorpe
> Cc: Wesley Shields; Ashok Shrestha; Brandon Flowers; Kris
> Kennaway; Mike Meyer; freebsd-hackers@freebsd.org; Dag-Erling Sm?rgrav
> Subject: Re: speed up port compiling using RAM (
On Fri, Jan 20, 2006 at 04:54:33PM -0500, Sergey Babkin wrote:
> Kris Kennaway wrote:
> >
> > On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote:
> > > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <[EMAIL PROTECTED]>
> > >
> > > >Gary Thorpe <[EMAIL PROTECTED]> writes:
> > > >> This eff
Kris Kennaway wrote:
>
> On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote:
> > >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <[EMAIL PROTECTED]>
> >
> > >Gary Thorpe <[EMAIL PROTECTED]> writes:
> > >> This effectively means that you cannot take advantage of SMP to
> > >> compile FreeBS
On Fri, Jan 20, 2006 at 03:42:21PM -0500, John Baldwin wrote:
> Hmm, well, you can actually try the PAT patch if you are feeling brave as it
> maps all devices (including APICs) as uncacheable.
Heh, took me a minute to find. I first found the one at
http://people.freebsd.org/~jhb/patches/pat.pat
On Friday 20 January 2006 10:27, Craig Boston wrote:
> On Thu, Jan 19, 2006 at 10:17:39PM -0700, Scott Long wrote:
> > This points to a bus coherency problem. I wonder if your BIOS is
> > incorrectly setting the memory region of the apics as cachable. You'll
> > want to bug Baldwin about this.
>
On Sat, Jan 21, 2006 at 07:52:20AM +1100, Peter Jeremy wrote:5C
> IMHO, the biggest problem (as des pointed out) is that there's nothing
> to prevent two makes attempting to build the same port (this can
> easily happen when both ports A and B depend on port C). One possible
> solution would be t
On Fri, 2006-Jan-20 14:47:00 -0500, Kris Kennaway wrote:
>On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote:
>
>> >-j is not safe to use with port builds since many ported software
>> >contain race conditions in the build.
>> >
>> >Kris
>>
>> This effectively means that you cannot take a
On Fri, Jan 20, 2006 at 11:49:29AM -0500, Gary Thorpe wrote:
> >-j is not safe to use with port builds since many ported software
> >contain race conditions in the build.
> >
> >Kris
>
> This effectively means that you cannot take advantage of SMP to compile
> FreeBSD's ports collection. That so
On Fri, Jan 20, 2006 at 11:25:33AM -0600, Sergey Babkin wrote:
> >From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <[EMAIL PROTECTED]>
>
> >Gary Thorpe <[EMAIL PROTECTED]> writes:
> >> This effectively means that you cannot take advantage of SMP to
> >> compile FreeBSD's ports collection. That sounds l
>From: =?ISO646-US?Q?Dag-Erling_Sm=3Frgrav?= <[EMAIL PROTECTED]>
>Gary Thorpe <[EMAIL PROTECTED]> writes:
>> This effectively means that you cannot take advantage of SMP to
>> compile FreeBSD's ports collection. That sounds like a big
>> limitation...especially for people trying to speed up bulk b
Gary Thorpe <[EMAIL PROTECTED]> writes:
> This effectively means that you cannot take advantage of SMP to
> compile FreeBSD's ports collection. That sounds like a big
> limitation...especially for people trying to speed up bulk builds.
We cannot be held responsible for race conditions in the Makef
Kris Kennaway wrote:
On Thu, Jan 19, 2006 at 05:32:58PM -0500, Gary Thorpe wrote:
Ashok Shrestha wrote:
I mounted part of RAM as such:
mdmfs -s 500m md /mnt
Then put WRKDIRPREFIX=/path/to/md in /etc/make.conf.
It substantially reduces compile time by about 5-10 times.
Thanx to all ur re
On Thu, Jan 19, 2006 at 10:17:39PM -0700, Scott Long wrote:
> This points to a bus coherency problem. I wonder if your BIOS is
> incorrectly setting the memory region of the apics as cachable. You'll
> want to bug Baldwin about this.
I CC-ed him on my post since he was working with me on the pro
Wesley Shields <[EMAIL PROTECTED]> writes:
> I think he is trying to get at a scenario where WRKDIR is on a seperate
> disk from the one /usr/ports is on.
There is no performance advantage in doing that. I can only see two
possible reasons for pointing WRKDIRPREFIX to another disk:
- insufficie
19 matches
Mail list logo
