Flaw in .deb Packaging

Alexander Perepelkin — Tue, 28 Oct 2025 22:35:05 -0000

Having the change suggested above in place causes the following error on at least system with uname
Linux 6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC
after running
~/log4cpp-codegit$ cmake --build build
CMake Error at CMakeLists.txt:89 (INSTALL):
INSTALL DIRECTORY given no DESTINATION!

The following amendment will fix the error:
https://sourceforge.net/p/log4cpp/codegit/ci/8db27fdc27a3b992b53ff433e91f205990ac87de/
Could you ensure that this fix will also work for your case please?
If not, then how it can be further changed to satisfy your case too?

Thanks.

Flaw in .deb Packaging

Alexander Perepelkin — Fri, 23 Aug 2024 20:45:55 -0000

The patch is released with log4cpp-1.1.5rc1 at https://sourceforge.net/projects/log4cpp/files/log4cpp-1.1.x%20%28new%29/log4cpp-1.1/log4cpp-1.1.5rc1.tar.gz/download

Flaw in .deb Packaging

Andrew E Page — Thu, 08 Aug 2024 18:10:26 -0000

both runs configured for an arm64 toolchain

root@a8b4e71c175e:/home/andrew/packages/log4cpp/build# make install
Consolidate compiler generated dependencies of target log4cpp
[100%] Built target log4cpp
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/include/log4cpp
-- Installing: /usr/local/include/log4cpp/StringQueueAppender.hh
...
-- Installing: /usr/local/include/log4cpp/BasicConfigurator.hh
-- Installing: /usr/local/lib/liblog4cpp.a
root@a8b4e71c175e:/home/andrew/packages/log4cpp/build#

after patching:

root@16e345bafce3:/home/andrew/packages/log4cpp/build# make install
Consolidate compiler generated dependencies of target log4cpp
[100%] Built target log4cpp
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/include/aarch64-linux-gnu/log4cpp
-- Installing: /usr/local/include/aarch64-linux-gnu/log4cpp/StringQueueAppender.hh
...
-- Installing: /usr/local/include/aarch64-linux-gnu/log4cpp/BasicConfigurator.hh
-- Installing: /usr/local/lib/aarch64-linux-gnu/liblog4cpp.a

Flaw in .deb Packaging

Alexander Perepelkin — Wed, 07 Aug 2024 09:40:45 -0000

Andrew E Page,

Thank you for this contribution.

Could you elaborate a bit more please?
Could you show what were the installation paths prior the fix (and after them, to compare them easily, and clearly see the clash)? For both x86/Arm64 compilations.

--
Alexander

segfault at log4cpp::threading::ThreadLocalDataHolder::freeHolder

Alexander Perepelkin — Thu, 24 Dec 2020 19:46:13 -0000

Hello,

Do you mind sharing the minimal project which I can run locally to reproduce the trouble?

Thanks for the reminder.

segfault at log4cpp::threading::ThreadLocalDataHolder::freeHolder

Gang Li — Mon, 21 Dec 2020 20:40:11 -0000

Feature request / idea - forced log write like .text(std::string Message)

Alexander Perepelkin — Wed, 02 Dec 2020 17:34:35 -0000

Hello Jes,

Could you please elaborate more on this " . text"?
What is its essential difference from usual lines logged with the code like
logger.info("Initialized ok"); ?

Thanks,
Alexander

Feature request / idea - forced log write like .text(std::string Message)

Jes — Wed, 02 Dec 2020 07:47:38 -0000

Hi.
I lack a feature to have a "forced" write of a log entry, basically a side-level thing that is called .text (or whatever)
I is for those messages that are not debug,info,warn,fatal etc. but rather plain informative of the application progress like .text("application has shut down gracefully"); or .text("initialization completed successfully");

I lack this feature so that when logging an application with ERROR level then i can get this visual signature of forced texts that with a glimpse let me determine if things has behaving normally for days up to crashes start to occur.

I can have a go at it if people find it worthy of acceptance....

Regarding log flooding issue in https://sourceforge.net/projects/log4cpp/

Alexander Perepelkin — Mon, 04 May 2020 11:23:37 -0000

I can suggest you the following solution if you wish the throttling be the part of logging subsystem:
create custom appender (or logger) class which will keep the logged data in memory and compare it with the data logged next. If test shows they are equal, then discard this message instead of writing it.

However, the same functionality might be implemented separately from the logging subsystem as well. In this case log4cpp would consume only single message which came out of throttler.

Alex.

Regarding log flooding issue in https://sourceforge.net/projects/log4cpp/

Alexander Perepelkin — Fri, 24 Apr 2020 11:02:25 -0000

HelloHelloHello

Do we have any feature in log4cpp project about log flooding occurance for perticular log?Hello

The loggers do not track the content which comes into appenders. Therefore they have no ability to throttle the message which comes too frequently.

I could suggest to build your own appenders which performs the throttling.

Alex.

Recent posts to Discussion

Flaw in .deb Packaging

Flaw in .deb Packaging

Flaw in .deb Packaging

both runs configured for an arm64 toolchain

after patching:

Flaw in .deb Packaging

segfault at log4cpp::threading::ThreadLocalDataHolder::freeHolder

segfault at log4cpp::threading::ThreadLocalDataHolder::freeHolder

Feature request / idea - forced log write like .text(std::string Message)

Feature request / idea - forced log write like .text(std::string Message)

Regarding log flooding issue in https://sourceforge.net/projects/log4cpp/

Regarding log flooding issue in https://sourceforge.net/projects/log4cpp/