Error: Failed to build source-highlight: command execution failed

tom eee eeetom87 at gmail.com
Thu May 6 06:22:10 UTC 2021


I did this first:

0:56-43> /opt/local/bin/clang-mp-9.0 --version
clang version 9.0.1
Target: x86_64-apple-darwin11.4.2
Thread model: posix
InstalledDir: /opt/local/libexec/llvm-9.0/bin

For the last attempt to install source-highlight I did not include the '
configure.compiler=macports-clang-9.0' portion. So I did  the following and
got:

1:49-45> sudo port clean source-highlight
Password:
--->  Cleaning source-highlight
1:53-46> sudo port -s install source-highlight
configure.compiler=macports-clang-9.0
--->  Computing dependencies for source-highlight
--->  Fetching distfiles for source-highlight
--->  Verifying checksums for source-highlight
--->  Extracting source-highlight
--->  Configuring source-highlight
--->  Building source-highlight
--->  Staging source-highlight into destroot
--->  Installing source-highlight @3.1.9_0
--->  Deactivating source-highlight @3.1.8_2
--->  Cleaning source-highlight
--->  Activating source-highlight @3.1.9_0
--->  Cleaning source-highlight
--->  Updating database of binaries
--->  Updating database of C++ stdlib usage
--->  Scanning binaries for linking errors
--->  Found 18 broken files, matching files to ports
--->  Found 4 broken ports, determining rebuild order
You can always run 'port rev-upgrade' again to fix errors.
The following ports will be rebuilt:
 ffmpeg @3.2.4+gpl2+x11
 lcms @1.19
 dvdauthor @0.7.1
 wget @1.19.1+ssl
Continue? [Y/n]:

I think this means source-highlight is now OK, so I thought I would let you
know.  Now I am going to say yes to the continue question and move on to
whatever happens next.  Thank you very much for your help, patiences, and
understanding.
Tom

On Wed, May 5, 2021 at 9:53 PM Bill Cole <
macportsusers-20171215 at billmail.scconsult.com> wrote:

> On 2021-05-05 at 19:39:33 UTC-0400 (Wed, 5 May 2021 19:39:33 -0400)
> tom eee <eeetom87 at gmail.com>
> is rumored to have said:
>
> > /Developer is gone and Xcode 4.6.3 in service.  Still failing build.
> > See
> > attachment.  Thanks, Tom
>
> That log shows that you are back at the original problem, whose proposed
> solution was to force the use of a newer version of the clang compiler
> by running these:
>
>     sudo port clean source-highlight
>     sudo port -s install source-highlight
> configure.compiler=macports-clang-9.0
>
>
> However, I've lost track of whether we've actually solved the problem
> you hit the last time you tried that: a broken installation of
> clang-9.0. To make sure that problem is fixed, run this:
>
>     /opt/local/bin/clang-mp-9.0 --version
>
> That should put out something like this:
>
>     clang version 9.0.1
>     Target: i386-apple-darwin11.4.2
>     Thread model: posix
>     InstalledDir: /opt/local/libexec/llvm-9.0/bin
>
>
>
> > On Wed, May 5, 2021 at 5:14 PM Ryan Schmidt <ryandesign at macports.org>
> > wrote:
> >
> >>
> >>
> >> On May 5, 2021, at 12:19, tom eee wrote:
> >>
> >>> Second, I retried 'sudo port install source-light' with no success.
> >>> The
> >> main.log was very big, so I cut out a big portion of the middle and
> >> attached it to this email.
> >>
> >> The log still shows the same error described in
> >> https://trac.macports.org/ticket/59258 and shows that MacPorts still
> >> recognizes that you have Xcode 4.2.
> >>
> >> Deleting parts of logs can make it harder for us to help you. A
> >> better
> >> file size reduction choice is to compress the log.
> >>
> >>
> >>> Third, I downloaded Xcode 4.6.3 and when the opened dmg directed me
> >>> to
> >> install the Xcode in my Application folder, I checked for what was
> >> already
> >> there first, only to discover that I had Xcode 4.6.3 installed in the
> >> Application folder since 2013!  I then looked in the Developer folder
> >> and
> >> discovered Xcode 4.2 was there.  So I am confused about how to make
> >> Xcode
> >> 4.6.3 the version that MacPorts sees when it is doing it's thing and
> >> do I
> >> now have to do some update for Developer?
> >>
> >> The /Developer folder is obsolete. You can delete it. It is where
> >> Apple
> >> used to install Xcode and associated files, but sometime after Xcode
> >> 4.2
> >> they stopped doing that. Xcode now belongs in /Applications.
> >>
> >> You can use "xcode-select -print-path" to see what Xcode your system
> >> is
> >> configured to use. MacPorts will use this Xcode.
> >>
> >> Assuming it does not say the path is
> >> /Applications/Xcode.app/Contents/Developer, change it to that by
> >> running
> >> "sudo xcode-select -switch
> >> /Applications/Xcode.app/Contents/Developer"
> >>
> >> Then you can run "sudo port clean source-highlight" and try to
> >> install it
> >> again.
> >>
> >>
>
>
> --
> Bill Cole
> bill at scconsult.com or billcole at apache.org
> (AKA @grumpybozo and many *@billmail.scconsult.com addresses)
> Not Currently Available For Hire
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20210506/790e6e7c/attachment.htm>


More information about the macports-users mailing list