+1
Compiles and tests run under Debian 11. Signatures valid.
Note: we probably want to add some notes on the bugs fixed that were
found by fuzzing into the changelog.
-Robert Middleton
On Wed, Feb 26, 2025 at 4:00 AM Jan Friedrich
wrote:
>
> +1
>
> I verified the signatures and r
hould give it enough time to be pulled in to Debian
13.
-Robert Middleton
e, since it certainly goes against the spirit of semantic
versioning.
This change is better documented in a "migrate from 2.x to 3.x" page.
-Robert Middleton
On Sun, Jan 19, 2025 at 12:17 PM Piotr P. Karwasz
wrote:
>
> Hi Ralph,
>
> On 19.01.2025 17:55, Ralph Goers wrote:
> >
+1
Validated signatures and checksum. Compiled and tested cleanly on Debian 11.
-Robert Middleton
On Fri, Nov 29, 2024 at 5:06 PM Piotr P. Karwasz
wrote:
>
> Hi Stephen,
>
> On 28.11.2024 01:14, Stephen Webb wrote:
> > This is a vote to release the Apache Log4cxx 1.3.1.
>
I was going to suggest that anyway, so I'm all for it.
-Robert Middleton
On Thu, Nov 21, 2024 at 10:21 PM Stephen Webb wrote:
>
> Hi,
>
> I plan to cut Log4cxx 1.3.1 next week.
>
> Please let me know if there are any other urgent bugs to fix.
>
> Regards
> Stephen Webb
Thanks for getting the release out, it's good that we're getting more
automated about it.
-Robert Middleton
On Fri, Oct 18, 2024 at 2:12 AM Stephen Webb wrote:
>
> and here is my +1.
>
> With that the vote passed with 3 +1 votes from Piotr and Robert and myself.
> I
missing a few files that were in the 1.2.0
release, but those are all github/administrative files so it doesn't
cause an issue
Checksums/signatures are good
Builds and runs(tests pass) on Debian 11.
I checked the files from SVN
Looks good to me. +1
-Robert Middleton
On Tue, Oct 15, 2024 a
yocto
-Robert Middleton
On Tue, Oct 15, 2024 at 2:16 PM Volkan Yazıcı wrote:
>
> Mailing lists operate by modifying emails and this invalidates emails'
> checksum & signature – this is what I tried to explain in detail in my
> first email. There are "workarounds" (see Mailm
The source code is the same for all platforms, so we only need to run
it on one builder.
I took a brief look earlier, but I'm busy this weekend so I can take a
closer look next week.
-Robert Middleton
On Fri, Oct 11, 2024 at 2:10 PM Piotr P. Karwasz
wrote:
>
> Hi Stephen,
>
&
ecific, we also have log4cxx and log4net discussions
happening on here and we can to some extent share resources or
knowledge between the projects.
-Robert Middleton
On Thu, Oct 10, 2024 at 9:44 AM Volkan Yazıcı wrote:
>
> GitHub can be configured to send email notifications. We can route
Is there anything that people are looking for in a new release? We've
got a good bunch of changes ready, so I figure it's about time to do a
new release.
-Robert Middleton
I’ll check it out next week. The brief look that I did earlier looks good
though, good job Volkan!
-Robert Middleton
On Thu, Sep 19, 2024 at 8:08 AM Volkan Yazıcı
wrote:
> OSS-Fuzz <https://github.com/google/oss-fuzz> is a Google service that
> continuously runs fuzz tests of cr
remove the dormant
projects?
-Robert Middleton
There's nothing major going on at the moment, just some various
improvements to the code to make it more efficient. I'm not sure if
Stephen has anything else to add.
-Robert Middleton
On Tue, Apr 30, 2024 at 10:21 AM Volkan Yazıcı wrote:
>
> Can a Log4cxx maintainer share
+1
Verified the following:
* apache-log4net-source-2.0.16.zip and associated sha/signature
* apache-log4net-binaries-2.0.16.zip and associated sha/signature
It looks all good to me.
-Robert Middleton
On Tue, Mar 5, 2024 at 1:20 AM Ralph Goers wrote:
>
> +1
>
> Verified signature
I have no strong feelings either way. Turning on github discussions is a
good idea in my mind.
+0
-Robert Middleton
On Tue, Feb 13, 2024 at 12:45 PM Jan Friedrich
wrote:
> +1 from me
>
> Jan
>
> XA> +1.
> XA>
> XA> From: Matt
there is a concerted effort in the future to improve it by people
who do find it useful, I would definitely be open to looking at it
again.
-Robert Middleton
On Wed, Feb 7, 2024 at 2:56 AM Volkan Yazıcı wrote:
>
> +1
>
> Allow me to make some corrections:
>
> `XmlLayout` is dropp
d that archived documentation(since it is possible that some
behavior has changed between versions, and/or a newer API that you
want to use is not available with your version).
-Robert Middleton
On Wed, Feb 7, 2024 at 5:29 AM Piotr P. Karwasz wrote:
>
> Hi Volkan,
>
> On Wed, 7 Feb 2
Would people be in favor of enabling Github discussions for Log4cxx?
We don't get many reports, but we do occasionally get support
questions as issues.
INFRA needs to turn this on, there's no way for us to do it manually,
hence this question.
-Robert Middleton
The vote passes with +1 votes from Volkan, Piotr, Matt, and Stephen(in
the release review kit thread). I will continue with the release.
-Robert Middleton
On Fri, Dec 29, 2023 at 3:08 PM Matt Sicker wrote:
>
> +1
>
> Same checks as Volkan. Platform build info:
>
> cmake ve
Let me know if you want help on doing the build/test. Linux is the
easiest, OSX should be pretty easy, and Windows can be difficult. The
Github actions do a build and test for all 3 of those platforms.
-Robert Middleton
On Fri, Dec 29, 2023 at 4:04 AM Volkan Yazıcı wrote:
>
> I would
the website(under 'Development'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
If there aren't any objections, I will plan to do a release in a week
or so. I'm not aware of any issues that need to be fixed, so having a
new release for a new year seems like a good idea.
-Robert Middleton
On Mon, Nov 20, 2023 at 9:53 AM Robert Middleton wrote:
>
> It
r(according to my understanding) - I don't see any issue in
increasing the version number when you are not in one of those
scenarios. For example, the Linux kernel has a somewhat arbitrary
major number, since it doesn't really tell you what API the kernel
has(there is no stable interface inside of the kernel).
-Robert Middleton
.
-Robert Middleton
On Mon, Dec 11, 2023 at 11:15 AM Christian Grobmeier
wrote:
>
> Hi Volkan,
>
> I am not sure what you are proposing.
>
> On Mon, Dec 11, 2023, at 10:26, Volkan Yazıcı wrote:
> > I propose embracing a common versioning scheme across all Logging Services
> >
release? Since users should only be
interacting with the API, perhaps it makes sense to do core releases
more often than API releases, but that would mean committing to
allowing mismatched log4j-api and log4j-core versions.
-Robert Middleton
On Mon, Dec 4, 2023 at 5:04 PM Christian Grobmeie
It's been a bit over 6 months since the last release, is it time for a
new release? There aren't many new features that would impact a lot
of people, but a good number of maintenance fixes.
-Robert Middleton
Are the tests run on Windows through Github workflows? It doesn't
look like it to me.
If you need access to a Windows machine, you can download a
development VM straight from Microsoft:
https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
-Robert Middleton
On Mon, N
I suspect the settings are on a per-repo basis. Since this is a new
repo, it doesn't have the proper settings.
-Robert Middleton
On Wed, Nov 15, 2023 at 12:56 PM Matt Sicker wrote:
>
> Why do our email settings keep getting reset? Do we have some default
> settings somewhere?
&
quot; and then pass those
log messages up to other parts of chainsaw.
-Robert Middleton
On Tue, Oct 24, 2023 at 4:20 PM Matt Sicker wrote:
>
> If you use Log4j in Chainsaw, you could set up a JDBC appender or similar to
> forward things along. The Flume appender could be useful there,
g.a.o/log4j2? I ask because we would want to make
sure that redirects are added to try and avoid link rot.
-Robert Middleton
On Thu, Oct 19, 2023 at 6:05 AM Volkan Yazıcı wrote:
>
> > Every Git code repository uses a different staging domain name
>
> +1
>
> > The `asf-sta
ook things up - some sort of
visual programming/flow-based view would be very cool but also very
complicated.
-Robert Middleton
On Mon, Oct 9, 2023 at 3:24 PM Christian Grobmeier wrote:
>
> On Sun, Oct 8, 2023, at 23:19, Scott Deboy wrote:
> > I started but haven't had muc
es files. I think we can write our own reader/writer as well,
but ultimately I don't think that there is anything special that we
need that commons config doesn't provide us out of the box.
-Robert Middleton
On Mon, Oct 2, 2023 at 5:14 PM Matt Sicker wrote:
>
> Jackson makes
at least
two(maybe three) files. One was the xml config, one was a java serialized
map. Removing the java serialization is important.
-Robert Middleton
On Mon, Oct 2, 2023 at 6:12 AM Christian Grobmeier
wrote:
>
> On Mon, Oct 2, 2023, at 02:55, Robert Middleton wrote:
> > Some(m
save the data out.
-Robert Middleton
On Sun, Oct 1, 2023 at 3:39 PM Christian Grobmeier
wrote:
>
> On Sun, Oct 1, 2023, at 21:28, Scott Deboy wrote:
> > The ability to route events to tabs is a core feature in the code -
> > that's how Chainsaw log messages end up in
both the UI side(so you can know how things are routed) and on
the back-end side(to do the actual routing).
-Robert Middleton
On Sun, Oct 1, 2023 at 3:14 PM Christian Grobmeier
wrote:
> On Sun, Oct 1, 2023, at 20:59, Scott Deboy wrote:
> > It's great to see the contribution, thank
receivers are commented out because they depend on very
old versions of libraries, so it was easier to comment them out for the
time being rather than try to update them to newer dependencies.
-Robert Middleton
On Fri, Sep 29, 2023 at 6:14 PM Scott Deboy wrote:
> I think Robert commented
It starts up for me with Netbeans and OpenJDK 11. I would expect an
exception/stack trace to be printed to stderr if an exception was thrown
that caused it to fail to load.
-Robert Middleton
On Fri, Sep 29, 2023 at 9:17 AM Christian Grobmeier
wrote:
> Hi,
>
> I have found out
logging-chainsaw is not archived and contains the most up-to-date code.
The old 'chainsaw' repository has been archived.
-Robert Middleton
On Tue, Sep 26, 2023 at 5:57 PM Rob Tompkins wrote:
> Maybe we should un-archive it and run with it in a new direction?
>
> -Rob
>
&
erminal when new messages come in. Right-clicking will open up a
pop-up menu contextually depending on what it is you have clicked on(the
time, logger name, level, or the message).
Anyway, that's what I personally feel would be more useful, but I would
love to hear some other ideas.
-Robert
ant to see/think could be
useful/would want to try and code up?
-Robert Middleton
is much too busy to make it useful. I have been thinking
about how it could be re-done though, I do have some ideas that I can put
in a new thread.
Latest staging site for reference:
https://logging.staged.apache.org/chainsaw/2.2.0/
-Robert Middleton
On Fri, Sep 22, 2023 at 10:30 AM Scott Deboy
I think #1 is a mirror of SVN(
https://svn.apache.org/repos/asf/logging/chainsaw/trunk/), while #2 is a
mirror of the gitbox repository.
-Robert
On Thu, Sep 21, 2023 at 1:59 PM Volkan Yazıcı wrote:
> Does anybody know the difference between these two repositories[1][2]
> and why the mirroring d
to get it
to be in a reasonable state but I haven't yet found a need where chainsaw
is a good fit. I think there are some good ideas in there that can be
fleshed out more, but it has been largely dormant for several years at this
point.
-Robert Middleton
On Tue, Sep 19, 2023 at 2:52 PM Vladimir
They already go to the notifications list, is that not sufficient? I’m
pretty sure that’s how all of the jira notifications are setup.
-Robert Middleton
On Wed, Aug 23, 2023 at 4:15 PM Christian Grobmeier
wrote:
> Should Github notifications go to a separate list? I know there will
hat people who are coming into this for the first time have
similar problems getting started, since there are a large number of
ways to set it up.
-Robert Middleton
On Fri, Jul 7, 2023 at 4:05 PM Ralph Goers wrote:
>
> Funny you should ask.
>
> At the moment I am working on a more
Severity: 6.8
Affected versions:
- Apache Log4cxx 0.9.0 before 1.1.0
Description:
SQL injection in Log4cxx when using the ODBC appender to send log messages to a
database. No fields sent to the database were properly escaped for SQL
injection. This has been the case since at least version 0
Adding my +1.
With that, the vote officially passes with the +3 votes from me,
Piotr, and Volkan, with Thorsten and Steven adding their +1 as well.
I will proceed with the release.
-Robert Middleton
On Fri, May 5, 2023 at 2:04 PM Piotr P. Karwasz wrote:
>
> Hi Robert,
>
> On Thu
bsite(under 'Development'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
The release has been formally completed at this point; mirrors have
their copy of the official tar.gz file.
-Robert Middleton
On Fri, Jan 6, 2023 at 7:36 AM Tobias Frost wrote:
>
> On Mon, Jan 02, 2023 at 10:45:37PM -0500, Robert Middleton wrote:
> > Awesome! Thanks for the packagi
Adding my +1.
With that, the release passes with 3 binding votes from me, Volkan,
Remko, and two votes from Stephen and Thorsten.
Thanks to all for your work; I will send out the release notification shortly.
-Robert Middleton
On Fri, Jan 6, 2023 at 9:07 AM Volkan Yazıcı wrote:
>
&
Awesome! Thanks for the packaging work that you do. Once we get it
voted on you should have a proper release.
-Robert Middleton
On Mon, Jan 2, 2023 at 2:52 PM Tobias Frost wrote:
>
> Update:
>
> FTP masters have been very quick and approved the package, so the snapshot is
ist.apache.org/repos/dist/dev/logging/log4cxx/
Building directions are on the website(under 'Development'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
ince that follows what
we have been doing before. That lintian error is useful; now that I
know that you're getting that error, it makes sense to fix it on the
upstream end instead of having you fix that on yours.
-Robert Middleton
earlier it probably would be the same), but that's
part of this release to get it into a state where the versions and
SONAME should increment independently of each other.
Anyway, I'm going to do the following:
* Update the changelog for this new release
* Make sure the ABI dump is up to date(only needed for builds on
github, this is not in the release tarball)
* Merge next_stable into master and delete next_stable, so that master
becomes the new master
* Call a release vote
-Robert Middleton
Kevin,
I don't work on Log4net, but looking through the recent commits it
looks like this may have been fixed:
https://github.com/apache/logging-log4net/pull/92
I don't know if there is currently a timeline as to when this might be
officially released.
-Robert Middleton
On Thu, Dec 2
ly before I bumped it. I think I've done it correctly, but it
would be nice to have somebody double-check it. I arbitrarily bumped
it to version 15, skipping 14. The version of the SO file should also
now match the version of log4cxx, but that version is not the same as
the SONAME.
-Robert Middleton
e something in the compiler changed.
But it looks like that's on master, where what we're talking about
here is currently in the next_stable branch(which should have a
ridiculous number of ABI failures, but it should still be
source-compatible).
-Robert Middleton
ribution I
use), but that depends on Tobias' availability.
With that in mind, should we do a release in the immediate
future(within the next ~7 days), or should we wait a bit for some more
tweaking and/or features?
-Robert Middleton
[1]: https://lists.apache.org/thread/zg150rbkdkzgog1bnd403052818nncs7
ave to do that, especially
since the stacktrace is really only useful if you have a debug build.
Am I right in overthinking this? Is there something much simpler that
I'm missing?
-Robert Middleton
It looks like I was overcomplicating this. The constructor for a
std::chrono::time_point does take in a duration from the clock's
epoch, which is ultimately what we want to do.
PR up on github for review.
-Robert Middleton
On Sat, Nov 26, 2022 at 11:10 PM Stephen Webb wrote:
>
> F
is by setting
log4j.debug=true in your config file.
-Robert Middleton
On Wed, Nov 30, 2022 at 11:41 PM Eisenberg, Nathan
wrote:
>
> I have configured 2 loggers inside my java config file: 1 is the rootLogger
> and it has 2 appenders, and the other is called sender and it has 1 appender.
::system_clock instead of steady_clock.
-Robert Middleton
On Fri, Nov 25, 2022 at 11:03 PM Stephen Webb wrote:
>
> In Visual studio 2019 the line
>
> fmt::arg("d", event->getChronoTimeStamp()),
>
>
> causes the compile time error:
>
> error C2338: Cannot format
ebody with more experience on the Windows side be able to take a
look at it?
I suspect that this could also be something to do with the wchar on
Windows, but it is not clear to me if that is the case or not.
-Robert Middleton
rule of
thumb is to support whatever compiler the 'oldstable' version of
Debian uses(so anything released in the past ~5 years). RHEL has a
much longer release cycle; I believe RHEL 7(which is still supported
for at least 1.5 years) would only be able to be compiled with a C++11
com
I don't think any of those are too common, so it probably doesn't make
sense to do all of those combinations. The prefer_boost should be
effectively covered by the new build that compiles it in C++11 mode.
-Robert Middleton
On Thu, Oct 27, 2022 at 10:43 PM Stephen Webb wrote:
>
, it's fixed now. Are there any other configurations that we
should test for while I'm making updates?
-Robert Middleton
On Thu, Oct 27, 2022 at 1:37 AM Stephen Webb wrote:
>
> It works using a more recent version of vcpkg - not sure what the issue
> with the old version is.
would you be able to take a look at it
and figure out why it might be failing?
The branch in question:
https://github.com/apache/logging-log4cxx/tree/LOGCXX-562
-Robert Middleton
h Jira now.
I will plan on enabling the Github issues for Log4cxx sometime in the
next few days unless somebody strongly disagrees.
-Robert Middleton
On Sun, Oct 23, 2022 at 7:30 PM Matt Sicker wrote:
>
> Jira support is left in place for anyone who heavily relies on it already.
>
e amount of work required to create a
> release (it looks like a lot), I wonder if there are enough changes in
> master to justify the work of creating a release.
>
> On Tue, Sep 27, 2022 at 11:02 AM Robert Middleton
> wrote:
>
> > On Mon, Sep 26, 2022 at 5:09 AM Thorste
or message of "please
initialize the log4cxx system properly" which should probably print
out a bit more as to what it tried to do and why it failed.
-Robert Middleton
1], that's fine to do so it would not require an SONAME
bump.
[1]: https://community.kde.org/Policies/Binary_Compatibility_Issues_With_C%2B%2B
-Robert Middleton
an 0.13.1 release before the
end of the year and wait a bit on the next major version before we're
comfortable with it. Does anybody have any thoughts?
-Robert Middleton
I haven't tried it, but if you go to your settings for Github you can
set dependabot to not notify you.
That doesn't affect the notifications@ list of course.
-Robert Middleton
On Fri, Sep 23, 2022 at 7:47 PM Matt Sicker wrote:
>
> After secretary emails, emails related to De
get a
compiler error when you build, but a linker error. Option #2 would
cause a compiler error, but is not what we have been doing before.
-Robert Middleton
+1 from me - signatures and checksums look good. I didn't validate
anything else as I don't use .NET.
Note: You may want to not zip up the target/ directory, since that is
only for maven.
-Robert Middleton
On Fri, Jul 29, 2022 at 6:26 PM Ralph Goers wrote:
>
> But I jus
ow nothing about .net development.
-Robert Middleton
On Mon, Jul 25, 2022 at 5:45 AM Davyd McColl
wrote:
>
> Hi all
>
> It's been a while, but I've finally tied together some work in a 2.0.15
> release for log4net. An rc tag is up at GitHub with details:
> https://gith
+1
Notes:
* Copyright needs updating
* I did not check maven artifacts, only distribution archives.
* I did not test any code, I validated that signatures and checksums are good.
-Robert Middleton
On Fri, Jun 24, 2022 at 8:39 PM Matt Sicker wrote:
>
> Bump again.
> —
> Matt Sicker
s of these libraries that make them good.
Some of the terminology here could probably be better standardized, so
any suggestions are welcome! I may turn this into a presentation to
break it up as well, I haven't decided yet.
Github PR: https://github.com/apache/logging-site/pull/1
-Robert Middleton
It seems to me that this would only work if a) there exists a stable
API/ABI for log4j and b) sufficient demand for the appenders exists.
If a stable API/ABI doesn't exist, then the new maintainers would be
on the hook for any changes that log4j made, which seems unreasonable
to me.
-R
/latest_stable/0.12.0/, which of
course leads to a 404 error.
Is it useful to have the historical websites available? Or should we
keep the current behavior and always point to the newest website?
-Robert Middleton
Adding my +1
With that the release passes with binding +1 votes from Remko, Matt,
and me, and +1 votes from Stephen and Thorsten.
-Robert Middleton
On Sun, Apr 24, 2022 at 5:50 PM Matt Sicker wrote:
>
> +1
>
> Notes:
>
> * NOTICE file needs an updated copyright
> —
>
ist.apache.org/repos/dist/dev/logging/log4cxx/
Building directions are on the website(under 'Development'). Note
that APR is required to build(as well as boost if your compiler does
not support C++17).
-Robert Middleton
ing application with useless log messages(e.g. filter on
the log4j side instead of sending all messages to the log viewer and
filtering there).
-Robert Middleton
On Wed, Apr 6, 2022 at 3:14 AM Ralph Goers
wrote:
> I’m looking for some inspiration.
>
> At work we use Spring Cloud Config an
ping point.
-Robert Middleton
/tree/documentation-updates
The newest documentation is up on the staging site too:
https://logging.staged.apache.org/chainsaw/2.2.0/quicktour.html
-Robert Middleton
On Fri, Mar 4, 2022 at 6:30 PM Scott Deboy wrote:
> I'll check out your branch - there are a ton of features, I'll put
&g
ne if that would be a good
way to distribute chainsaw
-Robert Middleton
On Mon, Jan 17, 2022 at 2:02 PM Robert Middleton
wrote:
> Thanks for the input. In that case I will certainly make sure that we
> do keep the VFSLogFilePatternReceiver.
>
> One thing that would be helpful if yo
use it there
isn't really any good documentation.
-Robert Middleton
On Mon, Jan 17, 2022 at 1:17 AM Scott Deboy wrote:
>
> Looks great!
>
> It's a lot of work for sure - lots more to do to fully remove log4j1 -
> custom level support (java.util.logging and Android for e
g4j2 with a configuration file similar to the following:
?xml version="1.0" encoding="UTF-8"?>
You should then see log messages showing up in a new tab.
-Robert Middleton
On Tue, Dec 28, 2021 at 6:32 A
> I am tinkering with the idea of a Kickstarter-like initiative to sign up
> for this. Maybe as a 2-months-long gig?
>
That sounds like it could be a GSoC thing(if nobody else is
interested). The ASF has participated a number of times before.
-Robert Middleton
The Log4cxx JIRA is pretty clean at the moment - Thorsten went through
it a few months ago so there's not much (if anything) to do there.
-Robert Middetlon
On Fri, Jan 7, 2022 at 11:47 AM Matt Sicker wrote:
>
> I think this is a great idea. I'm sure we can find some dupes and link
> some other i
I've fixed everything to work properly at this
point.
What should our workflow be? Is there a better way? Obviously there
are certain things that would only target next_stable and not master,
so I'm not thinking about those cases for this.
-Robert Middleton
rs of the library unless you explicitly turn that off.
I'll add some documentation related to that.
-Robert Middleton
On Sun, Jan 2, 2022 at 8:07 AM Thorsten Schöning wrote:
>
> Guten Tag Robert Middleton,
> am Sonntag, 2. Januar 2022 um 02:38 schrieben Sie:
>
> > 2. Create
is
just a natural extension of that.
-Robert Middleton
On Sat, Jan 1, 2022 at 7:50 PM Stephen Webb wrote:
>
> I prefer option 2 if it is possible.
>
> I do not think it is useful to have the full path name (of the build
> directory) in shipped binaries.
>
> On Sun, Jan 2, 2
ilers
that don't support C++17, and only requires boost for older compilers.
-Robert Middleton
+1 to option 1
-Robert Middleton
On Wed, Dec 29, 2021 at 2:33 PM Christian Grobmeier
wrote:
>
> Hello,
>
> as discussed in another thread, this is a vote about the future of log4j 1.
> This vote stays open for the usual 72h.
> Options are explained below.
>
> You c
for us to load the required DLLs
from the PATH).
-Robert Middleton
On Wed, Dec 29, 2021 at 5:27 PM Stephen Webb wrote:
>
> That looks like a cmake issue - could you try cmake version 3.22?
>
> I am still using Visual Studio 2019 Community Edition.
>
> <https://www.avast.com/s
directory level issue that I
missed.
-Robert Middleton
On Wed, Dec 29, 2021 at 7:15 AM Thorsten Schöning wrote:
>
> Hi everyone,
>
> I just tried to run the throughput test: Installed FMT using VCPKG,
> changed CMAKE to option that test ON and things built successfully.
> Th
super consistent we should at least be able to get a rough
order of magnitude over dozens of builds.
-Robert Middleton
On Tue, Dec 28, 2021 at 7:30 AM Volkan Yazıcı wrote:
>
> Agreed with your remarks regarding the unreliability of benchmark results
> in the cloud. See my proposal in privat
1 - 100 of 245 matches
Mail list logo
