Package Details: edfbrowser 2.09-1

Git Clone URL: (read-only, click to copy)
Package Base: edfbrowser
Description: A free, opensource, multiplatform, universal viewer and toolbox intended for, but not limited to, timeseries storage files like EEG, EMG, ECG, BioImpedance, etc.
Upstream URL:
Licenses: GPL
Submitter: cbrnr
Maintainer: cbrnr
Last Packager: cbrnr
Votes: 6
Popularity: 0.002247
First Submitted: 2016-07-21 11:40 (UTC)
Last Updated: 2024-04-10 07:06 (UTC)

Latest Comments

1 2 Next › Last »

cbrnr commented on 2023-06-01 07:14 (UTC)

I would like to automate this, but so far I haven't found a way to do this. Ideally, this package should be updated with every new release of EDFbrowser. However, I don't want to switch to a git package, but only follow proper releases.

Tabsc commented on 2023-05-31 14:09 (UTC)

The package seems to be out of date since its switch to 2.04 with a sha1sum to ac2610440fd3b92d4f0f56250f8d27e1376e175e.

Also I have a suggestion: why not switching to the gitlab repository since there is a tag for each new release. That might be easier (i.e. no need to update the sha1sum each time). Otherwise the sha256sum could be extracted from the website ?

ksnw commented on 2023-02-22 20:01 (UTC)

All good. Thanks for digging.

cbrnr commented on 2023-02-21 18:51 (UTC) (edited on 2023-02-22 09:07 (UTC) by cbrnr)

Apparently this has already been reported and fixed:

So we need to wait for the next release I guess. If you don't want to wait, you can modify your ~/.makepkg.conf and remove the offending flag (

cbrnr commented on 2023-02-21 16:55 (UTC)

Maybe I changed my /etc/makepkg.conf at some point, because this flag seems to be a relatively new default (see e.g. If that's the case then this needs to be fixed upstream. Can you report it and link the issue here?

ksnw commented on 2023-02-21 16:34 (UTC) (edited on 2023-02-21 16:48 (UTC) by ksnw)

To be safe, I removed /etc/makepkg.conf and reinstalled pacman, same error.

Inside /etc/makepkg.conf, the CFLAGS is set as CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \ -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security \ -fstack-clash-protection -fcf-protection"

meaning pacman turned on -Werror=format-security by default. I tried locally - turning this off does remove the compilation error. Did you turn it off manually?

cbrnr commented on 2023-02-21 07:07 (UTC)

My gcc flags are identical. Maybe you changed something in /etc/makepkg.conf?

ksnw commented on 2023-02-20 15:02 (UTC) (edited on 2023-02-20 15:05 (UTC) by ksnw)

Interesting. I don't think I tweaked any gcc setups, at least not intentionally. here is my gcc -v dump,

Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/12.2.1/lto-wrapper Target: x86_64-pc-linux-gnu Configured with: /build/gcc/src/gcc/configure --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++,d --enable-bootstrap --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl= --with-build-config=bootstrap-lto --with-linker-hash-style=gnu --with-system-zlib --enable-__cxa_atexit --enable-cet=auto --enable-checking=release --enable-clocale=gnu --enable-default-pie --enable-default-ssp --enable-gnu-indirect-function --enable-gnu-unique-object --enable-libstdcxx-backtrace --enable-link-serialization=1 --enable-linker-build-id --enable-lto --enable-multilib --enable-plugin --enable-shared --enable-threads=posix --disable-libssp --disable-libstdcxx-pch --disable-werror Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 12.2.1 20230201 (GCC)

cbrnr commented on 2023-02-20 14:49 (UTC)

That's really strange. I have exactly the same versions as you. And yes, my system is also completely up to date.

Did you set any additional compiler options by any chance? It looks like you set -Werror=format-security, which is not enabled by default.

ksnw commented on 2023-02-20 14:43 (UTC) (edited on 2023-02-20 14:44 (UTC) by ksnw)

ok... thanks anyways.

I updated with pacman -Syu without errors, and I assume you did the same. I also installed the base-devel, which was recently converted to meta from group. How is it possible that we are different versions of any dependency libraries?

Anyways, my systems is on gcc/gcc-libs 12.2.1-2, and glibc 2.37-2.

Does anybody else have compilation errors?