Opened 12 years ago
Closed 12 years ago
#34839 closed defect (fixed)
log4cplus: build fails with clang
| Reported by: | simon.lehmann@… | Owned by: | macports@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.1 |
| Keywords: | clang | Cc: | ryandesign (Ryan Carsten Schmidt), vhaisman@… |
| Port: | log4cplus |
Description
Installing/building the log4cplus port on Mac OS X Lion fails with some linker errors. However, following the instructions on the ProblemHotlist page I could get it to build and install using gcc instead:
sudo port clean log4cplus sudo port install log4cplus configure.compiler=llvm-gcc-4.2
Attachments (1)
Change History (5)
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Keywords: | building gcc removed |
| Owner: | changed from macports-tickets@… to macports@… |
| Summary: | Building log4cplus on Mac OS X Lion fails with default compiler (llvm/clang) → log4cplus: build fails with clang |
Changed 12 years ago by simon.lehmann@…
Log file with build failures using clang
comment:2 Changed 12 years ago by vhaisman@…
This has been fixed/worked around in log4cplus 1.0.4.1. It is caused by misdetection of __declspec(dllexport)/__declspec(dllimport) support in Clang. See http://log4cplus.bzr.sourceforge.net/bzr/log4cplus/1.0.4.1/revision/924/m4/ax_declspec.m4 for the necessary change. I do not remember if there were not any other necessary Clang related changes.
comment:4 Changed 12 years ago by jmroot (Joshua Root)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
To clarify: the build failed with clang, and you were able to get it to work by using llvm-gcc (not gcc). It would be nice if you would attach the main.log file showing the build failure with clang.
It looks like newer versions (1.0.4, 1.0.4.1, 1.1.0) of log4cplus are available. We should try updating the port to one of those versions to see if it fixes this problem.