New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #25258 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

gcc ports break after upgrading mpfr to 3.0.0

Reported by: jwiegley@… Owned by: vinc17@…
Priority: Normal Milestone:
Component: ports Version: 1.9.0
Keywords: Cc: mww@…, ryandesign@…, ram@…
Port: arm-elf-gcc, i386-elf-gcc, cgal, gcc40, gcc41, gcc42, gcc43, gcc44, gcc45, gcc46, gnat-gcc, upc, py25-mx-experimental, redland

Description

Last night I upgraded gcc45 to patchlevel 3. Today, I upgrade mpfr to 3.0.0. Doing the latter caused gcc45 to abort, since it was still looking for the older version of mpfr. I had to rebuild gcc45 before it would work again.

Change History

comment:1 Changed 3 years ago by ryandesign@…

  • Cc ryandesign@… added
  • Owner changed from macports-tickets@… to vinc17@…
  • Port changed from gcc45 to arm-elf-gcc, i386-elf-gcc, cgal, gcc40, gcc41, gcc42, gcc43, gcc44, gcc45, gcc46, gnat-gcc, upc, py25-mx-experimental, redland

Yup, mpfr @2.4.2-p1_0 provided /opt/local/lib/libmpfr.1.dylib while mpfr @3.0.0_0 provides /opt/local/lib/libmpfr.4.dylib. Everything that depends on mpfr needs a revbump now.

comment:2 Changed 3 years ago by ram@…

  • Cc ram@… added

Cc Me!

comment:3 Changed 3 years ago by jmr@…

  • Summary changed from gcc45 breaks after upgrading mpfr to 3.0.0 to gcc ports break after upgrading mpfr to 3.0.0

comment:4 Changed 3 years ago by ryandesign@…

Updated gcc46 in r68879.

comment:5 Changed 3 years ago by vinc17@…

Is it up to the maintainers of the ports in question to do the revbump?

comment:6 follow-up: ↓ 8 Changed 3 years ago by ryandesign@…

I would say it was up to you to do so, since you updated mpfr to version 3 which caused the breakage.

I will be updating gcc44 and maybe gcc43 anyway for other reasons shortly. The other ports can all receive simple revision bumps now IMHO.

comment:7 Changed 3 years ago by vinc17@…

OK, I've revbumped the remaining ports except gcc43 and gcc44 (to avoid 2 recompilations in a short period) in r68933.

comment:8 in reply to: ↑ 6 Changed 3 years ago by ram@…

Replying to ryandesign@…:

I will be updating gcc44 and maybe gcc43 anyway for other reasons shortly.

When are you planning on this as as just been bitten by this problem with gcc43 and gcc44?

comment:9 Changed 3 years ago by ryandesign@…

Has duplicate #25327.

comment:10 Changed 3 years ago by jmr@…

  • Status changed from new to closed
  • Resolution set to fixed

Since gcc43 and gcc44 have now been broken for a week, I rev bumped them in r69036. If the other changes go in soon, most unnecessary rebuilds can still be avoided.

Note: See TracTickets for help on using tickets.