Just found this note in freebsd-gnome: ~~~ NOTE: When building with gcc from ports on i386, CPUTYPE must be set to a value that specifies an architecture that has 8 byte atomic op support (i686 or higher?). If CPUTYPE is not set, the build will fail with an undefined reference to __atomic_fetch_add_8. ~~~
Cheers, Ondrej -- Ondřej Surý -- Technical Fellow -------------------------------------------- CZ.NIC, z.s.p.o. -- Laboratoře CZ.NIC Milesovska 5, 130 00 Praha 3, Czech Republic mailto:[email protected] https://nic.cz/ -------------------------------------------- ----- Original Message ----- > From: "Leo Vandewoestijne" <[email protected]> > To: "knot-dns-users" <[email protected]> > Sent: Monday, 26 June, 2017 12:23:36 > Subject: Re: [knot-dns-users] problem with Knot 2.4.0 on FreeBSD 10.3 and > 11.0 - i386 > Hello, > > > > [atomic]: > I'm still having the problem: > http://beefy10.nyi.freebsd.org/data/110i386-default/444089/logs/knot2-2.4.3.log > > I tried to solve the problem, but when upgrading to 2.5.1 I marked it broken > for > i386. > Meanwhile, after this problem: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220241 > I've upgraded the port to 2.5.2. > Now when I test explicit with gcc or clang I still get atomic issues on i386. > > > [libknot]: > The cascading result is knot-resolver also doesn't install (on i386), > since it's depending on knot2 to install libknot. > > So, I in my dev env I made a seperate port for libknot that would use knot2 > distro; > that installs on i386 without atomic issues, and so i386 users would be able > install knot-resolver again. > > But it's a bit complicated to avoid collisions with these two (or actually > three) > when using both knot2 and knot-resolver (or removing knot2 and keeping > knot-resolver). > > So before I continue in making a meta-port or the knot2 port, just for the > sake > of libknot, > I'm wondering; > wouldn't other OS'es packaging systems not benefit from having libknot > seperate > from knot? > > > -- > > Met vriendelijke groet, > With kind regards, > > > Leo Vandewoestijne > <[email protected]> > <www.dns.company> > > > > > On Tue, 07 Feb 2017, [email protected] wrote: > >> Hi Leo, >> >> The attached patch could help. >> >> Daniel >> >> On 2017-02-07 13:14, Leo Vandewoestijne wrote: >> > Hi, >> > >> > >> > I tried to install knot 2.4.0 on FreeBSD 10.3 & 11.0. >> > On amd64 these complete fine, however on i386 they don't: >> > >> > https://dns.company/downloads/knot2/knot2-2.4.0_103i386.log >> > https://dns.company/downloads/knot2/knot2-2.4.0_110i386.log >> > >> > Is there anything I can do better to prevent this? > >> diff --git a/src/knot/nameserver/query_module.h >> b/src/knot/nameserver/query_module.h >> index a8e8c41..2b47798 100644 >> --- a/src/knot/nameserver/query_module.h >> +++ b/src/knot/nameserver/query_module.h > ____________________________________________ >8 etc. > _______________________________________________ > knot-dns-users mailing list > [email protected] > https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users _______________________________________________ knot-dns-users mailing list [email protected] https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users
