Opened 14 years ago

Closed 14 years ago

#25173 closed defect (invalid)

gcc44 fails to build: pointer in read-only segment not allowed in slidable image, used in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)

Reported by: dmmonarres@… Owned by: mww@…
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: ryandesign (Ryan Carsten Schmidt)
Port: gcc44

Description

Attached a build log. Looks like it is failing at a link stage (maybe a problem with gmp?) while building gcj.

Attachments (1)

gcc44-error.log.bz2 (286.1 KB) - added by dmmonarres@… 14 years ago.
Debug Build Log

Download all attachments as: .zip

Change History (5)

Changed 14 years ago by dmmonarres@…

Attachment: gcc44-error.log.bz2 added

Debug Build Log

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

Cc: mww@… removed
Owner: changed from macports-tickets@… to mww@…

comment:2 Changed 14 years ago by jmroot (Joshua Root)

Summary: gcc4 fails to build: pointer in read-only segment not allowed in slidable image, used in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)gcc44 fails to build: pointer in read-only segment not allowed in slidable image, used in ___gmpn_divexact_1 from /usr/local/lib/libgmp.a(dive_1.o)

This shouldn't happen if you move /usr/local/lib/libgmp.a aside during the build. Obviously it would be better if the build system ignored /usr/local in the the first place, but getting it to do that may not be feasible.

comment:3 in reply to:  2 Changed 14 years ago by dmmonarres@…

Replying to jmr@…:

This shouldn't happen if you move /usr/local/lib/libgmp.a aside during the build. Obviously it would be better if the build system ignored /usr/local in the the first place, but getting it to do that may not be feasible.

ah yes. usually the first thing that i look for. thank you.

comment:4 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: ryandesign@… added
Resolution: invalid
Status: newclosed

Yeah, it's not supported to have anything in /usr/local while using MacPorts because it can cause conflicts like this.

Note: See TracTickets for help on using tickets.