Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#46064 closed defect (wontfix)

Why does gcc48 depend on libgcc which is based on gcc49 which does not build on PPC Tiger and Leopard?

Reported by: ballapete (Peter "Pete" Dyballa) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.3
Keywords: Cc: mww@…
Port: gcc48

Description

The problem with gcc49/libgcc is reported in bug #45820.

I really would like to know why gcc48 has to be based on some foreign libgcc. What is this package good for? port info libgcc does not give me an answer and reports instead on gcc49 – and what this package is good for I do know.

Change History (3)

comment:1 in reply to:  description ; Changed 10 years ago by larryv (Lawrence Velázquez)

Resolution: → wontfix
Status: new → closed

Sorry, Trac isn’t a Q&A forum. Ask on macports-users or macports-dev. There are very good reasons for this setup.

Also, you have not answered my last question on #45820.

Closing as “wontfix” because we won’t be changing this.

comment:2 in reply to:  1 ; Changed 10 years ago by ballapete (Peter "Pete" Dyballa)

Replying to larryv@…:

Also, you have not answered my last question on #45820.

Because it takes days to compile gcc48, gcc49, or libgcc on a PowerBook! And since I have only one PPC based device I have to share it between Leopard and Tiger. So sometimes my reaction can be slowed down even more.

comment:3 in reply to:  2 Changed 10 years ago by larryv (Lawrence Velázquez)

Ah, no rush then.

Note: See TracTickets for help on using tickets.