Arch Linux

plenaerts

Member

From: BE

Registered: 2018-01-01

Posts: 2

PKGBUILD review sqliteodbc

I maintain the sqliteodbc AUR package. At some point I've had to update autotools scripts and with the GCC update to 15 came some incompatibilities.

The build() looks like this now at https://aur.archlinux.org/cgit/aur.git/ … sqliteodbc :

build() {
    cd "$srcdir/${pkgname}-$pkgver"

    # Autotools are from 2003. We have to autoreconf.
    rm aclocal.m4
    mv configure.in configure.ac
    aclocal -I m4
    echo "AC_CONFIG_MACRO_DIRS([m4])" >> configure.ac
    echo 'ACLOCAL_AMFLAGS="-Im4"' >> Makefile.am 
    autoupdate --force
    autoreconf --force --install

    export CFLAGS+=" -std=c17 -Wall -Wno-error=implicit-function-declaration"

    ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
    make -j$(nproc)
}

Many thanks for any suggestions for improvements. I don't really know what I'm doing with autotools or C.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,870

Re: PKGBUILD review sqliteodbc

    # Autotools are from 2003. We have to autoreconf.
    rm aclocal.m4
    mv configure.in configure.ac
    aclocal -I m4
    echo "AC_CONFIG_MACRO_DIRS([m4])" >> configure.ac
    echo 'ACLOCAL_AMFLAGS="-Im4"' >> Makefile.am 
    autoupdate --force
    autoreconf --force --install

Such changes directly alter the sourcecode and should be done in prepare() , not build() .
https://wiki.archlinux.org/title/Creati … _functions for more info .

Typically you want to change only what's absolutely needed to get things to build .

I maintain https://aur.archlinux.org/packages/cnrdrvcups-lb that has the same issue of targeting a very old autotools.
Looking at its PKGBUILD may help you.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

plenaerts

Member

From: BE

Registered: 2018-01-01

Posts: 2

Re: PKGBUILD review sqliteodbc

Thanks. I'll move those steps to prepare().

Typically you want to change only what's absolutely needed to get things to build .

I can't judge that. I've duckduckgo'd and trial'd and error'd, but I don't really know how autotools work. I use sqliteodbc. It was unmaintained so I picked it up. Things got a bit more complicated over the years, so this is the point where I'm asking advice I guess :-)

If I skip steps or change the order, the build gives warnings or breaks. But I don't know if I'm being moronically brutal in forcing autoupdate and autoreconf.

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 13,870

Re: PKGBUILD review sqliteodbc

Read https://wiki.archlinux.org/title/Arch_Linux#Simplicity .

Forcing autoreconf is very often necessary to get things to build using the uptodate autotools version provided by archlinux .
The other steps you take are likely not needed and may very well cause problems.

Warnings that don't break build are common for all software .
Ideally they should be reported upstream so upstream can fix them.

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky