macports-users Digest, Vol 127, Issue 19
Franck Olivier Ngassam Nyakam
ngassamnyakam at gmail.com
Wed Mar 22 17:30:18 UTC 2017
Hello sir
Please i would like you to help me finish my xcrysden installation via macport. Indeed I followed the whole procedure and I have this message:Configuring gmp
Error: Failed to configure gmp, consult /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/work/gmp-6.1.2/config.log
Error: Failed to configure gmp: configure failure: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_gmp/gmp/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xcrysden failed
which appears when I enter the command sudo port install xcrysden +x11
Thank you
> Le 22 mars 2017 à 13:00, macports-users-request at lists.macports.org a écrit :
>
> Send macports-users mailing list submissions to
> macports-users at lists.macports.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.macports.org/mailman/listinfo/macports-users
> or, via email, send a message with subject or body 'help' to
> macports-users-request at lists.macports.org
>
> You can reach the person managing the list at
> macports-users-owner at lists.macports.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of macports-users digest..."
>
>
> Today's Topics:
>
> 1. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Jan Stary)
> 2. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Daniel J. Luke)
> 3. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Brandon Allbery)
> 4. Re: all compilers blacklisted or unavailable (Brandon Allbery)
> 5. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Jan Stary)
> 6. Re: all compilers blacklisted or unavailable (Jan Stary)
> 7. Re: all compilers blacklisted or unavailable (Daniel J. Luke)
> 8. Re: all compilers blacklisted or unavailable (Brandon Allbery)
> 9. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Peter West)
> 10. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Dave Horsfall)
> 11. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Brandon Allbery)
> 12. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Brandon Allbery)
> 13. Re: all compilers blacklisted or unavailable (Jan Stary)
> 14. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Chris Jones)
> 15. Re: port diagnose fails on 10.6.8 (Ryan Schmidt)
> 16. Re: ffmpeg update fails (Ryan Schmidt)
> 17. Re: ffmpeg update fails (Chris Jones)
> 18. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Ryan Schmidt)
> 19. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Ryan Schmidt)
> 20. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Brandon Allbery)
> 21. Re: all compilers blacklisted or unavailable (Ryan Schmidt)
> 22. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Ryan Schmidt)
> 23. Re: Prevent MacPorts editing .bash_profile over and over
> again... (Rainer Müller)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Tue, 21 Mar 2017 14:30:45 +0100
> From: Jan Stary <hans at stare.cz>
> To: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <20170321133045.GA13298 at www.stare.cz>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> On Jan 28 16:31:12, barry at barrys-emacs.org wrote:
>> I want to be able to stop MacPorts Installation from editing my .bash_profile.
>> As it happens I already set all the env var that are needed my self.
>
> On Feb 01 00:38:03, ryandesign at macports.org wrote:
>>> Nothing should change my .bash_profile without asking back.
>>> It is something that malware usually does.
>>
>> The MacPorts installer has always done this. I'm pretty sure it tells you it will do this, and our documentation says so too. The alternative is that the user installs MacPorts, then when they try to use it they get an error that "port" could not be found in the path.
>
> The same error is there now.
> After a fresh install of 2.4.1 yesterday,
> 'port' is not found, because /opt/local/bin is not in my PATH.
> The installer has written the PATH=... bit into my ~/.profile,
> but that does not mean it is the PATH of the shell I am already running.
> It will be, after I start a new shell, or re-login.
>
>> this will cause tons of support requests that I would prefer to avoid, so I'd like to keep things the way they are, with the installer modifying the user's profile when needed.
>
> I appreciate you concern about being spammed with trivia.
> But it's one line in ~/.profile, which is equally trivial.
> I find mangling the user's shell configuration worse:
> someone who uses macports to install software
> is capable of editing one line in their config if told so.
>
> We can trade all this for a sentence that says
> "add /opt/local/bin to your $PATH". In fact,
> the documentation already says so for EDITOR.
> How is this different?
>
> On Feb 01 15:20:26, web at bachsau.name wrote:
>> Not only repeated modifications.
>> It simply should not do that in any case.
>
> Exactly.
>
> I will try to come up with a diff tonight.
>
> Jan
>
>
>
> ------------------------------
>
> Message: 2
> Date: Tue, 21 Mar 2017 11:29:03 -0400
> From: "Daniel J. Luke" <dluke at geeklair.net>
> To: Jan Stary <hans at stare.cz>
> Cc: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <C729693C-2A46-430B-8C75-E6D2E1EE1A57 at geeklair.net>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> On Mar 21, 2017, at 9:30 AM, Jan Stary <hans at stare.cz> wrote:
>> I appreciate you concern about being spammed with trivia.
>> But it's one line in ~/.profile, which is equally trivial.
>
> While I agree with you in principle (see list archives where I disagreed with adding this to the installer way back when it was first introduced) - Ryan is right that we used to get lots of support requests where people apparently weren't capable of reading the instructions and updating their $PATH themselves.
>
> Our actual experience around this issue tells us that it's worse to not try to set $PATH in the installer.
>
>> I find mangling the user's shell configuration worse:
>> someone who uses macports to install software
>> is capable of editing one line in their config if told so.
>
> users who are smart enough to edit their configs are also smart enough to install from source (where you don't have this issue at all).
>
> --
> Daniel J. Luke
>
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Tue, 21 Mar 2017 14:11:38 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: "Daniel J. Luke" <dluke at geeklair.net>
> Cc: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID:
> <CAKFCL4XbB+h-hDCTErs9J48Cc8FxJtkxoo=OOeUBSJPV-4iRBw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Mar 21, 2017 at 11:29 AM, Daniel J. Luke <dluke at geeklair.net> wrote:
>
>> While I agree with you in principle (see list archives where I disagreed
>> with adding this to the installer way back when it was first introduced) -
>> Ryan is right that we used to get lots of support requests where people
>> apparently weren't capable of reading the instructions and updating their
>> $PATH themselves.
>
>
> Never assume people will read instructions. How often do we get people who
> cut and paste the boilerplate at the end of a failed build that tells them
> to check the build log, and mail it here asking what they should do?
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170321/79c6b37a/attachment-0001.html>
>
> ------------------------------
>
> Message: 4
> Date: Tue, 21 Mar 2017 14:43:12 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: MacPorts Users <macports-users at lists.macosforge.org>
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID:
> <CAKFCL4U2Vu=2YxfR7=WnQmFrxvoNOPYrYZ6jkGLgrFmhgtPXJg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary <hans at stare.cz> wrote:
>
>> Why are they unavailable? The gcc and clang from Xcode work just fine.
>
>
> "Works for random stuff I tried it on" does not guarantee it doesn't throw
> spurious errors or even produce broken programs in specific cases (which is
> to say, most compilers have bugs, but you only run into them in certain
> cases). Compilers get blacklisted for specific ports when they have been
> found to be incapable of building that port properly.
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170321/b72420e6/attachment-0001.html>
>
> ------------------------------
>
> Message: 5
> Date: Tue, 21 Mar 2017 21:43:28 +0100
> From: Jan Stary <hans at stare.cz>
> To: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <20170321204328.GA53623 at www.stare.cz>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> Here is a diff to postflight and an accompanying diff to installing.xml
> (what other places need to be touched if this goes through?)
>
> Jan
>
>
> diff --git a/portmgr/dmg/postflight.in b/portmgr/dmg/postflight.in
> index 750553f0..a3a8bd80 100755
> --- a/portmgr/dmg/postflight.in
> +++ b/portmgr/dmg/postflight.in
> @@ -87,28 +87,6 @@ function update_macports {
> fi
> }
>
> -# Through this command we write an environment variable to an appropriate shell configuration file,
> -# backing up the original only if it exists and if it doesn't contain the ${OUR_STRING} identification string,
> -# which hints that we've already tweaked it and therefore already backed it up.
> -function write_setting () {
> - if [[ -f "${HOME}/.${CONF_FILE}" ]] && ! grep "${OUR_BASESTRING}" "${HOME}/.${CONF_FILE}" > /dev/null; then
> - echo "Backing up your ${HOME}/.${CONF_FILE} shell confguration file as ${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX} before adapting it for MacPorts."
> - /bin/cp -fp "${HOME}/.${CONF_FILE}" "${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX}" || {
> - echo "An attempt to backup your original configuration file failed! Please set your MacPorts compatible environment manually."
> - update_macports
> - exit 1
> - }
> - echo -e "\n##\n# Your previous ${HOME}/.${CONF_FILE} file was backed up as ${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX}\n##" >> "${HOME}/.${CONF_FILE}"
> - fi
> - {
> - echo -e "\n# ${OUR_STRING}: adding an appropriate ${1} variable for use with MacPorts."
> - echo "${ENV_COMMAND} ${1}${ASSIGN}${2}"
> - echo -e "# Finished adapting your ${1} environment variable for use with MacPorts.\n"
> - } >> "${HOME}/.${CONF_FILE}"
> - chown "${USER}" "${HOME}/.${CONF_FILE}" || echo "Warning: unable to adapt permissions on your ${HOME}/.${CONF_FILE} shell configuration file!"
> - echo "An appropriate ${1} variable has been added to your shell environment by the MacPorts installer."
> -}
> -
> function cleanup_man () {
> # Remove old non-compressed man pages
> echo -e "\nRemoving old man pages..."
> @@ -195,8 +173,6 @@ function create_run_user {
> fi
> }
>
> -echo "The MacPorts Project, postflight script version ${VERSION}: checking the shell environment for user \"${USER}\"."
> -
> # create macports user
> create_run_user
> # Set up config files
> @@ -207,78 +183,11 @@ cleanup_man
> delete_old_tcl_package_link
> delete_old_tcl_packages
>
> -# Determine the user's shell, in order to choose an appropriate configuration file we'll be tweaking.
> -# Exit nicely if the shell is any other than bash or tcsh, as that's considered non-standard.
> -USHELL=$(${DSCL} . -read "/Users/${USER}" shell) || {
> - echo "An attempt to determine your shell name failed! Please set your MacPorts compatible environment manually."
> - update_macports
> - exit 1
> -}
> -# leave full path to shell
> -USHELL=${USHELL#*shell: }
> -
> -case "${USHELL}" in
> - */tcsh)
> - echo "Detected the tcsh shell."
> - LOGIN_FLAG=""
> - ENV_COMMAND="setenv"
> - ASSIGN=" "
> - if [[ -f "${HOME}/.tcshrc" ]]; then
> - CONF_FILE=tcshrc
> - elif [[ -f "${HOME}/.cshrc" ]]; then
> - CONF_FILE=cshrc
> - else
> - CONF_FILE=tcshrc
> - fi
> - ;;
> - */bash)
> - echo "Detected the bash shell."
> - LOGIN_FLAG="-l"
> - ENV_COMMAND="export"
> - ASSIGN="="
> - if [[ -f "${HOME}/.bash_profile" ]]; then
> - CONF_FILE=bash_profile
> - elif [[ -f "${HOME}/.bash_login" ]]; then
> - CONF_FILE=bash_login
> - else
> - CONF_FILE=profile
> - fi
> - ;;
> - *)
> - echo "Unknown shell ($USHELL)! Please set your MacPorts compatible environment manually."
> - update_macports
> - exit 0
> - ;;
> -esac
> -
> -# Adding our setting to the PATH variable if not already there:
> -# Run as the $USER: /usr/bin/su $USER -l
> -# Run a command in the shell: -c "/usr/bin/printenv PATH"
> -# Only process the last line output (profile may print info): tail -n 1
> -# Output each path on its own line: tr ":" "\n"
> -# Look for exactly the BINPATH: grep "^${BINPATH}$"
> -if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv PATH" | tail -n 1 | tr ":" "\n" | grep "^${BINPATH}$" > /dev/null; then
> - echo "Your shell already has the right PATH environment variable for use with MacPorts!"
> -else
> - write_setting PATH "\"${BINPATH}:${SBINPATH}:\$PATH\""
> -fi
> -
> -# Adding our setting to the MANPATH variable only if it exists:
> -if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv MANPATH" > /dev/null; then
> - # check for MANPAGES already in MANPATH
> - if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv MANPATH" | tail -n 1 | tr ":" "\n" | grep "^${MANPAGES}$" >/dev/null; then
> - echo "Your shell already has the right MANPATH environment variable for use with MacPorts!"
> - else
> - write_setting MANPATH "\"${MANPAGES}:\$MANPATH\""
> - fi
> -fi
> -
> -# Adding a DISPLAY variable only if we're running on Tiger or less and if it doesn't already exist:
> -if (($(sw_vers -productVersion | awk -F . '{print $2}') >= 5)) || /usr/bin/su "${USER}" -l -c "/usr/bin/printenv DISPLAY" > /dev/null > /dev/null; then
> - echo "Your shell already has the right DISPLAY environment variable for use with MacPorts!"
> -else
> - write_setting DISPLAY ":0"
> -fi
> +echo "Remember to set your environment:"
> +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH."
> +echo "Prepend ${MANPAGES} to MANPATH if you use MANPATH."
> +echo "Remember to set DISPLAY if you are on 10.4 or older."
> +echo "See https://guide.macports.org/#installing.shell for details."
>
> # Postflight script is done with its job, update MacPorts and exit gracefully!
> update_macports
>
>
>
>
> diff --git a/guide/xml/installing.xml b/guide/xml/installing.xml
> index 31f8719..18adb66 100644
> --- a/guide/xml/installing.xml
> +++ b/guide/xml/installing.xml
> @@ -412,34 +412,25 @@
> <section id="installing.shell">
> <title>MacPorts and the Shell</title>
>
> - <para>MacPorts requires that some environment variables be set in the shell. When MacPorts is installed using
> - the OS X package installer, a <quote>postflight</quote> script is run after installation that automatically
> - adds or modifies a shell configuration file in your home directory, ensuring that it defines variables
> - according to the rules described in the following section. Those <link
> - linkend="installing.macports.source">installing MacPorts from source code</link> must modify their
> - environment manually using the rules as a guide.</para>
> -
> - <para>Depending on your shell and which configuration files already exist, the installer may use
> - <filename>.profile</filename>, <filename>.bash_login</filename>, <filename>.bash_profile</filename>,
> - <filename>.tcshrc</filename>, or <filename>.cshrc</filename>.</para>
> + <para>MacPorts requires that some environment variables be set in the shell.
> + Depending on your shell, this means you need to edit some of the following config files:
> + <filename>.profile</filename>, <filename>.bash_login</filename> or <filename>.bash_profile</filename> for bash,
> + <filename>.tcshrc</filename> or <filename>.cshrc</filename> for tcsh.</para>
>
> <section id="installing.shell.postflight">
> - <title>The Postflight Script</title>
> + <title>Configure Your Environment</title>
>
> - <para>The postflight script automatically sets the <varname>PATH</varname> variable, and optionally the
> - <varname>MANPATH</varname> and <varname>DISPLAY</varname> variables according to the rules described
> - below. If a current shell configuration file exists at installation time it is renamed to
> - <quote>mpsaved_$timestamp</quote>. Those <link linkend="installing.macports.source">installing MacPorts
> - from source code</link> must modify their environment manually using the rules as a guide.</para>
> + <para>The <varname>PATH</varname> environment variable,
> + and optionally <varname>MANPATH</varname> and <varname>DISPLAY</varname> variables need to be edited
> + according to the rules described below.</para>
>
> <itemizedlist>
> <listitem>
> <para>Required: <varname>PATH</varname> variable</para>
>
> - <para>This variable is set by the postflight script to append the MacPorts executable paths to the
> - default path as shown. The MacPorts paths are appended at the front of <varname>PATH</varname>
> - so the MacPorts libraries will take precedence over vendor-supplied libraries for ported
> - software at runtime.</para>
> + <para>This variable should have the MacPorts executable paths prepended to the default path as shown.
> + The MacPorts paths are at the front of <varname>PATH</varname> so that the MacPorts binaries
> + will take precedence over vendor-supplied libraries.</para>
>
> <programlisting>export PATH=/opt/local/bin:/opt/local/sbin:$PATH</programlisting>
>
> @@ -456,30 +447,18 @@
> <listitem>
> <para>Optional: <varname>MANPATH</varname> variable</para>
>
> - <para>Condition: If prior to MacPorts installation a <varname>MANPATH</varname> variable exists in
> - a current <filename>.profile</filename> that contains neither the value
> - <filename>${prefix}/share/man,</filename> nor any empty values, the postflight script sets the
> - <varname>MANPATH</varname> variable as shown below. Otherwise, the <varname>MANPATH</varname>
> - variable is omitted.</para>
> + <para>If your shell configuration sets a <varname>MANPATH</varname> variable,
> + it should be edited to contain <filename>${prefix}/share/man</filename>.</para>
>
> <programlisting>export MANPATH=/opt/local/share/man:$MANPATH</programlisting>
> -
> - <para>Here are some examples of paths that contain empty values:</para>
> -
> - <simplelist>
> - <member>/usr/share/man:</member>
> - <member>:/usr/share/man</member>
> - <member>/usr/share/man::/usr/X11R6/man</member>
> - </simplelist>
> </listitem>
>
> <listitem>
> <para>Optional: <varname>DISPLAY</varname> variable</para>
>
> - <para>Condition: If installing on a Mac OS X version earlier than 10.5 (Leopard), and if a shell
> - configuration file exists at time of MacPorts installation without a <varname>DISPLAY</varname>
> - variable, the postflight script sets a <varname>DISPLAY</varname> variable as shown below. The
> - <varname>DISPLAY</varname> variable is always omitted on Mac OS X 10.5 or higher.</para>
> + <para>If installing on a Mac OS X version earlier than 10.5 (Leopard),
> + a <varname>DISPLAY</varname> variable should be set as shown below.
> + On Mac OS X 10.5 or higher, the <varname>DISPLAY</varname> variable is always omitted.</para>
>
> <programlisting>export DISPLAY=:0.0</programlisting>
> </listitem>
> @@ -487,7 +466,7 @@
> </section>
>
> <section id="installing.shell.verifyprofile">
> - <title>Verify the Configuration File</title>
> + <title>Verify the Configuration</title>
>
> <para>To verify that the file containing the MacPorts variables is in effect, type <command>env</command> in
> the terminal to verify the current environment settings after the file has been created. Example output
>
>
> ------------------------------
>
> Message: 6
> Date: Tue, 21 Mar 2017 22:03:20 +0100
> From: Jan Stary <hans at stare.cz>
> To: macports-users at lists.macports.org
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID: <20170321210320.GA48496 at www.stare.cz>
> Content-Type: text/plain; charset=us-ascii
>
> On Mar 21 14:43:12, allbery.b at gmail.com wrote:
>> On Tue, Mar 21, 2017 at 4:37 AM, Jan Stary <hans at stare.cz> wrote:
>>
>>> Why are they unavailable? The gcc and clang from Xcode work just fine.
>>
>>
>> "Works for random stuff I tried it on" does not guarantee it doesn't throw
>> spurious errors or even produce broken programs in specific cases (which is
>> to say, most compilers have bugs, but you only run into them in certain
>> cases). Compilers get blacklisted for specific ports when they have been
>> found to be incapable of building that port properly.
>
> I don't doubt that compilers throw errors or even produce broken code.
> But which specific compilers are blacklisted for which specific reasons
> when building sox, specifically? I don't see anything compiler-related
> in the sox's Portfile.
>
> Looking at the output of port -v -d install sox:
>
> DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>
> That does not look like a specific reason why clang fails to build sox properly.
> Does that mean clang < 500 (as installed by Xcode 3.2.6) is blacklisted as such,
> for building any port?
>
> Even if so, why are "all compilers blacklisted" after clang has been ruled out?
>
> Jan
>
>
>
> ------------------------------
>
> Message: 7
> Date: Tue, 21 Mar 2017 17:26:35 -0400
> From: "Daniel J. Luke" <dluke at geeklair.net>
> To: Jan Stary <hans at stare.cz>
> Cc: macports-users at lists.macports.org
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID: <966A5548-D9BA-4B84-8801-603E05E5EDC0 at geeklair.net>
> Content-Type: text/plain; charset=us-ascii
>
> On Mar 21, 2017, at 5:03 PM, Jan Stary <hans at stare.cz> wrote:
>> Looking at the output of port -v -d install sox:
>>
>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>>
>> That does not look like a specific reason why clang fails to build sox properly.
>
> you trimmed the relevant information - that's almost certainly coming from a port that sox requires and not sox itself.
>
> Most of the ports that use compiler blacklist have a comment in the portfile explaining why (most people don't care, though ;-) ).
>
> --
> Daniel J. Luke
>
>
>
>
>
> ------------------------------
>
> Message: 8
> Date: Tue, 21 Mar 2017 17:29:09 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: "Daniel J. Luke" <dluke at geeklair.net>
> Cc: macports-users <macports-users at lists.macports.org>
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID:
> <CAKFCL4XHUpqK5Tr-W-i8jj0S=yDnfvC_oWMT=1zw2BwXGmFtVw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> IIRC there's also an edge case when something tries to check the compiler
> in a fetch step or w/e and the information doesn't exist yet, so all
> compilers are "blacklisted" because there are no compilers defined yet,
> while the code printing that assumes the compiler list is empty because
> blacklisting removed all of them? And I think another if something tries to
> look up Xcode-specific information but the xcode portgroup hasn't been
> initialized?
>
> On Tue, Mar 21, 2017 at 5:26 PM, Daniel J. Luke <dluke at geeklair.net> wrote:
>
>> On Mar 21, 2017, at 5:03 PM, Jan Stary <hans at stare.cz> wrote:
>>> Looking at the output of port -v -d install sox:
>>>
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>>> Warning: All compilers are either blacklisted or unavailable; defaulting
>> to first fallback option
>>> Warning: All compilers are either blacklisted or unavailable; defaulting
>> to first fallback option
>>>
>>> That does not look like a specific reason why clang fails to build sox
>> properly.
>>
>> you trimmed the relevant information - that's almost certainly coming from
>> a port that sox requires and not sox itself.
>>
>> Most of the ports that use compiler blacklist have a comment in the
>> portfile explaining why (most people don't care, though ;-) ).
>>
>> --
>> Daniel J. Luke
>>
>>
>>
>>
>
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170321/6777f937/attachment-0001.html>
>
> ------------------------------
>
> Message: 9
> Date: Wed, 22 Mar 2017 09:04:21 +1000
> From: Peter West <lists at pbw.id.au>
> To: Jan Stary <hans at stare.cz>, macports-users at lists.macosforge.org
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <19D62638-AEF1-44FE-9085-34D6750AA849 at pbw.id.au>
> Content-Type: text/plain; charset=utf-8
>
>> On 21 Mar 2017, at 11:30 pm, Jan Stary <hans at stare.cz> wrote:
>>
> …
>> The same error is there now.
>> After a fresh install of 2.4.1 yesterday,
>> 'port' is not found, because /opt/local/bin is not in my PATH.
>> The installer has written the PATH=... bit into my ~/.profile,
>> but that does not mean it is the PATH of the shell I am already running.
>> It will be, after I start a new shell, or re-login.
>
> Does
> . ~/.profile
> work?
>
> --
> Peter West
> pbw at pbw.id.au
> “Even the pagans do as much, do they not?”
>
>
>
> ------------------------------
>
> Message: 10
> Date: Wed, 22 Mar 2017 08:23:44 +1100 (EST)
> From: Dave Horsfall <dave at horsfall.org>
> To: macports-users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <alpine.BSF.2.20.1703220815470.63087 at aneurin.horsfall.org>
> Content-Type: text/plain; charset=US-ASCII
>
> On Tue, 21 Mar 2017, Brandon Allbery wrote:
>
>> Never assume people will read instructions. How often do we get people
>> who cut and paste the boilerplate at the end of a failed build that
>> tells them to check the build log, and mail it here asking what they
>> should do?
>
> Which reminds me: would it be possible to symlink to the log file from
> somewhere in /tmp? It's a real PITA doing a C&P with a path that wraps
> lines... Yes, I'm an old fogey, and use 80 columns...
>
> --
> Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
>
>
> ------------------------------
>
> Message: 11
> Date: Tue, 21 Mar 2017 19:18:46 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: Dave Horsfall <dave at horsfall.org>
> Cc: macports-users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID:
> <CAKFCL4We1B1t1fH8BswH2cVDzHdptob3Q66MidcG-6WqCXXiCw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Mar 21, 2017 at 5:23 PM, Dave Horsfall <dave at horsfall.org> wrote:
>
>> On Tue, 21 Mar 2017, Brandon Allbery wrote:
>>> Never assume people will read instructions. How often do we get people
>>> who cut and paste the boilerplate at the end of a failed build that
>>> tells them to check the build log, and mail it here asking what they
>>> should do?
>>
>> Which reminds me: would it be possible to symlink to the log file from
>> somewhere in /tmp? It's a real PITA doing a C&P with a path that wraps
>> lines... Yes, I'm an old fogey, and use 80 columns...
>>
>
> vim $(port logfile thePort)
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170321/faefa1b5/attachment-0001.html>
>
> ------------------------------
>
> Message: 12
> Date: Tue, 21 Mar 2017 19:21:12 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: Dave Horsfall <dave at horsfall.org>
> Cc: macports-users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID:
> <CAKFCL4UO=Cn4rXka1+GoJb_jjsmgE1FiEN44zuuWtxEZzSyVcw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery <allbery.b at gmail.com>
> wrote:
>
>> vim $(port logfile thePort)
>>
>
> ...and the port you installed will usually get expanded with <esc>.
> (bash/zsh, in default emacs mode) so you don't even need to type that :)
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170321/123fe81d/attachment-0001.html>
>
> ------------------------------
>
> Message: 13
> Date: Wed, 22 Mar 2017 00:43:05 +0100
> From: Jan Stary <hans at stare.cz>
> To: macports-users at lists.macports.org
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID: <20170321234305.GA9338 at www.stare.cz>
> Content-Type: text/plain; charset=us-ascii
>
> On Mar 21 17:26:35, dluke at geeklair.net wrote:
>> On Mar 21, 2017, at 5:03 PM, Jan Stary <hans at stare.cz> wrote:
>>> Looking at the output of port -v -d install sox:
>>>
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 503}
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>>> DEBUG: compiler clang 77 blacklisted because it matches {clang < 500}
>>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>>>
>>> That does not look like a specific reason why clang fails to build sox properly.
>>
>> you trimmed the relevant information - that's almost certainly coming from a port that sox requires and not sox itself.
>
> No, all of Sox's requirements are already installed.
>
>> Most of the ports that use compiler blacklist have a comment in the portfile explaining why (most people don't care, though ;-) ).
>
> SoX does not blacklist anything in its Portfile.
>
>
>
> ------------------------------
>
> Message: 14
> Date: Wed, 22 Mar 2017 09:39:16 +0000
> From: Chris Jones <jonesc at hep.phy.cam.ac.uk>
> To: macports-users at lists.macports.org
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <5cbb91cb-64d4-41c8-4009-e5a6ef38aa86 at hep.phy.cam.ac.uk>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
>
> On 21/03/17 20:43, Jan Stary wrote:
>> Here is a diff to postflight and an accompanying diff to installing.xml
>> (what other places need to be touched if this goes through?)
>
> I do not think this will get committed. At least I hope it does not. As
> explained by others the current situation where if you use the installer
> then the config file gets updated, but if you install from source is the
> best compromise of user friendliness.
>
>>
>> Jan
>>
>>
>> diff --git a/portmgr/dmg/postflight.in b/portmgr/dmg/postflight.in
>> index 750553f0..a3a8bd80 100755
>> --- a/portmgr/dmg/postflight.in
>> +++ b/portmgr/dmg/postflight.in
>> @@ -87,28 +87,6 @@ function update_macports {
>> fi
>> }
>>
>> -# Through this command we write an environment variable to an appropriate shell configuration file,
>> -# backing up the original only if it exists and if it doesn't contain the ${OUR_STRING} identification string,
>> -# which hints that we've already tweaked it and therefore already backed it up.
>> -function write_setting () {
>> - if [[ -f "${HOME}/.${CONF_FILE}" ]] && ! grep "${OUR_BASESTRING}" "${HOME}/.${CONF_FILE}" > /dev/null; then
>> - echo "Backing up your ${HOME}/.${CONF_FILE} shell confguration file as ${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX} before adapting it for MacPorts."
>> - /bin/cp -fp "${HOME}/.${CONF_FILE}" "${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX}" || {
>> - echo "An attempt to backup your original configuration file failed! Please set your MacPorts compatible environment manually."
>> - update_macports
>> - exit 1
>> - }
>> - echo -e "\n##\n# Your previous ${HOME}/.${CONF_FILE} file was backed up as ${HOME}/.${CONF_FILE}.${BACKUP_SUFFIX}\n##" >> "${HOME}/.${CONF_FILE}"
>> - fi
>> - {
>> - echo -e "\n# ${OUR_STRING}: adding an appropriate ${1} variable for use with MacPorts."
>> - echo "${ENV_COMMAND} ${1}${ASSIGN}${2}"
>> - echo -e "# Finished adapting your ${1} environment variable for use with MacPorts.\n"
>> - } >> "${HOME}/.${CONF_FILE}"
>> - chown "${USER}" "${HOME}/.${CONF_FILE}" || echo "Warning: unable to adapt permissions on your ${HOME}/.${CONF_FILE} shell configuration file!"
>> - echo "An appropriate ${1} variable has been added to your shell environment by the MacPorts installer."
>> -}
>> -
>> function cleanup_man () {
>> # Remove old non-compressed man pages
>> echo -e "\nRemoving old man pages..."
>> @@ -195,8 +173,6 @@ function create_run_user {
>> fi
>> }
>>
>> -echo "The MacPorts Project, postflight script version ${VERSION}: checking the shell environment for user \"${USER}\"."
>> -
>> # create macports user
>> create_run_user
>> # Set up config files
>> @@ -207,78 +183,11 @@ cleanup_man
>> delete_old_tcl_package_link
>> delete_old_tcl_packages
>>
>> -# Determine the user's shell, in order to choose an appropriate configuration file we'll be tweaking.
>> -# Exit nicely if the shell is any other than bash or tcsh, as that's considered non-standard.
>> -USHELL=$(${DSCL} . -read "/Users/${USER}" shell) || {
>> - echo "An attempt to determine your shell name failed! Please set your MacPorts compatible environment manually."
>> - update_macports
>> - exit 1
>> -}
>> -# leave full path to shell
>> -USHELL=${USHELL#*shell: }
>> -
>> -case "${USHELL}" in
>> - */tcsh)
>> - echo "Detected the tcsh shell."
>> - LOGIN_FLAG=""
>> - ENV_COMMAND="setenv"
>> - ASSIGN=" "
>> - if [[ -f "${HOME}/.tcshrc" ]]; then
>> - CONF_FILE=tcshrc
>> - elif [[ -f "${HOME}/.cshrc" ]]; then
>> - CONF_FILE=cshrc
>> - else
>> - CONF_FILE=tcshrc
>> - fi
>> - ;;
>> - */bash)
>> - echo "Detected the bash shell."
>> - LOGIN_FLAG="-l"
>> - ENV_COMMAND="export"
>> - ASSIGN="="
>> - if [[ -f "${HOME}/.bash_profile" ]]; then
>> - CONF_FILE=bash_profile
>> - elif [[ -f "${HOME}/.bash_login" ]]; then
>> - CONF_FILE=bash_login
>> - else
>> - CONF_FILE=profile
>> - fi
>> - ;;
>> - *)
>> - echo "Unknown shell ($USHELL)! Please set your MacPorts compatible environment manually."
>> - update_macports
>> - exit 0
>> - ;;
>> -esac
>> -
>> -# Adding our setting to the PATH variable if not already there:
>> -# Run as the $USER: /usr/bin/su $USER -l
>> -# Run a command in the shell: -c "/usr/bin/printenv PATH"
>> -# Only process the last line output (profile may print info): tail -n 1
>> -# Output each path on its own line: tr ":" "\n"
>> -# Look for exactly the BINPATH: grep "^${BINPATH}$"
>> -if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv PATH" | tail -n 1 | tr ":" "\n" | grep "^${BINPATH}$" > /dev/null; then
>> - echo "Your shell already has the right PATH environment variable for use with MacPorts!"
>> -else
>> - write_setting PATH "\"${BINPATH}:${SBINPATH}:\$PATH\""
>> -fi
>> -
>> -# Adding our setting to the MANPATH variable only if it exists:
>> -if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv MANPATH" > /dev/null; then
>> - # check for MANPAGES already in MANPATH
>> - if /usr/bin/su "${USER}" -l -c "/usr/bin/printenv MANPATH" | tail -n 1 | tr ":" "\n" | grep "^${MANPAGES}$" >/dev/null; then
>> - echo "Your shell already has the right MANPATH environment variable for use with MacPorts!"
>> - else
>> - write_setting MANPATH "\"${MANPAGES}:\$MANPATH\""
>> - fi
>> -fi
>> -
>> -# Adding a DISPLAY variable only if we're running on Tiger or less and if it doesn't already exist:
>> -if (($(sw_vers -productVersion | awk -F . '{print $2}') >= 5)) || /usr/bin/su "${USER}" -l -c "/usr/bin/printenv DISPLAY" > /dev/null > /dev/null; then
>> - echo "Your shell already has the right DISPLAY environment variable for use with MacPorts!"
>> -else
>> - write_setting DISPLAY ":0"
>> -fi
>> +echo "Remember to set your environment:"
>> +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH."
>> +echo "Prepend ${MANPAGES} to MANPATH if you use MANPATH."
>> +echo "Remember to set DISPLAY if you are on 10.4 or older."
>> +echo "See https://guide.macports.org/#installing.shell for details."
>>
>> # Postflight script is done with its job, update MacPorts and exit gracefully!
>> update_macports
>>
>>
>>
>>
>> diff --git a/guide/xml/installing.xml b/guide/xml/installing.xml
>> index 31f8719..18adb66 100644
>> --- a/guide/xml/installing.xml
>> +++ b/guide/xml/installing.xml
>> @@ -412,34 +412,25 @@
>> <section id="installing.shell">
>> <title>MacPorts and the Shell</title>
>>
>> - <para>MacPorts requires that some environment variables be set in the shell. When MacPorts is installed using
>> - the OS X package installer, a <quote>postflight</quote> script is run after installation that automatically
>> - adds or modifies a shell configuration file in your home directory, ensuring that it defines variables
>> - according to the rules described in the following section. Those <link
>> - linkend="installing.macports.source">installing MacPorts from source code</link> must modify their
>> - environment manually using the rules as a guide.</para>
>> -
>> - <para>Depending on your shell and which configuration files already exist, the installer may use
>> - <filename>.profile</filename>, <filename>.bash_login</filename>, <filename>.bash_profile</filename>,
>> - <filename>.tcshrc</filename>, or <filename>.cshrc</filename>.</para>
>> + <para>MacPorts requires that some environment variables be set in the shell.
>> + Depending on your shell, this means you need to edit some of the following config files:
>> + <filename>.profile</filename>, <filename>.bash_login</filename> or <filename>.bash_profile</filename> for bash,
>> + <filename>.tcshrc</filename> or <filename>.cshrc</filename> for tcsh.</para>
>>
>> <section id="installing.shell.postflight">
>> - <title>The Postflight Script</title>
>> + <title>Configure Your Environment</title>
>>
>> - <para>The postflight script automatically sets the <varname>PATH</varname> variable, and optionally the
>> - <varname>MANPATH</varname> and <varname>DISPLAY</varname> variables according to the rules described
>> - below. If a current shell configuration file exists at installation time it is renamed to
>> - <quote>mpsaved_$timestamp</quote>. Those <link linkend="installing.macports.source">installing MacPorts
>> - from source code</link> must modify their environment manually using the rules as a guide.</para>
>> + <para>The <varname>PATH</varname> environment variable,
>> + and optionally <varname>MANPATH</varname> and <varname>DISPLAY</varname> variables need to be edited
>> + according to the rules described below.</para>
>>
>> <itemizedlist>
>> <listitem>
>> <para>Required: <varname>PATH</varname> variable</para>
>>
>> - <para>This variable is set by the postflight script to append the MacPorts executable paths to the
>> - default path as shown. The MacPorts paths are appended at the front of <varname>PATH</varname>
>> - so the MacPorts libraries will take precedence over vendor-supplied libraries for ported
>> - software at runtime.</para>
>> + <para>This variable should have the MacPorts executable paths prepended to the default path as shown.
>> + The MacPorts paths are at the front of <varname>PATH</varname> so that the MacPorts binaries
>> + will take precedence over vendor-supplied libraries.</para>
>>
>> <programlisting>export PATH=/opt/local/bin:/opt/local/sbin:$PATH</programlisting>
>>
>> @@ -456,30 +447,18 @@
>> <listitem>
>> <para>Optional: <varname>MANPATH</varname> variable</para>
>>
>> - <para>Condition: If prior to MacPorts installation a <varname>MANPATH</varname> variable exists in
>> - a current <filename>.profile</filename> that contains neither the value
>> - <filename>${prefix}/share/man,</filename> nor any empty values, the postflight script sets the
>> - <varname>MANPATH</varname> variable as shown below. Otherwise, the <varname>MANPATH</varname>
>> - variable is omitted.</para>
>> + <para>If your shell configuration sets a <varname>MANPATH</varname> variable,
>> + it should be edited to contain <filename>${prefix}/share/man</filename>.</para>
>>
>> <programlisting>export MANPATH=/opt/local/share/man:$MANPATH</programlisting>
>> -
>> - <para>Here are some examples of paths that contain empty values:</para>
>> -
>> - <simplelist>
>> - <member>/usr/share/man:</member>
>> - <member>:/usr/share/man</member>
>> - <member>/usr/share/man::/usr/X11R6/man</member>
>> - </simplelist>
>> </listitem>
>>
>> <listitem>
>> <para>Optional: <varname>DISPLAY</varname> variable</para>
>>
>> - <para>Condition: If installing on a Mac OS X version earlier than 10.5 (Leopard), and if a shell
>> - configuration file exists at time of MacPorts installation without a <varname>DISPLAY</varname>
>> - variable, the postflight script sets a <varname>DISPLAY</varname> variable as shown below. The
>> - <varname>DISPLAY</varname> variable is always omitted on Mac OS X 10.5 or higher.</para>
>> + <para>If installing on a Mac OS X version earlier than 10.5 (Leopard),
>> + a <varname>DISPLAY</varname> variable should be set as shown below.
>> + On Mac OS X 10.5 or higher, the <varname>DISPLAY</varname> variable is always omitted.</para>
>>
>> <programlisting>export DISPLAY=:0.0</programlisting>
>> </listitem>
>> @@ -487,7 +466,7 @@
>> </section>
>>
>> <section id="installing.shell.verifyprofile">
>> - <title>Verify the Configuration File</title>
>> + <title>Verify the Configuration</title>
>>
>> <para>To verify that the file containing the MacPorts variables is in effect, type <command>env</command> in
>> the terminal to verify the current environment settings after the file has been created. Example output
>>
>
>
> ------------------------------
>
> Message: 15
> Date: Wed, 22 Mar 2017 04:42:11 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Jan Stary <hans at stare.cz>
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: port diagnose fails on 10.6.8
> Message-ID: <705B6103-F5D6-4FDD-BE8A-3F376DC7EBF9 at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
>
>> On Mar 21, 2017, at 02:56, Jan Stary <hans at stare.cz> wrote:
>>
>> This is MacPorts 2.4.1 on a mac mini running 10.6.8.
>> 'port diagnose fails like this:
>>
>> Error: process_cmd failed:
>> Usage: xcode-select -print-path
>> or: xcode-select -switch <xcode_folder_path>
>> or: xcode-select -version
>> Arguments:
>> -print-path Prints the path of the current Xcode folder
>> -switch <xcode_folder_path> Sets the path for the current Xcode folder
>> -version Prints xcode-select version information
>> child process exited abnormally
>>
>> I am using XCode 3.2.6, the latest available fo 10.6.8.
>> Apparently, the xcode-select call has changed somehow.
>
> Yes. Please file a bug report.
>
>
>
> ------------------------------
>
> Message: 16
> Date: Wed, 22 Mar 2017 04:42:58 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: tome at qx.net
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: ffmpeg update fails
> Message-ID: <ED45C6BF-A9D7-496F-8577-19B57DACFCB5 at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
>
>> On Mar 20, 2017, at 21:12, tome at qx.net wrote:
>>
>> Mac mini 2.7Ghz Intel Core i7
>> 8 GB 1333 Mhz DDR3
>> Lion OS X 10.7.5
>> ffmpeg @3.1.4_0+gpl2+x11 (active)
>>
>> Attempting this update broke my ffmpeg. Port update was successful.
>> Please help.
>>
>> Thank you,
>> Tom<main.log>
>
> This is the libarchive build failure we already know about.
>
> https://trac.macports.org/ticket/53712
>
>
>
>
> ------------------------------
>
> Message: 17
> Date: Wed, 22 Mar 2017 09:45:18 +0000
> From: Chris Jones <jonesc at hep.phy.cam.ac.uk>
> To: macports-users at lists.macports.org
> Subject: Re: ffmpeg update fails
> Message-ID: <624b7f7c-56f9-04a0-ccbd-9e0e420c95c5 at hep.phy.cam.ac.uk>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
>
> you should search trac for known issues before posting to the list. In
> this case you would have found the long standing issue with libarchive
> on old OSX releases.
>
> https://trac.macports.org/ticket/53712
>
> On 21/03/17 02:12, tome at qx.net wrote:
>> Mac mini 2.7Ghz Intel Core i7
>> 8 GB 1333 Mhz DDR3
>> Lion OS X 10.7.5
>> ffmpeg @3.1.4_0+gpl2+x11 (active)
>>
>> Attempting this update broke my ffmpeg. Port update was successful.
>> Please help.
>>
>> Thank you,
>> Tom
>>
>
>
> ------------------------------
>
> Message: 18
> Date: Wed, 22 Mar 2017 04:47:31 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Dave Horsfall <dave at horsfall.org>
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <230094D6-5FAF-4915-AC54-8E341092CD3A at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
>
>> On Mar 21, 2017, at 16:23, Dave Horsfall <dave at horsfall.org> wrote:
>>
>> On Tue, 21 Mar 2017, Brandon Allbery wrote:
>>
>>> Never assume people will read instructions. How often do we get people
>>> who cut and paste the boilerplate at the end of a failed build that
>>> tells them to check the build log, and mail it here asking what they
>>> should do?
>>
>> Which reminds me: would it be possible to symlink to the log file from
>> somewhere in /tmp? It's a real PITA doing a C&P with a path that wraps
>> lines... Yes, I'm an old fogey, and use 80 columns...
>
> If I want to copy the logfile path, I usually use:
>
> port logfile thePort | pbcopy
>
>
>
> ------------------------------
>
> Message: 19
> Date: Wed, 22 Mar 2017 04:48:38 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Brandon Allbery <allbery.b at gmail.com>
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <E4DBE88B-EAF2-491F-8A0F-8F3EFD7FE635 at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
>
> On Mar 21, 2017, at 18:21, Brandon Allbery wrote:
>> On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery wrote:
>>> vim $(port logfile thePort)
>>
>> ...and the port you installed will usually get expanded with <esc>. (bash/zsh, in default emacs mode) so you don't even need to type that :)
>
> I'm not aware of this. Can you explain how to make this work?
>
> You mention "emacs mode"... I don't know what that is.
>
>
>
> ------------------------------
>
> Message: 20
> Date: Wed, 22 Mar 2017 06:41:40 -0400
> From: Brandon Allbery <allbery.b at gmail.com>
> To: Ryan Schmidt <ryandesign at macports.org>
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID:
> <CAKFCL4XHbzMT9QAjzNkw7sTueAfBqY5N7MHvXu+8M7t_H9Fp5w at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Wed, Mar 22, 2017 at 5:48 AM, Ryan Schmidt <ryandesign at macports.org>
> wrote:
>>
>> On Mar 21, 2017, at 18:21, Brandon Allbery wrote:
>>> On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery wrote:
>>>> vim $(port logfile thePort)
>>>
>>> ...and the port you installed will usually get expanded with <esc>.
>> (bash/zsh, in default emacs mode) so you don't even need to type that :)
>>
>> I'm not aware of this. Can you explain how to make this work?
>>
>
> That was a little unclear... escape key followed by period.
>
>
>> You mention "emacs mode"... I don't know what that is.
>>
>
> Unless you're disabling it for some reason, you have advanced line editing,
> generally via readline. (If the arrow keys work for history, you have it.)
>
> If control-p / control-n goes through history, you are in emacs mode.
> If pressing <esc> then using j and k goes through history, you are in vi
> mode.
>
> (It turns out that, for whatever reason, readline doesn't bind
> yank-last-arg in vi mode. :/ http://jasonwryan.com/blog/2011/12/01/readline/
> )
>
> --
> brandon s allbery kf8nh sine nomine associates
> allbery.b at gmail.com ballbery at sinenomine.net
> unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170322/0c13cec9/attachment-0001.html>
>
> ------------------------------
>
> Message: 21
> Date: Wed, 22 Mar 2017 05:51:20 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Jan Stary <hans at stare.cz>
> Cc: MacPorts Users <macports-users at lists.macports.org>, Jeremy
> Huddleston Sequoia <jeremyhu at macports.org>
> Subject: Re: all compilers blacklisted or unavailable
> Message-ID: <984F6BB7-AAF9-43B2-BA3A-A960848CC31B at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
> Jeremy, I'm Cc'ing you for input on wavpack; see the last few paragraphs.
>
>
> On Mar 21, 2017, at 03:37, Jan Stary wrote:
>
>> This is MacPorts 2.4.1 on MacOSX 10.6.8.
>> A build of audio/sox starts with the following warning:
>>
>> $ sudo port install -d sox
>
> Note that this "-d" does nothing. Single-letter flags like "-d" are global flags and only take effect when placed after the word "port" and before the action verb, e.g. "sudo port -d install sox". Multi-letter flags like "--enforce-variants" apply only to specific verbs, so they only take effect if you place them after the verb, e.g. "sudo port upgrade --enforce-variants someport +x11".
>
>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>> Warning: All compilers are either blacklisted or unavailable; defaulting to first fallback option
>> ---> Computing dependencies for sox
>> ---> Fetching archive for sox
>> ---> Attempting to fetch sox-14.4.2_0.darwin_10.x86_64.tbz2 from https://packages.macports.org/sox
>> ---> Attempting to fetch sox-14.4.2_0.darwin_10.x86_64.tbz2 from http://nue.de.packages.macports.org/sox
>> ---> Attempting to fetch sox-14.4.2_0.darwin_10.x86_64.tbz2 from http://lil.fr.packages.macports.org/sox
>> ---> Fetching distfiles for sox
>> ---> Verifying checksums for sox
>> ---> Extracting sox
>> ---> Applying patches to sox
>> ---> Configuring sox
>> ---> Building sox
>> ---> Staging sox into destroot
>> ---> Installing sox @14.4.2_0
>> ---> Activating sox @14.4.2_0
>> ---> Cleaning sox
>> ---> Updating database of binaries
>> ---> Scanning binaries for linking errors
>> ---> No broken files found.
>>
>> What "all compilers" are those? (I have Xcode 3.2.6)
>
> All compilers that are in the list of compilers that MacPorts will consider to build the port in question. It depends on the Xcode version and the macOS version and ports can modify the list if needed. It usually includes the version of clang provided by Xcode and newer versions of clang provided by MacPorts. With Xcode 4 and earlier, it also includes llvm-gcc-4.2, and with Xcode 3 and earlier, it also includes gcc-4.2. You can see the code that builds the default list here:
>
> https://github.com/macports/macports-base/blob/v2.4.1/src/port1.0/portconfigure.tcl#L474
>
>
>> Why are they blacklisted? Who blacklisted them?
>
> The author of the portfile determined that those compilers were unable to build this port.
>
>> Why are they unavailable? The gcc and clang from Xcode work just fine.
>
> There are a wide variety of reasons why code written for today's compilers might not work on last decade's compilers. As was mentioned, in some cases you can find a comment in the portfile that explains why a compiler is blacklisted. In other cases, you may have to go to the git history and read the commit message that added the blacklisting.
>
>> How do I get port(1) to print all this for me if -d doesn't?
>
> Using the debug flag properly (sudo port -d install sox) will give you the context to see which port is causing this warning, but it won't explain the reasons for the blacklisting; for that you'll have to explore the code.
>
>> WHy is the message printed twice?
>
> MacPort apparently evaluates this information twice for each port. I don't know why. Perhaps there is an opportunity for optimization here.
>
>
> As Daniel pointed out, the message applies not to sox itself but to its dependencies. (There's no way to know that by looking at the non-debug output, but after analysis, that's what's happening.) Even though you already have the dependencies installed, MacPorts will still evaluate the dependencies' portfiles and report any problems it runs into.
>
> Looking at all of sox's recursive dependencies, I see four ports that blacklist specific compilers:
>
> flac blacklists Xcode clang < 503 and MacPorts clang 3.3. The reason given in the Portfile is https://trac.macports.org/ticket/46038. You're on Snow Leopard where the default compiler is gcc-4.2 so that compiler will still get used.
>
> gettext blacklists Xcode clang < 211.10.1. The reason given is https://trac.macports.org/ticket/31167. Same as above, this doesn't mention gcc-4.2, so that still gets used on your system.
>
> libopus, on Intel systems, blacklists Xcode clang < 500 and all Xcode gcc compilers. The reason given is an error message "checking How to get X86 CPU Info... configure: error: no supported Get CPU Info method, please disable intrinsics". On your system, this means MacPorts clang 3.4 will get used.
>
> wavpack blacklists Xcode clang < 500, MacPorts clang 3.3 and 3.4, and all Xcode gcc compilers. This covers all of the compilers in the list on your system, hence the message that all compilers are blacklisted. When this happens, MacPorts prints the warning and then tries to build the port using the first compiler in the list, knowing that it will fail.
>
> No reason is given in the portfile, but looking at the git history, we see that wavpack used to disable its assembly code on Snow Leopard and earlier because the compilers couldn't handle it. Then, when build problems were discovered on Lion, this was changed to reenable the assembly code but blacklist the old compilers that couldn't handle it:
>
> https://github.com/macports/macports-ports/commit/0090d5f7bae96c92d19d297e955fb203e3231a41
>
> Then it was discovered that the port failed to build on Leopard (and presumably Snow Leopard) because all compilers were blacklisted:
>
> https://trac.macports.org/ticket/51357
>
> Jeremy initially considered adding newer MacPorts clang compilers to the fallback list, but thought this would have adverse consequences (a dependency on libc++), so instead he did something which I don't think I've seen done in any other port: he wrote code to detect if all compilers are blacklisted, and if so, disable assembly again:
>
> https://github.com/macports/macports-ports/commit/6fb35a1f2843454f08ef5027dfe0e3db59016d99
>
> In this way, the faster assembly code could be used if a compiler that understands it is found, otherwise assembly is disabled and the port can still build.
>
> This is clever, but I don't like that it causes MacPorts to print an inaccurate warning that clearly causes user confusion. I think we could fix the problem by having the port blacklist the compilers only when libc++ is in use (MacPorts base will then add newer clang compilers to the fallback list), and disable assembly when libstdc++ is in use.
>
>
>
>
>
> ------------------------------
>
> Message: 22
> Date: Wed, 22 Mar 2017 05:54:45 -0500
> From: Ryan Schmidt <ryandesign at macports.org>
> To: Brandon Allbery <allbery.b at gmail.com>
> Cc: MacPorts Users <macports-users at lists.macports.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <2A3A6CA0-D5B0-418C-B9AB-EDDAF2CF1D7C at macports.org>
> Content-Type: text/plain; charset=us-ascii
>
>
>> On Mar 22, 2017, at 05:41, Brandon Allbery <allbery.b at gmail.com> wrote:
>>
>> On Wed, Mar 22, 2017 at 5:48 AM, Ryan Schmidt <ryandesign at macports.org> wrote:
>> On Mar 21, 2017, at 18:21, Brandon Allbery wrote:
>>> On Tue, Mar 21, 2017 at 7:18 PM, Brandon Allbery wrote:
>>>> vim $(port logfile thePort)
>>>
>>> ...and the port you installed will usually get expanded with <esc>. (bash/zsh, in default emacs mode) so you don't even need to type that :)
>>
>> I'm not aware of this. Can you explain how to make this work?
>>
>> That was a little unclear... escape key followed by period.
>
> Ah, cool. Thanks.
>
> On MacBook Pro with Touch Bar, pressing Esc is a bit of an adventure so retyping the port name is probably less error prone for me.
>
>
>
>
> ------------------------------
>
> Message: 23
> Date: Wed, 22 Mar 2017 12:53:15 +0100
> From: Rainer Müller <raimue at macports.org>
> To: macports-users <macports-users at lists.macosforge.org>
> Subject: Re: Prevent MacPorts editing .bash_profile over and over
> again...
> Message-ID: <347bfaab-4acf-bfd9-80b3-b45fb97ef0d7 at macports.org>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> On 2017-03-21 21:43, Jan Stary wrote:
>> +echo "Remember to set your environment:"
>> +echo "Prepend ${BINPATH} and ${SBINPATH} to PATH."
>> +echo "Prepend ${MANPAGES} to MANPATH if you use MANPATH."
>> +echo "Remember to set DISPLAY if you are on 10.4 or older."
>> +echo "See https://guide.macports.org/#installing.shell for details."
>
> Where do you think users would see this? I am quite sure the installer
> does not show any output of the postflight script.
>
> Rainer
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macports.org
> https://lists.macports.org/mailman/listinfo/macports-users
>
> ------------------------------
>
> End of macports-users Digest, Vol 127, Issue 19
> ***********************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20170322/45d34657/attachment.html>
More information about the macports-users
mailing list