Changes between Initial Version and Version 1 of Ticket #68742


Ignore:
Timestamp:
Nov 19, 2023, 7:33:01 PM (12 months ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #68742

    • Property Component changed from ports to base

  • Ticket #68742 – Description

    initial v1  
    1 In the world of the autotools, it is common to use a CONFIG_SITE to specify parameters to the configure script.  There is something about the current macports build that does not play well with this.  If the environment variable CONFIG_SITE is set to a path containing the text "prefix=/p/a/t/h", then the build (checked out at ddc57c5f6ced9ccc0bb4e04e22e218ae851c241d) fails.  To be specific:
     1In the world of the autotools, it is common to use a CONFIG_SITE to specify parameters to the configure script.  There is something about the current macports build that does not play well with this.  If the environment variable CONFIG_SITE is set to a path containing the text "prefix=/p/a/t/h", then the build (checked out at [ddc57c5f6ced9ccc0bb4e04e22e218ae851c241d/macports-base]) fails.  To be specific:
    22
     3{{{
    34export CONFIG_SITE=/some/path
    45echo 'prefix=/p/a/t/h' > $CONFIG_SITE
    56./configure
    67make
     8}}}
    79
    810fails with an error like:
    911
     12{{{
    1013chmod: ${PWD}/vendor/vendor-destroot/p/a/t/h/libexec/macports/lib/tcllib*: No such file or directory
     14}}}
    1115
    1216The build works fine if the config site is not used but instead the user invokes the configure script with the prefix specified as an argument.