ImageMagick failure to install
Christopher Jones
jonesc at hep.phy.cam.ac.uk
Wed Dec 15 13:59:44 UTC 2021
Its never a good idea to force activation as you did below.
what you should do instead is is
sudo port -f deactivate libgcc11 libgcc
then install libgcc-devel
> On 15 Dec 2021, at 1:56 pm, VACCARI FRANCO <vaccari at units.it> wrote:
>
> So I did that, but a lot of messages care coming’s out,
>
> mm02:~ sudo port -f uninstall libgcc
> Password:
> ---> Unable to uninstall libgcc @5.0_0, the following ports depend on it:
> ---> gcc11 @11.2.0_0
> Warning: Uninstall forced. Proceeding despite dependencies.
> ---> Deactivating libgcc @5.0_0
> ---> Cleaning libgcc
> ---> Uninstalling libgcc @5.0_0
> ---> Cleaning libgcc
>
> mm02:~ sudo port install libgcc-devel
>
> ---> Computing dependencies for libgcc-devel
> ---> Fetching archive for libgcc-devel
> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2 from https://packages.macports.org/libgcc-devel
> ---> Attempting to fetch libgcc-devel-12-20211209_0.darwin_21.arm64.tbz2.rmd160 from https://packages.macports.org/libgcc-devel
> ---> Installing libgcc-devel @12-20211209_0
> ---> Activating libgcc-devel @12-20211209_0
> Error: Failed to activate libgcc-devel: Image error: /opt/local/include/gcc/c++/algorithm is being used by the active libgcc11 port. Please deactivate this port first, or use 'port -f activate libgcc-devel' to force the activation.
> Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_gcc-devel/libgcc-devel/main.log for details.
> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
> Error: Processing of port libgcc-devel failed
>
> mm02:~ sudo port -f activate libgcc-devel
>
> ---> Computing dependencies for libgcc-devel
> ---> Activating libgcc-devel @12-20211209_0
> Warning: File /opt/local/include/gcc/c++/algorithm already exists. Moving to: /opt/local/include/gcc/c++/algorithm.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/any already exists. Moving to: /opt/local/include/gcc/c++/any.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/array already exists. Moving to: /opt/local/include/gcc/c++/array.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/atomic already exists. Moving to: /opt/local/include/gcc/c++/atomic.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/auto_ptr.h already exists. Moving to: /opt/local/include/gcc/c++/backward/auto_ptr.h.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/backward_warning.h already exists. Moving to: /opt/local/include/gcc/c++/backward/backward_warning.h.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/binders.h already exists. Moving to: /opt/local/include/gcc/c++/backward/binders.h.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/hash_fun.h already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_fun.h.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/hash_map already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_map.mp_1639575707.
> Warning: File /opt/local/include/gcc/c++/backward/hash_set already exists. Moving to: /opt/local/include/gcc/c++/backward/hash_set.mp_1639575707.
> …
> …
> …
>
> tons of similar messages
>
> …
> …
>
> Warning: File /opt/local/lib/libgcc/libatomic.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libatomic.1.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libgcc_s.1.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgcc_s.1.1.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libgfortran.5.dylib already exists. Moving to: /opt/local/lib/libgcc/libgfortran.5.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libgomp.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libgomp.1.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libitm.1.dylib already exists. Moving to: /opt/local/lib/libgcc/libitm.1.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libobjc-gnu.4.dylib already exists. Moving to: /opt/local/lib/libgcc/libobjc-gnu.4.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libssp.0.dylib already exists. Moving to: /opt/local/lib/libgcc/libssp.0.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libgcc/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libgcc/libstdc++.6.dylib.mp_1639575707.
> Warning: File /opt/local/lib/libstdc++.6.dylib already exists. Moving to: /opt/local/lib/libstdc++.6.dylib.mp_1639575707.
> ---> Cleaning libgcc-devel
> • miniadmin at mm02:~
>
> After that I could install ImageMagick.
>
> So, should I happily disregard those warming messages?
>
> And, as I had previously installed gcc11, should I uninstall it and rather install gcc-devel? I’m afraid of mixing things up…
>
> Franco
>
>
>> On 15 Dec 2021, at 12:56, Christopher Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>
>>
>> Please remember to reply to list...
>>
>> No. do not do that.
>>
>> sudo port -f uninstall libgcc
>> sudo port install libgcc-devel
>>
>>
>>> On 15 Dec 2021, at 11:54 am, VACCARI FRANCO <vaccari at units.it> wrote:
>>>
>>> Ok, I’ll delete all what I installed up to now and restart from scratch. My concern is that some packages will force the install of libgcc and some others will require libgcc-devel. Will see and report the outcome...
>>>
>>> Thanks
>>>
>>> Franco
>>>
>>>
>>>> On 15 Dec 2021, at 12:51, Christopher Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>>>
>>>> Hi,
>>>>
>>>> gcc-devel is the (current) preferred gcc compiler on Apple silicon at the moment, as none of the released gcc versions are fully stable on this platform. gcc-devel requires libgcc-devel as its runtime. libgcc and libgcc-devel are interchangeable, so you should remove libgcc and allow libgcc-devel to be installed instead.
>>>>
>>>> Chris
>>>>
>>>>> On 15 Dec 2021, at 11:37 am, VACCARI FRANCO <vaccari at units.it> wrote:
>>>>>
>>>>> I’m configuring a new Mac Mini M1 running Mac OS 12.1 and Xcode 13.2, and installing the usual packages I need. When dealing with ImageMagick I get the following error:
>>>>>
>>>>> mm02:~ sudo port install imagemagick
>>>>> ---> Computing dependencies for ImageMagick
>>>>> Error: Can't install libgcc-devel because conflicting ports are active: libgcc
>>>>> Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug.
>>>>> Error: Processing of port imagemagick failed
>>>>> mm02:~
>>>>>
>>>>> I believe that deactivating libgcc would break packages already installed that depend on it. Is it so, or can I deactivate libgcc and later activate it again?
>>>>>
>>>>> Thanks
>>>>>
>>>>> Franco
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 1930 bytes
Desc: not available
URL: <http://lists.macports.org/pipermail/macports-users/attachments/20211215/207df2d0/attachment.bin>
More information about the macports-users
mailing list