Skip to content

configure --disable-rt doesn't work #16932

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
Closed
bagder opened this issue Apr 3, 2025 · 1 comment
Closed

configure --disable-rt doesn't work #16932

bagder opened this issue Apr 3, 2025 · 1 comment
Labels
build

Comments

@bagder
Copy link
Member

bagder commented Apr 3, 2025

I did this

./configure --disable-rt --with-openssl
...
checking for gcc options needed to detect all undeclared functions... none needed
checking whether fseeko is declared... yes
checking how to set a socket into non-blocking mode... fcntl O_NONBLOCK
checking for perl... /usr/bin/perl
checking whether to enable the threaded resolver... yes
configure: error: options --enable-pthreads and --disable-rt are mutually exclusive

I expected the following

It should just work as on Linux there's no need for -lrt anyway.

Maybe we should just drop the --disable-rt option?

curl/libcurl version

git master

operating system

Debian unstable
@bagder bagder added the build label Apr 3, 2025
bagder added a commit that referenced this issue Apr 3, 2025
@bagder
configure: fix --disable-rt
a0a0fd5 
This option now better only prevents the actual -lrt to be used, and
thus has no effect if the system does not need -lt for the monotonic
clock etc.

Fixes #16932
@bagder bagder mentioned this issue Apr 3, 2025
Closed
@bagder
Copy link
Member Author

bagder commented Apr 3, 2025

Found by running my "randdisable" script.

@bagder bagder closed this as completed in 6e00db5 Apr 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

configure: fix --disable-rt curl/curl
1 participant
@bagder