Opened 11 years ago

Closed 11 years ago

#38157 closed defect (wontfix)

boost @1.52.0_1+no_single+no_static+python27: Build failure

Reported by: iwerris@… Owned by: adfernandes (Andrew Fernandes)
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: cooljeanius (Eric Gallager)
Port: boost

Description (last modified by larryv (Lawrence Velázquez))

After trying for a few hours I can't figure out why this isn't working. I'm running OS X 10.8.2.

The farthest I've been able to get is running :

sudo port clean boost
sudo port selfupdate
sudo port -d install boost

Which results in a failure and the attached log file...

Attachments (1)

main.log (844.0 KB) - added by iwerris@… 11 years ago.

Download all attachments as: .zip

Change History (7)

Changed 11 years ago by iwerris@…

Attachment: main.log added

comment:1 Changed 11 years ago by larryv (Lawrence Velázquez)

Description: modified (diff)
Keywords: boost removed
Owner: changed from macports-tickets@… to adfernandes@…
Summary: Boost will not complete installationboost @1.52.0_1+no_single+no_static+python27: Build failure

Thanks for the ticket. In the future, please Cc relevant port maintainers and use WikiFormatting in your ticket descriptions and comments.

comment:2 Changed 11 years ago by adfernandes (Andrew Fernandes)

There is an important thing to remember when debugging boost builds... and that is to swear loud and long. :-)

I went over your attached log file (thanks for attaching!) and could not find anything obvious. As you probably noticed, no error is given by the boost build system as to what failed, or why.

I do have one thing to suggest, though. I noticed that you are using a 32-bit build of MacPorts, even on 10.8.2. Boost has a history of failing on 32-bit Mac (#35172). That ticket was closed since gcc seemed to respect the -march flag. My guess is that clang does not, and something is getting messed up there.

Unfortunately, this is one of those "technically boost supports 32-bit builds on OS X", but given the number of bugs that have been reported, it's clear that they are never seriously tested (or in some cases, even built!) on 32-bit systems.

I realize that if you adjust your MacPorts arch flags to go to a 64-bit build it may entail a lot of port builds and reinstallations... but I can't see or think of anything else that might be the problem... sorry.

I'd appreciate if you replied either way (if you install 64-bit or not) so I can update this ticket, either way. Thanks!

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

Replying to adfernandes@…:

That ticket was closed since gcc seemed to respect the -march flag. My guess is that clang does not, and something is getting messed up there.

Clang does support -march (see its man page). Who’s to say that it does what you think it does, though. :P

comment:4 Changed 11 years ago by iwerris@…

Thanks for the speedy reply (as well as your work).

Commenting out the line 'build_arch i386' in /opt/local/etc/macports/macports.conf completely resolved the issue. After sitting through a massive recompilation I was able to successfully build boost.

Thanks again guys.

comment:5 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:6 Changed 11 years ago by adfernandes (Andrew Fernandes)

Resolution: wontfix
Status: newclosed

Thanks for the report! r103433.

Note: See TracTickets for help on using tickets.