Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#36188 closed defect (fixed)

magic: magic/tclmagic.dylib did not get built

Reported by: rupapara.prashant@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.1.2
Keywords: Cc:
Port: magic

Description


Attachments (4)

main.log (89.8 KB) - added by rupapara.prashant@… 12 years ago.
main.2.log (5.1 KB) - added by rupapara.prashant@… 12 years ago.
main.3.log (1.5 KB) - added by rupapara.prashant@… 12 years ago.
main.4.log (10.2 KB) - added by rupapara.prashant@… 12 years ago.
terminal screen

Download all attachments as: .zip

Change History (15)

Changed 12 years ago by rupapara.prashant@…

Attachment: main.log added

comment:1 Changed 12 years ago by mf2k (Frank Schima)

Priority: HighNormal

The priority field is reserved for use by Macports team members.

comment:2 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned
Summary: magic :error:build org.macports.build for port magic returned: magic/tclmagic.dylib did not get builtmagic: magic/tclmagic.dylib did not get built

I believe I've solved this in r97859. It's a fascinating problem about which I'll probably write a message to the macports-dev mailing list. Please wait 30 minutes, then run "sudo port clean magic" and "sudo port selfupdate" and then try again. If it fails again, please attach the new main.log file and also the make.log file from inside the work directory (the directory printed by the command "port work magic").

Changed 12 years ago by rupapara.prashant@…

Attachment: main.2.log added

comment:3 Changed 12 years ago by rupapara.prashant@…

I did "sudo port clean magic" and "sudo port selfupdate" and then "sudo port install magic" but got different errors this time ..so also tries "sudo port install -d -k magic configure.compiler=llvm-gcc-4.2" but same error. attaching log file. please tell me what to do.

Changed 12 years ago by rupapara.prashant@…

Attachment: main.3.log added

comment:4 Changed 12 years ago by rupapara.prashant@…

I did it again after some time and now I got something else. attaching it.

Changed 12 years ago by rupapara.prashant@…

Attachment: main.4.log added

terminal screen

comment:5 Changed 12 years ago by rupapara.prashant@…

I dont know why this time it didn't create total log so I copy pasted terminal screen. Hope it will be useful

comment:6 Changed 12 years ago by rupapara.prashant@…

Hey , I uninstalled oregano which was using libgnome-keying and then uninstalled libgnome-keyring. after that I deactivated gnome-keyring. and "sudo port install -d -k magic configure.compiler=llvm-gcc-4.2". And it's done. It's installed and working.

Thanks for help ................

comment:7 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

main.2.log shows a problem fetching libxml2, which has nothing to do with the magic port.

main.3.log shows the gnome-keyring port not wanting to deactivate, because other ports depend on it. You could either force the deactivation ("sudo port -f deactivate gnome-keyring"), or do what you already did and first uninstall all ports that were using gnome-keyring.

main.4.log shows the same as main.3.log but in more detail.

You don't need to manually tell MacPorts to use llvm-gcc-4.2; I already told this port to do so in r97860.

So I'm glad it seems to be working for you as well.

comment:8 Changed 12 years ago by rupapara.prashant@…

Last edited 12 years ago by rupapara.prashant@… (previous) (diff)

comment:9 Changed 12 years ago by rupapara.prashant@…

Resolution: fixed
Status: closedreopened

comment:10 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: reopenedclosed

This ticket was about not being able to build magic. That issue was fixed. Your new issue with magic is being tracked in #36251.

comment:11 Changed 12 years ago by rupapara.prashant@…

ya ..sorry for this.. first I tried to reopen and try to type problem here. but it wasn't successful , so I opened new ticket.

Note: See TracTickets for help on using tickets.