Opened 12 years ago

Closed 12 years ago

#38184 closed defect (fixed)

pdf2djvu @0.7.16, Revision 1 +compiler error: segmentation fault

Reported by: kalebmckale Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.1.3
Keywords: Cc: NicosPavlov
Port: pdf2djvu

Description (last modified by ryandesign (Ryan Carsten Schmidt))

System Configuration:
  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro4,1
  Processor Name:	Intel Core 2 Duo
  Processor Speed:	2.5 GHz
  Number Of Processors:	1
  Total Number Of Cores:	2
  L2 Cache:	6 MB
  Memory:	4 GB

  System Version:	Mac OS X 10.6.8 (10K549)
  Kernel Version:	Darwin 10.8.0
  Secure Virtual Memory:	Enabled
  64-bit Kernel and Extensions:	Yes

MacPorts version 2.1.3

Notes: attached is the log file for the error. the error begins with the line

:info:build pdf2djvu.cc: In function ‘void _ZL5xmainiPKPc.omp_fn.0(void*)’:
:info:build pdf2djvu.cc:1373: internal compiler error: Segmentation fault

Attachments (1)

main.log (79.5 KB) - added by kalebmckale 12 years ago.

Download all attachments as: .zip

Change History (13)

Changed 12 years ago by kalebmckale

Attachment: main.log added

comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Submit a bug report to Apple, like the instructions in the log say to do. To work around it, try compiling with a different compiler.

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

Description: modified (diff)
Keywords: pdf2djvu snow leopard segmentation fault removed

Oh sorry, I see now you're on an old OS, using an old compiler Apple won't care about anymore. In that case, try using configure.compiler=llvm-gcc-4.2 or configure.compiler=clang. If that doesn't work, try a newer clang port in MacPorts, like clang-3.2.

comment:3 in reply to:  2 ; Changed 12 years ago by kalebmckale

Replying to ryandesign@…:

Oh sorry, I see now you're on an old OS, using an old compiler Apple won't care about anymore. In that case, try using configure.compiler=llvm-gcc-4.2 or configure.compiler=clang. If that doesn't work, try a newer clang port in MacPorts, like clang-3.2.

I'm somewhat terminal experienced. However, I'm not sure where to enter the configuration changes in the command line. Sorry. :(

comment:4 in reply to:  3 Changed 12 years ago by kalebmckale

Replying to kdmckale@…:

Replying to ryandesign@…:

Oh sorry, I see now you're on an old OS, using an old compiler Apple won't care about anymore. In that case, try using configure.compiler=llvm-gcc-4.2 or configure.compiler=clang. If that doesn't work, try a newer clang port in MacPorts, like clang-3.2.

I'm somewhat terminal experienced. However, I'm not sure where to enter the configuration changes in the command line. Sorry. :(

I found what I was looking for. Thanks!

comment:5 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)

Did a different compiler work?

comment:6 Changed 12 years ago by NicosPavlov

For the sake of comparison, I checked back the logs of the buildbot, and the SL one built fine pdf2djvu.
However, there is a difference between the two logs. In the case here, pdf2djvu uses openmp which happens to be installed. As the openmpi requires a specific compiler (by default gcc45), this may be the cause of the build error with gcc42 which is the one employed in the log.

Obviously, I will have some cleanup to do in the pdf2djvu port in order to avoid opportunistic linking and/or consider openmp as a dependency.

comment:7 Changed 12 years ago by NicosPavlov

I disabled openmp from pdf2djvu in r103396. Hopefully it should fix compilation in this case.

comment:8 in reply to:  5 Changed 12 years ago by kalebmckale

Replying to ryandesign@…:

Did a different compiler work?

Yes. I upgraded to the newest clang.

comment:9 in reply to:  6 ; Changed 12 years ago by kalebmckale

I have gcc45 installed. I just did not know what the compiler option was to make it use it since it was neither from Apple nor installed via MacPorts.

Replying to nicos@…:

For the sake of comparison, I checked back the logs of the buildbot, and the SL one built fine pdf2djvu.
However, there is a difference between the two logs. In the case here, pdf2djvu uses openmp which happens to be installed. As the openmpi requires a specific compiler (by default gcc45), this may be the cause of the build error with gcc42 which is the one employed in the log.

Obviously, I will have some cleanup to do in the pdf2djvu port in order to avoid opportunistic linking and/or consider openmp as a dependency.

comment:10 in reply to:  9 Changed 12 years ago by NicosPavlov

Replying to kdmckale@…:

I have gcc45 installed. I just did not know what the compiler option was to make it use it since it was neither from Apple nor installed via MacPorts.

Macports discourages the use of external compilers, and has its own gcc45, that you may have too. The compiler can be chosen through the variable configure.compiler.

Just in order to know if this issue is fixed, did pdf2djvu @ 0.7.16 Revision 2 build fine without the need of specifying any compiler ? It should be the case, but I would like to have confirmation before closing the ticket.

comment:11 Changed 12 years ago by kalebmckale

That I cannot answer since I had already installed it using the suggestion to install specifying clang and using a newer version of clang.

comment:12 Changed 12 years ago by NicosPavlov

Resolution: fixed
Status: newclosed

Alright, understandable.

I'll consider the issue fixed at least for now, since I could install pdf2djvu with openmpi installed and with the command

sudo port install pdf2djvu configure.compiler=apple-gcc-4.2

which should be equivalent to the configuration described in the bug.

Note: See TracTickets for help on using tickets.