Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
jrun
@257
sorry wait.
yeah, that symbol is not there
this is the correct ebuild, it builds off v2.1.0 or whatever the actuall ebuild is called:
here is the list of files installed:
and libkres.pc:
Vladimír Čunát
@vcunat
I would certainly feel safer if the same set of variables was passed to both build an installation. It's enough to have them as environment variables, as make picks them automatically.
jrun
@257
vcunat: i'm trying without ${EPREFIX} at the build phase, is that what you mean?
vcunat: and still the same problem.
hmm, wait. i forgot about LDFLAGS at install phase.
Vladimír Čunát
@vcunat
Well, that point was unrelated to the missing symbol, really.
The toolchain is recent gcc, gnu ld, and some unusual system-wide CFLAGS/LDFLAGS?
jrun
@257
gcc: [1] x86_64-pc-linux-gnu-6.4.0 *
binutils: [1] x86_64-pc-linux-gnu-2.29.1 *
CFLAGS="-march=native -O2 -pipe"
CXXFLAGS="${CFLAGS}"
Vladimír Čunát
@vcunat
And some hardening flags, as I read.
But that's all fairly standard.
jrun
@257
not sure, i don't think so in fact.
where did you see them?
Vladimír Čunát
@vcunat
It's written in the ebuild :-)
What's the output of cc --version ?
jrun
@257
oh, that can be set via USE flags. it's not set on my system.
Vladimír Čunát
@vcunat
Ah, right got it :-D
You may apply something like
--- a/platform.mk
+++ b/platform.mk
@@ -55,7 +55,7 @@ else
                ifeq ($(UNAME),Linux)
                        LDFLAGS += -ldl
                endif
-               ifeq (GCC,$(shell $(CC) --version | grep -q '\<GCC\>' && echo GCC))
+               ifeq (GCC,$(shell $(CC) --version | grep -q '\<gcc\>' && echo GCC))
                        # Otherwise Fedora is making kresd symbols inaccessible for modules.
                        # Clang doesn't support this flag, so we hackily detect gcc.
                        BUILD_CFLAGS += -rdynamic
Or just add -rdynamic to CFLAGS.
I was being obtuse this evening.
I suppose case-insensitive match for "gcc" word will do it. Each platform has this string different, apparently, and so far I haven't found a better way of recognizing gcc from e.g. clang.
jrun
@257
hmm, not getting this:
not sure if it's related.
i didn't use your patch, yet. i'm appending cflags conditionally, i.e. if cc supports it.
Vladimír Čunát
@vcunat
And the file is missing?
jrun
@257
nope
Vladimír Čunát
@vcunat
Is it accessible by the user+group running kresd?
jrun
@257
hmm, permission problem i think
-rw-r----- 1 root root 3.3K Feb 21 12:37 /etc/knot-resolver/root.hints
-rw-r--r-- 1 root root 563 Feb 21 12:43 /etc/knot-resolver/root.keys
still not go
Vladimír Čunát
@vcunat
Hmm, our makefile is installing etc files with 0640. I have no clue why.
jrun
@257
i actully cp'ed it from /var/lib/knot-resolver/root.keys into /etc/knot-resolver
it's installing 0644, i don't know about the first case.
Vladimír Čunát
@vcunat
root.keys would better be writable by kresd
That's important for rfc5011 updates, unless you update the file by package manager for example.
jrun
@257
still no go:
-rw-r--r-- 1 kresd kresd 563 Feb 21 12:43 /etc/knot-resolver/root.keys
Vladimír Čunát
@vcunat
and ls -ld /etc/knot-resolver ?