Git Product home page Git Product logo

Comments (8)

michael-grunder avatar michael-grunder commented on June 23, 2024 1

Do you get the same error without USE_REDIS_SYMLINKS=no

No that also solves the problem which does seem weird.

Interestingly when you include USE_REDIS_SYMLINKS=no the second build does far more work. Basically a complete rebuild without respect to the previously built deps. Perhaps this is actually related to the .make-settings cache.

from valkey.

zuiderkwast avatar zuiderkwast commented on June 23, 2024 1

Interestingly when you include USE_REDIS_SYMLINKS=no the second build does far more work. Basically a complete rebuild without respect to the previously built deps. Perhaps this is actually related to the .make-settings cache.

Yeah, that's it! That USE_REDIS_SYMLINKS variable sets some macro in CFLAGS! We can remove that. We don't need to set that macro in CFLAGS.

See here: https://github.com/valkey-io/valkey/pull/193/files#diff-1abc5651133d108c0c420d9411925373c711133e7748d9e4f4c97d5fb543fdd9R7008

from valkey.

zuiderkwast avatar zuiderkwast commented on June 23, 2024 1

@furai Workaround: Use USE_REDIS_SYMLINKS=no in make and in make install.

from valkey.

furai avatar furai commented on June 23, 2024 1

Workaround worked for me, thanks!

from valkey.

michael-grunder avatar michael-grunder commented on June 23, 2024

The problem is that the BUILD_TLS env var being pulled from .make-settings doesn't propagate to the dep build.

It's fixable by appending this after -include .make-settings in src/Makefile:

export BULD_TLS

I'm not sure if that's the right/clean way to fix it though.

from valkey.

zuiderkwast avatar zuiderkwast commented on June 23, 2024

@michael-grunder What does this has to do with USE_REDIS_SYMLINKS=no?

from valkey.

michael-grunder avatar michael-grunder commented on June 23, 2024

@zuiderkwast Nothing, I don't think anyway.

The build was failing because the second invocation of make rebuilt hiredis but without forwarding BUILD_TLS=yes to the dep makefile so Valkiey builds expecting libhiredis_ssl.a but hiredis doesn't build it.

Making the above change fixes the linker error. Isn't USE_REDIS_SYMLINKS just so we symlink redis-server instead of valkey-server, etc?

from valkey.

zuiderkwast avatar zuiderkwast commented on June 23, 2024

Isn't USE_REDIS_SYMLINKS just so we symlink redis-server instead of valkey-server, etc?

Yes, but it seemed to be part of the problem.

@furai Do you get the same error without USE_REDIS_SYMLINKS=no?

from valkey.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.