Re: Calling functions in `make-flags'

2014-02-22 Thread Sree Harsha Totakura
On 02/23/2014 07:20 AM, Mark H Weaver wrote: > As for why 'which' didn't work, I suspect it's because this code is > evaluated very early in the build process, before the PATH variable has > been set. > > You can use 'which' in the code segments passed to #:phases because > those are wrapped with

Re: Calling functions in `make-flags'

2014-02-22 Thread Mark H Weaver
Sree Harsha Totakura writes: > Can you explain why my earlier code did not work? Your earlier code was: > (arguments > '(#:make-flags '((string-append "SH=" (which "sh"))) The expression immediately following "#:make-flags" is evaluated to produce the list of make flags. In this case, that

Re: Calling functions in `make-flags'

2014-02-22 Thread Sree Harsha Totakura
On 02/22/2014 08:34 AM, Mark H Weaver wrote: > Try this instead: > > (arguments >'(#:make-flags (list (string-append "SH=" (which "sh"))) > ...)) > That did not work, but the following did: > If that doesn't work, then try this: > > (arguments >'(#:make-flags (list (string-app

Re: Calling functions in `make-flags'

2014-02-21 Thread Mark H Weaver
Sree Harsha Totakura writes: > Hi, > > I am trying to build a package which does not have 'configure' script. > It instead relies solely on a makefile. For this to function, I have to > set the 'SH' variable inside the Makefile to a valid shell. > > I am trying to set the 'SH' variable through b

Calling functions in `make-flags'

2014-02-21 Thread Sree Harsha Totakura
Hi, I am trying to build a package which does not have 'configure' script. It instead relies solely on a makefile. For this to function, I have to set the 'SH' variable inside the Makefile to a valid shell. I am trying to set the 'SH' variable through build-flags like this: > (arguments > '(