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.

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

what happened to jemalloc? #165

Open
nigoroll opened this issue Aug 7, 2023 · 1 comment
Open

what happened to jemalloc? #165

nigoroll opened this issue Aug 7, 2023 · 1 comment

Comments

@nigoroll
Copy link
Member

nigoroll commented Aug 7, 2023

The way I read this repository, our deb builds should, except for some platforms, use jemalloc.

But when I unpack https://packagecloud.io/varnishcache/varnish60lts/packages/ubuntu/jammy/varnish_6.0.11-1~jammy_amd64.deb?distro_version_id=237, it does not look like it linked against it?

.../varnish_6.0.11-1~jammy_amd64$ ldd ./usr/sbin/varnishd
	linux-vdso.so.1 (0x00007ffd3f7e8000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f6e89301000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6e89222000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6e89041000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6e8903c000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f6e894e0000)
.../varnish_6.0.11-1~jammy_amd64$ sha256sum ./usr/sbin/varnishd
b49f009a7f6ebae31b8918dce8a4f2d10cd345e18e5ad380897aba7aa1665333  ./usr/sbin/varnishd

edit: I should have found #159 , sorry

@simonvik
Copy link
Contributor

Think this can be closed, the lto-changes got ported to 6.0-lts too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants