Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 30 Dec 2010 20:37:49 +1000
From:      Da Rock <freebsd-questions@herveybayaustralia.com.au>
To:        Eitan Adler <lists@eitanadler.com>
Cc:        Bruce Cran <bruce@cran.org.uk>, freebsd-questions@freebsd.org
Subject:   Re: How to build a BROKEN port?
Message-ID:  <4D1C60FD.9090803@herveybayaustralia.com.au>
In-Reply-To: <AANLkTinhNWR1_CmmRtAJbDbHZ1_9K0v5F0kitcoYnbgY@mail.gmail.com>
References:  <4D1BD715.2010401@herveybayaustralia.com.au> <20101230010945.00003a5d@unknown> <4D1BDBEC.1050600@herveybayaustralia.com.au> <AANLkTinhNWR1_CmmRtAJbDbHZ1_9K0v5F0kitcoYnbgY@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 12/30/10 20:12, Eitan Adler wrote:
>>> Edit the port's Makefile and comment-out the BROKEN line.
>>>        
> Generally - don't do this.
>
>    
I kinda got that impression already, but can someone enlighten me why 
(apart from the obvious, of course- it could break the makefile if you 
forget)? And is that in general or just this line?

I ask because I'm currently editing the Makefile with some new variables 
to test a fix.
>>>        
>> Oh, the irony! :) I considered doing that, but I thought there might have
>> been some magic incantation that got around this...
>>
>>      
> There is
> make -DTRYBROKEN
>
>    
Thanks for the reply, but can someone tell me if this is documented 
anywhere particularly? I'm going to be pissed if I missed it ;)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D1C60FD.9090803>