[MacPorts] #51726: Gildas Install Fail

Ryan Schmidt ryandesign at macports.org
Fri Jul 1 03:18:28 PDT 2016


On Jun 30, 2016, at 4:54 AM, Sébastien Maret <sebastien.maret at icloud.com> wrote:
> 
> I don't think that "sudo gcc select" has an effect on the compiler which is used to build this port. There is a patch that forces the use of a specific version of the compiler (clang for C and C++ and gfortran for Fortran). 

You should reply to this topic by visiting the ticket URL in a web browser, not by sending an email.

>> Ticket URL: <https://trac.macports.org/ticket/51726#comment:10>


>> Le 30 juin 2016 à 11:40, MacPorts <noreply at macports.org> a écrit :
>> 
>> #51726: Gildas Install Fail
>> ------------------------+----------------------
>> Reporter:  jtb1435@…  |      Owner:  smaret@…
>>     Type:  defect     |     Status:  new
>> Priority:  Normal     |  Milestone:
>> Component:  ports      |    Version:  2.3.4
>> Resolution:             |   Keywords:
>>     Port:  gildas     |
>> ------------------------+----------------------
>> 
>> Comment (by bardeau@…):
>> 
>> Ok. So that's really a symbol issue. That's hard to debug without having
>> access to an identical machine and reproducing the bug. I see several
>> options, from easiest to more complicated:
>> 
>> 1) Use the MacPorts compilers, i.e.
>> sudo port select gcc mp-gcc5
>> This will change gcc and g++ from Apple LLVM ones to MacPorts ones. This
>> can be a problem for other software if they were relying precisely on the
>> Apple compilers. Note that this does not solve the issue, this circumvents
>> it by using another configuration. Once the compilers are changed, you
>> should rebuild gildas from scratch.
>> 
>> 2) Update the Apple compilers. You have Apple LLVM version 5.1
>> (clang-503.0.38), but I have 6.1. Compilers can be updated by updating
>> Xcode ( https://developer.apple.com/support/xcode/ ). However there is no
>> guarantee this solves the issue.
>> 
>> 3) Compile Gildas "by hand" (see
>> http://www.iram.fr/~gildas/dist/gildas.README section IV.2). The bug won't
>> disappear but we will will able to make some tests and iterate together.
>> 
>> As you prefer!
>> 
>> -- 
>> Ticket URL: <https://trac.macports.org/ticket/51726#comment:10>
>> MacPorts <https://www.macports.org/>
>> Ports system for OS X
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-dev



More information about the macports-dev mailing list