Opened 2 months ago

Closed 2 months ago

Last modified 2 months ago

#69499 closed defect (duplicate)

m4 will not build/install on eMac running Leopard 10.5.8

Reported by: ilovecrts Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.9.1
Keywords: leopard Cc:
Port: m4

Description

I am getting errors installing m4 on my eMac running Leopard 10.5.8.

The error occurs when I install any version of py-numpy. In my case, I am trying to install py312-numpy. I was able to successfully install python312.

I captured my terminal output after installing m4 by itself to record the errors.

I also captured the m4.log file.

I will try to attach both files to this ticket.

Something in both captures seem to say a filename is too long, perhaps?

Thank you for your attention and your help!

Attachments (2)

main.log (115.7 KB) - added by ilovecrts 2 months ago.
Error log file for m4 installation as directed to by installation.
m4_terminal_errors.txt (1.8 KB) - added by ilovecrts 2 months ago.
Terminal output of installation

Download all attachments as: .zip

Change History (5)

Changed 2 months ago by ilovecrts

Attachment: main.log added

Error log file for m4 installation as directed to by installation.

Changed 2 months ago by ilovecrts

Attachment: m4_terminal_errors.txt added

Terminal output of installation

comment:1 Changed 2 months ago by kencu (Ken)

Resolution: duplicate
Status: newclosed

duplicate of #62994

please see that ticket for details and workarounds

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

Keywords: m4 emac 10.5.8 removed

comment:3 Changed 2 months ago by ilovecrts

I know this ticket is closed but I feel I should close the loop here.

My problem was with the super long directory path created during the m4 installation process. It was longer than what a terminal command could delete. The installation would fail.

I simply deleted the folder in Finder and reran "sudo port install m4". Installation and building completed and I now have m4 on my machine.

Thank you! :)

Note: See TracTickets for help on using tickets.