Arch Linux User Repository

@dreieck: I got the same error. To me, writing 1 byte into a region of size 0 looks like a scary bug, and the fact that LTO stumbles over it prompted me to try turning this off first. But the real issue and why it is not flagged without LTO merit further investigation.

I think somewhere an option -Wno-error=stringop-overflow= or just a general -Wno-error needs to be explicitly added to the gcc options (i.e. the CFLAGS/ CXXFLAGS). I get a -Werror=stringop-overflow= compilation error, and I have not set manually any -Werror option:

gcc -Wall  -Werror  -g0 -march=x86-64 -mtune=native -O3 -flto -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -fomit-frame-pointer -fPIC  -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o bjnp bjnp-bjnp.o bjnp-bjnp-runloop.o bjnp-bjnp-io.o bjnp-bjnp-debug.o bjnp-bjnp-utils.o bjnp-bjnp-discover.o bjnp-bjnp-commands.o bjnp-bjnp-levels.o -lcups 
In function ‘bjnp_backendGetDeviceID’,
    inlined from ‘bjnp_backendRunLoop’ at bjnp-runloop.c:256:29,
    inlined from ‘main’ at bjnp.c:394:18:
bjnp-io.c:505:31: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
  505 |     device_id[device_id_size] = '\0';
      |                               ^
bjnp-runloop.c: In function ‘main’:
bjnp-runloop.c:74:10: note: at offset 1024 into destination object ‘dev_id’ of size 1024
   74 |     char dev_id[BJNP_IEEE1284_MAX];       /* IEEE1284 device id */
      |          ^
In function ‘bjnp_backendGetDeviceID’,
    inlined from ‘bjnp_backendRunLoop’ at bjnp-runloop.c:256:29,
    inlined from ‘main’ at bjnp.c:394:18:
bjnp-io.c:508:33: error: writing 1 byte into a region of size 0 [-Werror=stringop-overflow=]
  508 |     make_model[make_model_size] = '\0';
      |                                 ^
bjnp-runloop.c: In function ‘main’:
bjnp-runloop.c:73:10: note: at offset 64 into destination object ‘model’ of size 64
   73 |     char model[BJNP_MODEL_MAX];           /* printer make & model */
      |          ^
lto1: all warnings being treated as errors
lto-wrapper: fatal error: gcc returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed

For me the problem was mitigated with adding

  CFLAGS+=' -Wno-error'
  CXXFLAGS+=' -Wno-error'
  export CFLAGS
  export CXXFLAGS

before the ./configure call.

Btw., I could compile it with LTO.

Thanks for maintaining!

Compilation fails with LTO enabled (which is the default, at least on my system). A workaround is to add the line "options=('!lto')" to the PKGBUILD.

Compiling on GCC 8.1+ is fixed, many thanks to @ThoSTe and sorry for the delay.

When I try to install the package I get a compile warning/error. (https://bbs.archlinux.org/viewtopic.php?id=247748)

This can be avoided by disabling Werror complie option in PKBUILD ./configure --prefix='/usr' --disable-Werror