Another oddity I noticed in the log is

:info:build ld: warning: directory not found for option 
'-L/opt/local/var/macports/build/_Users_marbre_ports_math_taucs/taucs/work/taucs/lib/darwin16/'

That’s a valid path!

Mark Brethen
[email protected]



> On Nov 25, 2018, at 7:15 PM, Mark Brethen <[email protected]> wrote:
> 
> I used placeholders in the makefile then passed the environment variables 
> using reinplace statements. That worked, however I’m getting a make: 
> lib/darwin16/libtaucs.a: Permission denied. Sounds like I need to change the 
> permissions after extracting the source. Is there a tar flag for that?
> <main.log>
> Mark Brethen
> [email protected]
> 
> 
> 
>> On Nov 25, 2018, at 6:55 PM, Joshua Root <[email protected]> wrote:
>> 
>> On 2018-11-26 02:35 , Ryan Schmidt wrote:
>>> 
>>> 
>>> On Nov 25, 2018, at 09:13, Mark Brethen wrote:
>>> 
>>>> build {
>>>> ui_info "Building libtaucs archives:"
>>>> system -W ${worksrcpath} "${build.cmd} ${build.args} ${build.target}"
>>>> }
>>>> 
>>>> with 'LD = $(F77)’ in the Makefile, but that didn’t work. How should I 
>>>> pass this during build?
>>> 
>>> I suppose that ought to work, except that perhaps the problem you're 
>>> running into is that ${build.args} is a list of values. If you want to 
>>> concatenate all those list items with spaces and include that expanded 
>>> value in a string, as you're doing here, you'll need to use the expand 
>>> operator ({*}). Technically, build.cmd and build.target (and all other 
>>> MacPorts options) are lists too, though they might only contain one item at 
>>> the moment. To properly expand all those lists into strings, you'd use: 
>>> "{*}${build.cmd} {*}${build.args} {*}${build.target}".
>> 
>> The function of {*} is to pass a list to a command as multiple
>> arguments, one per list element. That is not what's desired here, as the
>> command to be run by system should be given in a single argument.
>> 
>> Perhaps you were thinking of 'join'? But that shouldn't really be needed
>> here either.
>> 
>> - Josh
> 

Reply via email to