Re: How to convert command.env tcl lists with spaces into working env strings

Thank you. I ended up refactoring the Portfile to use the default configure/build/destroot functionality. I was not aware that a side effect of writing one’s own build {} etc. blocks is that it blows away the automatic setting of environments variables in build.env. Thanks for suggesting—that

Re: Missing macOS libiconv.dylib Breaks ghc Bootstrap

Thanks for the pointers. I now have this working with MacPorts libiconv.dylib libraries, and have bootrapped ghc and cabal binaries that are independent of /usr/lib/libiconv.dylib. Relevant PR’s and issues: https://github.com/macports/macports-ports/pull/15770

Re: How to convert command.env tcl lists with spaces into working env strings

On 2022-9-1 21:51 , Steven Smith wrote: How does one convert a build.env list into a working string for sh env? If I specify this build.env build.env-append \     CC=${configure.cc } \ "CFLAGS=${configure.cflags} [get_canonical_archflags cc]" and later say something like

How to convert command.env tcl lists with spaces into working env strings

How does one convert a build.env list into a working string for sh env? If I specify this build.env > build.env-append \ > CC=${configure.cc} \ > "CFLAGS=${configure.cflags} [get_canonical_archflags cc]" and later say something like > system "env ${build.env}" This tcl string with br