Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FTBFS on armhf: symbol `fopen64' is already defined #54

Open
onlyjob opened this issue Apr 30, 2024 · 0 comments
Open

FTBFS on armhf: symbol `fopen64' is already defined #54

onlyjob opened this issue Apr 30, 2024 · 0 comments

Comments

@onlyjob
Copy link
Contributor

onlyjob commented Apr 30, 2024 •
edited
Loading

As reported in Debian, nocache FTBFS on armhf as follows:

cc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -c -o pageinfo.o pageinfo.c
sed 's!##libdir##!$(dirname "$0")!' <nocache.in >nocache
chmod a+x nocache
/tmp/ccsSPzHW.s: Assembler messages:
/tmp/ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined
guillemj added a commit to guillemj/nocache that referenced this issue Jun 10, 2024
@guillemj
Move wrappers into its own module
20b7b25 
This avoids polluting the module with system includes that can affect
how the wrapping function declarations are done, via remapping or
aliases that are outside our control.

This fixes building the project with LFS and time64 support enable.

Fixes: Feh#54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@onlyjob