> On Oct 24, 2020, at 9:50 AM, Ken Cunningham <ken.cunningham.web...@gmail.com>
> wrote:
>
>
>
>> On Oct 24, 2020, at 9:46 AM, Ken Cunningham <ken.cunningham.web...@gmail.com
>> <mailto:ken.cunningham.web...@gmail.com>> wrote:
>>
>> configure.env-append "DYLD_LIBRARY_PATH=${prefix}/lib/lilbgcc"
>> configure.env-append “DYLD_LIBRARY_PATH=${workpath}/build”
>>
>> but I found the second one just obliterates the first one.
>>
>> DYLD_LIBRARY_PATH='/opt/local/lib/lilbgcc'
>>
>>
>
> well the second one didn’t obliterate the first — other way around.
>
> but they both didn’t make into the env, which was what I was going for with
> that comment.
I am sorry, I cheated a bit using configure, and there is no ${workpath}/build
during configure, of course.
The second one did obliterate the first, which is what I saw last night, and it
shows up better using
destroot.env-append
where everything exists. For example, with “atk”, adding this:
destroot.env-append "DYLD_LIBRARY_PATH=${prefix}/lib/lilbgcc"
destroot.env-append “DYLD_LIBRARY_PATH=${workpath}/build”
gives:
“DYLD_LIBRARY_PATH='/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_atk/atk/work/build”'
Ken
