On 01/10/18 20:59, Lari Rasku wrote: > atril:/usr/local/lib/atril/3/backends/libepubdocument.so: undefined > symbol 'ftello64' > atril:/usr/local/lib/atril/3/backends/libepubdocument.so: undefined > symbol 'fseeko64' > atril:/usr/local/lib/atril/3/backends/libepubdocument.so: undefined > symbol 'fopen64' > > (atril:26401): AtrilDocument-WARNING **: Cannot load specified object > > (atril:26401): AtrilDocument-WARNING **: Cannot load backend > 'epubdocument' since file > '/usr/local/lib/atril/3/backends/libepubdocument.so' cannot be read. > > This is easy to fix with the following (crude) patch:
I forgot to mention that a patch isn't the only way to fix this: the atril source does define two feature test macros to gate the use of the 64-bit functions, IOAPI_NO_64 and USE_FILE32API, but I don't know what the preferred way to set them in a port Makefile would be. Adding CPPFLAGS=-DIOAPI_NO_64 to CONFIGURE_ARGS overrides the infrastructure-provided CPPFLAGS value and results in a broken build, whereas adding it to CONFIGURE_ENV just gets it overridden by the infrastructure-provided values in turn. In situations like this, is a patch like the above preferable to duplicating the default CONFIGURE_ARGS CPPFLAGS values in the port Makefile? But as Rafael suggested I'll also report this upstream.
