Bug 228607
| Summary: | [UPDATE PORT] devel/log4cxx: signed char issues | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | waitman | ||||
| Component: | Individual Port(s) | Assignee: | Steve Wills <swills> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Some People | ||||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
I'm a little confused, this seems to be building OK as is: http://beefy12.nyi.freebsd.org/data/head-amd64-default/p474051_s336054/logs/log4cxx-0.10.0_16.log Where are you seeing issues? (In reply to Steve Wills from comment #1) ports r473831 added -Wno-c++11-narrowing to CXXFLAGS in lieu of patching any files. I think this can be closed. |
Created attachment 193841 [details] svn diff changed Makefile, patch files build of port fails b/c it is cramming unsigned chars in signed char structure, should be fixed upstream but project appears abandoned. this patch allows the port to build and basically it's the same issue it's had for at least a decade. I think this probably relates to java not having unsigned chars (AFAIK) and log4cxx is a copy from the java library. (although i'm not a java person, i might be wrong about that)