On Sun, 24 Apr 2011, Carl wrote:
As for manually customizing /var/db/ports//options, the port builds
in question are done in a clean chroot using a batch process, so "make
config" doesn't happen and /var/db/ports//options never exists.
Why not just
make `cat options.txt`
Where options.txt
On 04/24/2011 11:26 AM, Carl wrote:
> On 2011-04-22 4:13 AM, Manolis Kiagias wrote:
>> On 04/22/2011 10:33 AM, Manolis Kiagias wrote:
>>> On 04/22/2011 10:08 AM, Carl wrote:
> This form will override the Makefile present in the current directory
> and will use the specified make file with n
On 24 Apr 2011 09:29, "Carl" wrote:
>
> On 2011-04-22 4:13 AM, Manolis Kiagias wrote:
>>
>> On 04/22/2011 10:33 AM, Manolis Kiagias wrote:
>>>
>>> On 04/22/2011 10:08 AM, Carl wrote:
>
> This form will override the Makefile present in the current directory
> and will use the specified
On 2011-04-22 4:13 AM, Manolis Kiagias wrote:
On 04/22/2011 10:33 AM, Manolis Kiagias wrote:
On 04/22/2011 10:08 AM, Carl wrote:
This form will override the Makefile present in the current directory
and will use the specified make file with name your_own_make_file_name .
make -f your_own_make_
> From owner-freebsd-questi...@freebsd.org Thu Apr 21 22:45:24 2011
> Date: Thu, 21 Apr 2011 20:17:31 -0700
> From: Carl
> To: freebsd-questions@freebsd.org
> Subject: building a port with very long list of build options
>
> Let's say I want to build a port for which I need to specify a huge
> n
On 04/22/2011 10:33 AM, Manolis Kiagias wrote:
> On 04/22/2011 10:08 AM, Carl wrote:
>>> This form will override the Makefile present in the current directory
>>> and will use the specified make file with name your_own_make_file_name .
>> make -f your_own_make_file_name
>>
>> Yes, I did see that, b
On Fri, Apr 22, 2011 at 3:08 AM, Carl wrote:
> On 2011-04-21 8:52 PM, Polytropon wrote:
>
>> This has been possible and common in the past. For example,
>> the many options for the mplayer and mencoder ports could
>> be specified in a file, so changing of a port's file was
>> not needed. I'm not
On 22 April 2011 08:08, Carl wrote:
> On 2011-04-21 8:52 PM, Polytropon wrote:
>>
>> This has been possible and common in the past. For example,
>> the many options for the mplayer and mencoder ports could
>> be specified in a file, so changing of a port's file was
>> not needed. I'm not fully sur
On 04/22/2011 10:08 AM, Carl wrote:
>
>>
>> This form will override the Makefile present in the current directory
>> and will use the specified make file with name your_own_make_file_name .
> make -f your_own_make_file_name
>
> Yes, I did see that, but I interpreted that to mean my make file
> *rep
On 2011-04-21 8:52 PM, Polytropon wrote:
This has been possible and common in the past. For example,
the many options for the mplayer and mencoder ports could
be specified in a file, so changing of a port's file was
not needed. I'm not fully sure this option is still present,
but at least on v7 i
On Thu, Apr 21, 2011 at 11:17 PM, Carl wrote:
> Let's say I want to build a port for which I need to specify a huge number
> of build options (eg. ghostscript). In my case I am cross-compiling on an
> amd64 host for what will be a NanoBSD i386 target, but I don't think that's
> important here. Th
On Thu, 21 Apr 2011 20:17:31 -0700, Carl wrote:
> Given that I do not want to customize the port's Makefile, I was hoping
> 'make' would support a command line option that would let me simply
> point to a separate file containing the list of variables to add, one
> per line. It's not apparent t
12 matches
Mail list logo
