Arch Linux User Repository

ArchLinux Pi-hole is not officially supported by Pi-hole project. In case of bugs and malfunctions please DO NOT file a report upstream.

First of all check if the wiki (https://wiki.archlinux.org/index.php/Pi-hole) can help then ask here for assistance and tips.
When it will be excluded that the problem does not depend on ArchLinux we will file a bug upstream.

@max.bra Happy to help. Looks like -fcommon did the trick without a patch to the source itself.

@setboolean thanks for reporting: -Werror is not a first time problem, but linking error on multiple declarations it's not really that good...

So trying to compile any version >5.2 throws a lot of error during the build process aka fails miserably. But first things first, picture the *ihavenoideawhatiamdoing meme. Now that we are on the same page let the fun begin.

1. [warning: __builtin_strncpy ... -Wstringop-truncation] in src/dnsmasq_interface.c. Those are only warnings but will bring the build process to a halt because some genius thought it would be a good idea to set -Werror in src/CMakeLists.txt :(

Fix: Replace -Werror with -Wno-error in src/CMakeLists.txt. This tells the build process to go f* himself if it encounters any warnings.

Bonus Fix: One could also replace all instances of strncpy with strlcpy in src/dnsmasq_interface.c and get rid of the warning itself. Does it create other problems further down the road? I have no idea but it compiles without errors.

1. [/usr/bin/ld: CMakeFiles/FTL.dir/datastructure.c.o: ... multiple definition of `querytypes';] Apparently there exist multiple definitions of querytypes in src/datastructure.h and src/datastructure.c which makes no sense to me because I never wrote a line of "real" code in my life. Anyway according to some docs it is a big no no to declare something multiple times in different code files, bummer. But apparently you can mark a definition as external and then ... magically all is well. And that's exactly what we gonna do.

Fix: Replace const char *querytypes[TYPE_MAX]; with extern const char *querytypes[TYPE_MAX]; in src/datastructure.h. So querytypes will only be declared in datastructure.c and datastructure.h will use it from there. Thats at least how I understand it.

Disclaimer: This was a fun endeavour, but seriously I have no idea what i'am doing. Errors are gone and it compiles. Next step is putting together a package for testing.

@deemon - My install works as expected/no errors in the web UI. I do see a message that is similar on pihole -c:

|¯¯¯(¯)_|¯|_  ___|¯|___        Core: version is 
| ¯_/¯|_| ' \/ _ \ / -_)        Web: version is 5.2.
|_| |_| |_||_\___/_\___|        FTL: 
 ——————————————————————————————————————————————————————————
  Hostname: pihole             (Arch  )
    Uptime: 2 days, 05:15:36                                                                                                    
 Task Load: 0.00 0.00 0.00     (Active: 0 of 33 tasks)
 CPU usage: 0%                 (4x 1.5 GHz @ 56c)
 RAM usage: 10%                (Used: 182 MB of 2 GB)
 HDD usage: 10%                (Used: 5 GB of 57 GB)
  LAN addr: 10.0.3.200         (Gateway: 10.0.3.1)
   Pi-hole: Active             (Blocking: 0 sites)
 Ads Today: 0%                 (Total: 0 of 0)
Local Qrys: 0%                 (2 DNS servers)
   Blocked: FTL offline                                                                                                         
Top Advert:                                                                                                                     
Top Domain:                                                                                                                     
Top Client:

But pihole status is normal:

% pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled

Guessing it is something simple.

For some reason pihole -c does say:

   Blocked: FTL offline                                                                                                                                    
Top Advert:                                                                                                                                                
Top Domain:                                                                                                                                                
Top Client:                                                                                                                                                

but it seems to work just fine:

[deemon@Zen ~]$ pihole status
  [✓] DNS service is running
  [✓] Pi-hole blocking is Enabled
[deemon@Zen ~]$ systemctl status pihole-FTL.service 
● pihole-FTL.service - Pi-hole FTLDNS engine
     Loaded: loaded (/usr/lib/systemd/system/pihole-FTL.service; disabled; vendor preset: disabled)
     Active: active (running) since Sat 2020-11-21 17:48:27 EET; 6min ago
   Main PID: 731 (pihole-FTL)
      Tasks: 6 (limit: 19106)
     Memory: 13.6M
     CGroup: /system.slice/pihole-FTL.service
             └─731 /usr/bin/pihole-FTL no-daemon

nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M]  -> Blocked DNS queries: 174
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M]  -> Unknown DNS queries: 0
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M]  -> Unique domains: 374
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M]  -> Unique clients: 1
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M]  -> Known forward destinations: 1
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.838 731M] Successfully accessed setupVars.conf
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.840 731M] WARNING: Unable to write PID to file.
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.840 731M]          Continuing anyway...
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.840 731M] PID of FTL process: 731
nov   21 17:48:27 Zen pihole-FTL[731]: [2020-11-21 17:48:27.840 731/T737] Listening on port 4711 for incoming IPv4 telnet connections

I see there some problem -- WARNING: Unable to write PID to file. ou... and whats with the port 4711 telnet???

Thanks @max.bra for the swift help - both suggestions work.

hi BertVoegele, yes it need about 800MB for a successful compilation. cross-compile is sure the best way for speed too, but a little swap file should do the trick.

Doesn't build on RaspberryPi Model 1B (512MB) & gcc 10.2 - it seems to die on an OOM at compiling src/database/sqlite3.c, with both processes (cc & as) using approx. 470 MB at the end. While trying different CC flags in makepkg.conf, I found them to be ignored in that build process. Is that pkg even intended to be built natively on that HW, or is cross-compile the way to go here?

Many Thanks for you swift guidance @Max.

@Prakkie glad you solved.
Don't understand why you can't switch css to the dark one...