You can run dcraw_emu without parameters, and also have a look at https://www.libraw.org/docs/Samples-LibRaw.html
On a side note, exposure is measured in lux seconds.

dcraw (and, so, LibRaw) standard processing is 'auto-ETTR', there are a lot of option to change it.

> I’m assuming the next snapshot will add support for recently released cameras like Fuji X-T5, X-H2, Sony A7R5, etc
Please don't assume.

Are the release notes publicly accessible and do they offer a list of camera updates, by chance?

Hello. Are you able to provide an estimate for when the next snapshot will be (I’m assuming the next snapshot will add support for recently released cameras like Fuji X-T5, X-H2, Sony A7R5, etc)?

1-4-6 beta definitely works. Does this mean that the GH6 .RW2 format will be supported in the next version? Is there an ETA on that?

If a company like Affinity is using LibRaw as a part of their developing engine, what can I do to let them know it is ready to be incorporated?

I get the error "File://( file name here) decoded with errors. Broken file or unsupported file format."

I am an avid user of Affinity Photo and I am told that Affinity Photo uses LibRaw as an essential element to the processing and development of RAW images. I recently purchased a Panasonic Lumix GH6 and was curious if this might be on the docket for updates to the .RW2 raw file processing? Affinity Photo was able to support earlier versions of the .RW2 format (I believe the Lumix GH5mII uses the same extension .RW2). If there is anything I can do to somehow contribute to getting camera or file data samples of the GH6 .RW2 files, I would be happy to spend the time.

Check your version of autoconf and compare to AC_PREREQ in aclocal.m4. Try re-installing autotools if something doesn't work.
On my focal 20.04 LTS, following https://www.libraw.org/docs/Install-LibRaw.html

$ apt-cache policy pkg-config
pkg-config:
  Installed: 0.29.1-0ubuntu4...
$ apt-cache policy automake
automake:
  Installed: 1:1.16.1-4ubuntu6...
$apt-cache policy libtool
libtool:
  Installed: 2.4.6-14...
$ autoconf -V
autoconf (GNU Autoconf) 2.69....
$ cd
$ git clone https://github.com/LibRaw/LibRaw.git
$ cd LibRaw
$ autoreconf --install
$ ./configure
$ make
$ bin/raw-identify 
Usage: /home/ib/LibRaw/bin/.libs/raw-identify [options] inputfiles
Options:
	-v	verbose output
	-w	print white balance
	-u	print unpack function
	-f	print frame size (only w/ -u)
	-s	print output image size
	-h	force half-size mode (only for -s)
	-M	disable use of raw-embedded color data
	+M	force use of raw-embedded color data
	-L filename	read input files list from filename
	-o filename	output to filename

Yes, I checked that: automake-1.15

I will try to reinstall.

Thank you anyway for your quick reply!

Sorry, I was confused. Repeated it so many times that I got a bit lost. Here is what happens:

./configure seems to work

make produces some warnings and errors:

configure.ac:16: error: possibly undefined macro: AC_SUBST
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:41: error: possibly undefined macro: AC_MSG_WARN
make: *** [Makefile:651: configure] Fehler 1

ignoring these, sudo make install produces the aforementioned error:

configure: WARNING: libjasper not found
./configure: line 12807: syntax error near unexpected token `ZLIB,zlib,'
./configure: line 12807: ` PKG_CHECK_MODULES(ZLIB,zlib,'
make: *** [Makefile:648: config.status] Fehler 2

Thanks! Jan