Pacman & make.conf

I have been doing alot of reading today on ABS, makepkg etc... I have one question, I think I know the answer but, I'm not sure. Does pacman check the make.conf for cflags prior to package download to insure native support?
Last edited by plat (2014-08-26 02:04:29)

I think the exact functionality desired would require many more subdirectories within each of the repos.  Currently core, extra, and community each have two subdirectories: i686, x86_64.  It sounds like plat was hoping to install precompiled binaries for his specific processor which - and this is the key part as to why it can't be done - would require many new subdirectories: one for i686-core2, x86_64-core2, i686-some-other, x86_64-some-other, etc, etc.
Pacman currently would work just fine with such precompiled binaries.  The limitation is simply that no one has seen sufficient reason to provide so many different versions of every package.  I don't think this is a lack of vision either - in most cases there really wouldn't be any noteworthy difference between an x86_64-generic and an x86_64-processor-specific package.  There are a limited number of cases where it would even be worth considering building your own from ABS just for this optimization - it certainly doesn't seem worth the added maintenance costs of dozens of extra subdirectories in the repos.

Similar Messages

  • Makepkg.conf the same as make.conf

    Simple question really, is makepkg the same as make? If I add in CFLAGS will they be used when compiling packages from source or does makepkg just work when using makepkg.

    makepkg is for compiling from source but the settings from makepkg.conf won't be used if you run
    ./configure && make && make install
    by hand (and it doesn't create an Arch package), they are used when you run 'makepkg'.
    'less /usr/bin/makepkg' will show you what 'makepkg' is.
    From the wiki: https://wiki.archlinux.org/index.php/Makepkg
    makepkg is a script that automates the building of packages; it can download and validate source files, check dependencies, configure build-time settings, compile the sources, install into a temporary root, make customizations, generate meta-info, and package everything together.
    Last edited by karol (2011-07-04 20:21:27)

  • Feature request: extra Include directive in default pacman.conf

    Since arch's move to systemd, cluster administration requires less and less use of sed.  In particular, systemctl, timedatectl, /etc/sysctl.d, /etc/modules-load.d, /etc/hostname, /etc/vconsole.conf, etc. make scripting configuration changes both simpler more robust than the old approach of editing multi-purpose files such as /etc/rc.conf.
    An exception to this trend is pacman.conf, which has non-trivial default contents that almost certainly needs to be customized (e.g., to enable multilib and local repositories).  These changes would be much simpler if the default pacman.conf included a line such as:
    Include = /etc/pacman.d/conf/*.conf
    Currently my scripts use sed to insert this line at the end of the [options] section.  (Unfortunately "Include = /etc/pacman.d/*.conf" doesn't work because there's sometimes a gpg.conf file in /etc/pacman.d, but maybe that could be fixed.)
    I don't know if the forum is the right place for feature requests, but I wanted to get people's reactions.  If people think it's a good idea I can add it as a feature request to the bug tracker.
    There are several other pieces of low-hanging fruit where I'd like to see arch decrease the complexity scripting configuration (e.g., an unattended pacman-key --populate and easier customization of mkinitcpio.conf), but I figured I'd start with the simplest and gauge people's reactions.

    aweb wrote:I don't know if the forum is the right place for feature requests, but I wanted to get people's reactions.  If people think it's a good idea I can add it as a feature request to the bug tracker.
    It isn't... best to place the feedback in flyspray so it will be sure to get to the peeps that need to see it.  Welcome to Arch.

  • [SOLVED] Cannot Compile Pacman 3.5.3

    My head is aching at the moment as I have become desperate to compile Pacman. The normal procedure ./configure then make fails with this error (Honest, I can't make out anything, it sound like a libtool problem):
    make all-recursive
    make[1]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3'
    Making all in lib/libalpm
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm'
    Making all in po
    make[3]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm/po'
    make[3]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm/po'
    make[3]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm'
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT add.lo -MD -MP -MF .deps/add.Tpo -c -o add.lo add.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT add.lo -MD -MP -MF .deps/add.Tpo -c add.c -fPIC -DPIC -o .libs/add.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT add.lo -MD -MP -MF .deps/add.Tpo -c add.c -o add.o >/dev/null 2>&1
    mv -f .deps/add.Tpo .deps/add.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm.lo -MD -MP -MF .deps/alpm.Tpo -c -o alpm.lo alpm.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm.lo -MD -MP -MF .deps/alpm.Tpo -c alpm.c -fPIC -DPIC -o .libs/alpm.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm.lo -MD -MP -MF .deps/alpm.Tpo -c alpm.c -o alpm.o >/dev/null 2>&1
    mv -f .deps/alpm.Tpo .deps/alpm.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm_list.lo -MD -MP -MF .deps/alpm_list.Tpo -c -o alpm_list.lo alpm_list.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm_list.lo -MD -MP -MF .deps/alpm_list.Tpo -c alpm_list.c -fPIC -DPIC -o .libs/alpm_list.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT alpm_list.lo -MD -MP -MF .deps/alpm_list.Tpo -c alpm_list.c -o alpm_list.o >/dev/null 2>&1
    mv -f .deps/alpm_list.Tpo .deps/alpm_list.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT backup.lo -MD -MP -MF .deps/backup.Tpo -c -o backup.lo backup.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT backup.lo -MD -MP -MF .deps/backup.Tpo -c backup.c -fPIC -DPIC -o .libs/backup.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT backup.lo -MD -MP -MF .deps/backup.Tpo -c backup.c -o backup.o >/dev/null 2>&1
    mv -f .deps/backup.Tpo .deps/backup.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_local.lo -MD -MP -MF .deps/be_local.Tpo -c -o be_local.lo be_local.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_local.lo -MD -MP -MF .deps/be_local.Tpo -c be_local.c -fPIC -DPIC -o .libs/be_local.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_local.lo -MD -MP -MF .deps/be_local.Tpo -c be_local.c -o be_local.o >/dev/null 2>&1
    mv -f .deps/be_local.Tpo .deps/be_local.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_package.lo -MD -MP -MF .deps/be_package.Tpo -c -o be_package.lo be_package.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_package.lo -MD -MP -MF .deps/be_package.Tpo -c be_package.c -fPIC -DPIC -o .libs/be_package.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_package.lo -MD -MP -MF .deps/be_package.Tpo -c be_package.c -o be_package.o >/dev/null 2>&1
    mv -f .deps/be_package.Tpo .deps/be_package.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_sync.lo -MD -MP -MF .deps/be_sync.Tpo -c -o be_sync.lo be_sync.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_sync.lo -MD -MP -MF .deps/be_sync.Tpo -c be_sync.c -fPIC -DPIC -o .libs/be_sync.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT be_sync.lo -MD -MP -MF .deps/be_sync.Tpo -c be_sync.c -o be_sync.o >/dev/null 2>&1
    mv -f .deps/be_sync.Tpo .deps/be_sync.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT conflict.lo -MD -MP -MF .deps/conflict.Tpo -c -o conflict.lo conflict.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT conflict.lo -MD -MP -MF .deps/conflict.Tpo -c conflict.c -fPIC -DPIC -o .libs/conflict.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT conflict.lo -MD -MP -MF .deps/conflict.Tpo -c conflict.c -o conflict.o >/dev/null 2>&1
    mv -f .deps/conflict.Tpo .deps/conflict.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT db.lo -MD -MP -MF .deps/db.Tpo -c -o db.lo db.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT db.lo -MD -MP -MF .deps/db.Tpo -c db.c -fPIC -DPIC -o .libs/db.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT db.lo -MD -MP -MF .deps/db.Tpo -c db.c -o db.o >/dev/null 2>&1
    mv -f .deps/db.Tpo .deps/db.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT delta.lo -MD -MP -MF .deps/delta.Tpo -c -o delta.lo delta.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT delta.lo -MD -MP -MF .deps/delta.Tpo -c delta.c -fPIC -DPIC -o .libs/delta.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT delta.lo -MD -MP -MF .deps/delta.Tpo -c delta.c -o delta.o >/dev/null 2>&1
    mv -f .deps/delta.Tpo .deps/delta.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT deps.lo -MD -MP -MF .deps/deps.Tpo -c -o deps.lo deps.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT deps.lo -MD -MP -MF .deps/deps.Tpo -c deps.c -fPIC -DPIC -o .libs/deps.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT deps.lo -MD -MP -MF .deps/deps.Tpo -c deps.c -o deps.o >/dev/null 2>&1
    mv -f .deps/deps.Tpo .deps/deps.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT diskspace.lo -MD -MP -MF .deps/diskspace.Tpo -c -o diskspace.lo diskspace.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT diskspace.lo -MD -MP -MF .deps/diskspace.Tpo -c diskspace.c -fPIC -DPIC -o .libs/diskspace.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT diskspace.lo -MD -MP -MF .deps/diskspace.Tpo -c diskspace.c -o diskspace.o >/dev/null 2>&1
    mv -f .deps/diskspace.Tpo .deps/diskspace.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT dload.lo -MD -MP -MF .deps/dload.Tpo -c -o dload.lo dload.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT dload.lo -MD -MP -MF .deps/dload.Tpo -c dload.c -fPIC -DPIC -o .libs/dload.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT dload.lo -MD -MP -MF .deps/dload.Tpo -c dload.c -o dload.o >/dev/null 2>&1
    mv -f .deps/dload.Tpo .deps/dload.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT error.lo -MD -MP -MF .deps/error.Tpo -c -o error.lo error.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c -fPIC -DPIC -o .libs/error.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT error.lo -MD -MP -MF .deps/error.Tpo -c error.c -o error.o >/dev/null 2>&1
    mv -f .deps/error.Tpo .deps/error.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT group.lo -MD -MP -MF .deps/group.Tpo -c -o group.lo group.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT group.lo -MD -MP -MF .deps/group.Tpo -c group.c -fPIC -DPIC -o .libs/group.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT group.lo -MD -MP -MF .deps/group.Tpo -c group.c -o group.o >/dev/null 2>&1
    mv -f .deps/group.Tpo .deps/group.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT handle.lo -MD -MP -MF .deps/handle.Tpo -c -o handle.lo handle.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT handle.lo -MD -MP -MF .deps/handle.Tpo -c handle.c -fPIC -DPIC -o .libs/handle.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT handle.lo -MD -MP -MF .deps/handle.Tpo -c handle.c -o handle.o >/dev/null 2>&1
    mv -f .deps/handle.Tpo .deps/handle.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT log.lo -MD -MP -MF .deps/log.Tpo -c -o log.lo log.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT log.lo -MD -MP -MF .deps/log.Tpo -c log.c -fPIC -DPIC -o .libs/log.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT log.lo -MD -MP -MF .deps/log.Tpo -c log.c -o log.o >/dev/null 2>&1
    mv -f .deps/log.Tpo .deps/log.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT package.lo -MD -MP -MF .deps/package.Tpo -c -o package.lo package.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT package.lo -MD -MP -MF .deps/package.Tpo -c package.c -fPIC -DPIC -o .libs/package.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT package.lo -MD -MP -MF .deps/package.Tpo -c package.c -o package.o >/dev/null 2>&1
    mv -f .deps/package.Tpo .deps/package.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT pkghash.lo -MD -MP -MF .deps/pkghash.Tpo -c -o pkghash.lo pkghash.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT pkghash.lo -MD -MP -MF .deps/pkghash.Tpo -c pkghash.c -fPIC -DPIC -o .libs/pkghash.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT pkghash.lo -MD -MP -MF .deps/pkghash.Tpo -c pkghash.c -o pkghash.o >/dev/null 2>&1
    mv -f .deps/pkghash.Tpo .deps/pkghash.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT remove.lo -MD -MP -MF .deps/remove.Tpo -c -o remove.lo remove.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT remove.lo -MD -MP -MF .deps/remove.Tpo -c remove.c -fPIC -DPIC -o .libs/remove.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT remove.lo -MD -MP -MF .deps/remove.Tpo -c remove.c -o remove.o >/dev/null 2>&1
    mv -f .deps/remove.Tpo .deps/remove.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT sync.lo -MD -MP -MF .deps/sync.Tpo -c -o sync.lo sync.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT sync.lo -MD -MP -MF .deps/sync.Tpo -c sync.c -fPIC -DPIC -o .libs/sync.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT sync.lo -MD -MP -MF .deps/sync.Tpo -c sync.c -o sync.o >/dev/null 2>&1
    mv -f .deps/sync.Tpo .deps/sync.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT trans.lo -MD -MP -MF .deps/trans.Tpo -c -o trans.lo trans.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT trans.lo -MD -MP -MF .deps/trans.Tpo -c trans.c -fPIC -DPIC -o .libs/trans.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT trans.lo -MD -MP -MF .deps/trans.Tpo -c trans.c -o trans.o >/dev/null 2>&1
    mv -f .deps/trans.Tpo .deps/trans.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT util.lo -MD -MP -MF .deps/util.Tpo -c -o util.lo util.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT util.lo -MD -MP -MF .deps/util.Tpo -c util.c -fPIC -DPIC -o .libs/util.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT util.lo -MD -MP -MF .deps/util.Tpo -c util.c -o util.o >/dev/null 2>&1
    mv -f .deps/util.Tpo .deps/util.Plo
    /bin/sh ../../libtool --tag=CC --mode=compile gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT version.lo -MD -MP -MF .deps/version.Tpo -c -o version.lo version.c
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT version.lo -MD -MP -MF .deps/version.Tpo -c version.c -fPIC -DPIC -o .libs/version.o
    libtool: compile: gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DHAVE_CONFIG_H -I. -I../.. -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -MT version.lo -MD -MP -MF .deps/version.Tpo -c version.c -o version.o >/dev/null 2>&1
    mv -f .deps/version.Tpo .deps/version.Plo
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -fvisibility=internal -fgnu89-inline -g -O2 -Wall -no-undefined -version-info 6:3:0 -o libalpm.la -rpath /usr/local/lib add.lo alpm.lo alpm_list.lo backup.lo be_local.lo be_package.lo be_sync.lo conflict.lo db.lo delta.lo deps.lo diskspace.lo dload.lo error.lo group.lo handle.lo log.lo package.lo pkghash.lo remove.lo sync.lo trans.lo util.lo version.lo -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -shared -fPIC -DPIC .libs/add.o .libs/alpm.o .libs/alpm_list.o .libs/backup.o .libs/be_local.o .libs/be_package.o .libs/be_sync.o .libs/conflict.o .libs/db.o .libs/delta.o .libs/deps.o .libs/diskspace.o .libs/dload.o .libs/error.o .libs/group.o .libs/handle.o .libs/log.o .libs/package.o .libs/pkghash.o .libs/remove.o .libs/sync.o .libs/trans.o .libs/util.o .libs/version.o -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -O2 -Wl,-soname -Wl,libalpm.so.6 -o .libs/libalpm.so.6.0.3
    libtool: link: (cd ".libs" && rm -f "libalpm.so.6" && ln -s "libalpm.so.6.0.3" "libalpm.so.6")
    libtool: link: (cd ".libs" && rm -f "libalpm.so" && ln -s "libalpm.so.6.0.3" "libalpm.so")
    libtool: link: ar cru .libs/libalpm.a add.o alpm.o alpm_list.o backup.o be_local.o be_package.o be_sync.o conflict.o db.o delta.o deps.o diskspace.o dload.o error.o group.o handle.o log.o package.o pkghash.o remove.o sync.o trans.o util.o version.o
    libtool: link: ranlib .libs/libalpm.a
    libtool: link: ( cd ".libs" && rm -f "libalpm.la" && ln -s "../libalpm.la" "libalpm.la" )
    make[3]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm'
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/lib/libalpm'
    Making all in src/util
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/src/util'
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT vercmp.o -MD -MP -MF .deps/vercmp.Tpo -c -o vercmp.o vercmp.c
    mv -f .deps/vercmp.Tpo .deps/vercmp.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o vercmp vercmp.o ../../lib/libalpm/version.o -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o vercmp vercmp.o ../../lib/libalpm/version.o -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT testpkg.o -MD -MP -MF .deps/testpkg.Tpo -c -o testpkg.o testpkg.c
    mv -f .deps/testpkg.Tpo .deps/testpkg.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o testpkg testpkg.o ../../lib/libalpm/.libs/libalpm.la -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o .libs/testpkg testpkg.o ../../lib/libalpm/.libs/libalpm.so -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -Wl,-rpath -Wl,/usr/local/lib
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT testdb.o -MD -MP -MF .deps/testdb.Tpo -c -o testdb.o testdb.c
    mv -f .deps/testdb.Tpo .deps/testdb.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o testdb testdb.o ../../lib/libalpm/.libs/libalpm.la -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o .libs/testdb testdb.o ../../lib/libalpm/.libs/libalpm.so -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -Wl,-rpath -Wl,/usr/local/lib
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT cleanupdelta.o -MD -MP -MF .deps/cleanupdelta.Tpo -c -o cleanupdelta.o cleanupdelta.c
    mv -f .deps/cleanupdelta.Tpo .deps/cleanupdelta.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o cleanupdelta cleanupdelta.o ../../lib/libalpm/.libs/libalpm.la -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o .libs/cleanupdelta cleanupdelta.o ../../lib/libalpm/.libs/libalpm.so -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -Wl,-rpath -Wl,/usr/local/lib
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT pactree.o -MD -MP -MF .deps/pactree.Tpo -c -o pactree.o pactree.c
    mv -f .deps/pactree.Tpo .deps/pactree.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o pactree pactree.o ../../lib/libalpm/.libs/libalpm.la -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o .libs/pactree pactree.o ../../lib/libalpm/.libs/libalpm.so -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -Wl,-rpath -Wl,/usr/local/lib
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/src/util'
    Making all in src/pacman
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/src/pacman'
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT conf.o -MD -MP -MF .deps/conf.Tpo -c -o conf.o conf.c
    mv -f .deps/conf.Tpo .deps/conf.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT database.o -MD -MP -MF .deps/database.Tpo -c -o database.o database.c
    mv -f .deps/database.Tpo .deps/database.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT deptest.o -MD -MP -MF .deps/deptest.Tpo -c -o deptest.o deptest.c
    mv -f .deps/deptest.Tpo .deps/deptest.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT package.o -MD -MP -MF .deps/package.Tpo -c -o package.o package.c
    mv -f .deps/package.Tpo .deps/package.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT pacman.o -MD -MP -MF .deps/pacman.Tpo -c -o pacman.o pacman.c
    mv -f .deps/pacman.Tpo .deps/pacman.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT query.o -MD -MP -MF .deps/query.Tpo -c -o query.o query.c
    mv -f .deps/query.Tpo .deps/query.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT remove.o -MD -MP -MF .deps/remove.Tpo -c -o remove.o remove.c
    mv -f .deps/remove.Tpo .deps/remove.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT sync.o -MD -MP -MF .deps/sync.Tpo -c -o sync.o sync.c
    mv -f .deps/sync.Tpo .deps/sync.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT callback.o -MD -MP -MF .deps/callback.Tpo -c -o callback.o callback.c
    mv -f .deps/callback.Tpo .deps/callback.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT upgrade.o -MD -MP -MF .deps/upgrade.Tpo -c -o upgrade.o upgrade.c
    mv -f .deps/upgrade.Tpo .deps/upgrade.Po
    gcc -std=gnu99 -DLOCALEDIR=\"/usr/local/share/locale\" -DCONFFILE=\"/usr/local/etc/pacman.conf\" -DROOTDIR=\"/\" -DDBPATH=\"/usr/local/var/lib/pacman/\" -DCACHEDIR=\"/usr/local/var/cache/pacman/pkg/\" -DLOGFILE=\"/usr/local/var/log/pacman.log\" -DHAVE_CONFIG_H -I. -I../.. -I../../lib/libalpm -pedantic -D_GNU_SOURCE -g -O2 -Wall -MT util.o -MD -MP -MF .deps/util.Tpo -c -o util.o util.c
    mv -f .deps/util.Tpo .deps/util.Po
    /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o pacman conf.o database.o deptest.o package.o pacman.o query.o remove.o sync.o callback.o upgrade.o util.o ../../lib/libalpm/.libs/libalpm.la -lfetch -lssl -larchive
    libtool: link: gcc -std=gnu99 -pedantic -D_GNU_SOURCE -g -O2 -Wall -o .libs/pacman conf.o database.o deptest.o package.o pacman.o query.o remove.o sync.o callback.o upgrade.o util.o ../../lib/libalpm/.libs/libalpm.so -lfetch -lssl /usr/lib/libarchive.so -lacl -lattr -lexpat -llzma -lbz2 -lz -lcrypto -Wl,-rpath -Wl,/usr/local/lib
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/src/pacman'
    Making all in scripts
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/scripts'
    GEN makepkg
    GEN pacman-db-upgrade
    GEN pacman-optimize
    GEN pkgdelta
    GEN rankmirrors
    GEN repo-add
    rm -f repo-remove
    ln -s repo-add repo-remove
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/scripts'
    Making all in etc
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/etc'
    GEN makepkg.conf
    GEN pacman.conf
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/etc'
    Making all in po
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/po'
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/po'
    Making all in test/pacman
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman'
    Making all in tests
    make[3]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman/tests'
    make[3]: Nothing to be done for `all'.
    make[3]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman/tests'
    make[3]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman'
    make[3]: Nothing to be done for `all-am'.
    make[3]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman'
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/pacman'
    Making all in test/util
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/util'
    make[2]: Nothing to be done for `all'.
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/test/util'
    Making all in contrib
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/contrib'
    GEN bacman
    GEN pacdiff
    GEN paclist
    GEN pacscripts
    GEN pacsearch
    GEN wget-xdelta.sh
    GEN bash_completion
    GEN zsh_completion
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/contrib'
    Making all in doc
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3/doc'
    make[2]: Nothing to be done for `all'.
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3/doc'
    make[2]: Entering directory `/home/aardvark/Documents/pacman/pacman-3.5.3'
    make[2]: Nothing to be done for `all-am'.
    make[2]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3'
    make[1]: Leaving directory `/home/aardvark/Documents/pacman/pacman-3.5.3'
    This is the output of ./configure:
    checking build system type... x86_64-unknown-linux-gnu
    checking host system type... x86_64-unknown-linux-gnu
    checking for a BSD-compatible install... /bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for gawk... (cached) gawk
    checking for style of include used by make... GNU
    checking for gcc... gcc
    checking whether the C compiler works... yes
    checking for C compiler default output file name... a.out
    checking for suffix of executables...
    checking whether we are cross compiling... no
    checking for suffix of object files... o
    checking whether we are using the GNU C compiler... yes
    checking whether gcc accepts -g... yes
    checking for gcc option to accept ISO C89... none needed
    checking dependency style of gcc... gcc3
    checking for gcc option to accept ISO C99... -std=gnu99
    checking whether ln -s works... yes
    checking whether make sets $(MAKE)... (cached) yes
    checking how to print strings... printf
    checking for a sed that does not truncate output... /bin/sed
    checking for grep that handles long lines and -e... /bin/grep
    checking for egrep... /bin/grep -E
    checking for fgrep... /bin/grep -F
    checking for ld used by gcc -std=gnu99... /usr/bin/ld
    checking if the linker (/usr/bin/ld) is GNU ld... yes
    checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
    checking the name lister (/usr/bin/nm -B) interface... BSD nm
    checking the maximum length of command line arguments... 1572864
    checking whether the shell understands some XSI constructs... yes
    checking whether the shell understands "+="... yes
    checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
    checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
    checking for /usr/bin/ld option to reload object files... -r
    checking for objdump... objdump
    checking how to recognize dependent libraries... pass_all
    checking for dlltool... no
    checking how to associate runtime and link libraries... printf %s\n
    checking for ar... ar
    checking for archiver @FILE support... @
    checking for strip... strip
    checking for ranlib... ranlib
    checking command to parse /usr/bin/nm -B output from gcc -std=gnu99 object... ok
    checking for sysroot... no
    checking for mt... no
    checking if : is a manifest tool... no
    checking how to run the C preprocessor... gcc -std=gnu99 -E
    checking for ANSI C header files... yes
    checking for sys/types.h... yes
    checking for sys/stat.h... yes
    checking for stdlib.h... yes
    checking for string.h... yes
    checking for memory.h... yes
    checking for strings.h... yes
    checking for inttypes.h... yes
    checking for stdint.h... yes
    checking for unistd.h... yes
    checking for dlfcn.h... yes
    checking for objdir... .libs
    checking if gcc -std=gnu99 supports -fno-rtti -fno-exceptions... no
    checking for gcc -std=gnu99 option to produce PIC... -fPIC -DPIC
    checking if gcc -std=gnu99 PIC flag -fPIC -DPIC works... yes
    checking if gcc -std=gnu99 static flag -static works... yes
    checking if gcc -std=gnu99 supports -c -o file.o... yes
    checking if gcc -std=gnu99 supports -c -o file.o... (cached) yes
    checking whether the gcc -std=gnu99 linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
    checking whether -lc should be explicitly linked in... no
    checking dynamic linker characteristics... GNU/Linux ld.so
    checking how to hardcode library paths into programs... immediate
    checking whether stripping libraries is possible... yes
    checking if libtool supports shared libraries... yes
    checking whether to build shared libraries... yes
    checking whether to build static libraries... yes
    checking for python2.7... python2.7
    checking for bash... /bin/bash
    checking whether NLS is requested... yes
    checking for msgfmt... /usr/bin/msgfmt
    checking for gmsgfmt... /usr/bin/msgfmt
    checking for xgettext... /usr/bin/xgettext
    checking for msgmerge... /usr/bin/msgmerge
    checking for ld used by GCC... /usr/bin/ld -m elf_x86_64
    checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
    checking for shared library run path origin... done
    checking for CFPreferencesCopyAppValue... no
    checking for CFLocaleCopyCurrent... no
    checking for GNU gettext in libc... yes
    checking whether to use NLS... yes
    checking where the gettext function comes from... libc
    checking for archive_read_data in -larchive... yes
    checking whether to link with libssl... yes
    checking for MD5_Final in -lssl... yes
    checking whether to link with libfetch... yes
    checking for fetchParseURL in -lfetch... yes
    checking whether fetchConnectionCacheInit is declared... yes
    checking fcntl.h usability... yes
    checking fcntl.h presence... yes
    checking for fcntl.h... yes
    checking glob.h usability... yes
    checking glob.h presence... yes
    checking for glob.h... yes
    checking libintl.h usability... yes
    checking libintl.h presence... yes
    checking for libintl.h... yes
    checking locale.h usability... yes
    checking locale.h presence... yes
    checking for locale.h... yes
    checking mntent.h usability... yes
    checking mntent.h presence... yes
    checking for mntent.h... yes
    checking for string.h... (cached) yes
    checking sys/ioctl.h usability... yes
    checking sys/ioctl.h presence... yes
    checking for sys/ioctl.h... yes
    checking sys/mount.h usability... yes
    checking sys/mount.h presence... yes
    checking for sys/mount.h... yes
    checking sys/param.h usability... yes
    checking sys/param.h presence... yes
    checking for sys/param.h... yes
    checking sys/statvfs.h usability... yes
    checking sys/statvfs.h presence... yes
    checking for sys/statvfs.h... yes
    checking sys/time.h usability... yes
    checking sys/time.h presence... yes
    checking for sys/time.h... yes
    checking for sys/types.h... (cached) yes
    checking sys/ucred.h usability... no
    checking sys/ucred.h presence... no
    checking for sys/ucred.h... no
    checking syslog.h usability... yes
    checking syslog.h presence... yes
    checking for syslog.h... yes
    checking wchar.h usability... yes
    checking wchar.h presence... yes
    checking for wchar.h... yes
    checking for inline... inline
    checking for mode_t... yes
    checking for off_t... yes
    checking for pid_t... yes
    checking for size_t... yes
    checking whether struct tm is in sys/time.h or time.h... time.h
    checking for uid_t in sys/types.h... yes
    checking for dirent.h that defines DIR... yes
    checking for library containing opendir... none required
    checking for struct dirent.d_type... yes
    checking PATH_MAX defined... yes
    checking vfork.h usability... no
    checking vfork.h presence... no
    checking for vfork.h... no
    checking for fork... yes
    checking for vfork... yes
    checking for working fork... yes
    checking for working vfork... (cached) yes
    checking for library containing getmntent... none required
    checking whether lstat correctly handles trailing slash... yes
    checking whether time.h and sys/time.h may both be included... yes
    checking for sys/time.h... (cached) yes
    checking for unistd.h... (cached) yes
    checking for alarm... yes
    checking for working mktime... yes
    checking for geteuid... yes
    checking for getmntinfo... no
    checking for realpath... yes
    checking for regcomp... yes
    checking for strcasecmp... yes
    checking for strndup... yes
    checking for strrchr... yes
    checking for strsep... yes
    checking for swprintf... yes
    checking for wcwidth... yes
    checking for uname... yes
    checking filesystem statistics type... checking for getmntinfo... (cached) no
    checking for getmntent... (cached) yes
    struct statvfs
    checking for struct statvfs.f_flag... yes
    checking for struct statfs.f_flags... no
    checking for special C compiler options needed for large files... no
    checking for _FILE_OFFSET_BITS value needed for large files... no
    checking whether gcc -std=gnu99 accepts -fvisibility=internal... yes
    checking for -fgnu89-inline... yes
    checking for du... /bin/du
    checking for asciidoc... asciidoc
    checking for building documentation... yes, enabled by configure
    checking for doxygen... no
    checking for doxygen... no, disabled by configure
    checking for debug mode request... no
    checking whether to use git version if available... no, disabled by configure
    configure: creating ./config.status
    config.status: creating lib/libalpm/Makefile
    config.status: creating lib/libalpm/po/Makefile.in
    config.status: creating src/pacman/Makefile
    config.status: creating src/util/Makefile
    config.status: creating scripts/Makefile
    config.status: creating doc/Makefile
    config.status: creating etc/Makefile
    config.status: creating po/Makefile.in
    config.status: creating test/pacman/Makefile
    config.status: creating test/pacman/tests/Makefile
    config.status: creating test/util/Makefile
    config.status: creating contrib/Makefile
    config.status: creating Makefile
    config.status: creating config.h
    config.status: executing depfiles commands
    config.status: executing libtool commands
    config.status: executing po-directories commands
    config.status: creating lib/libalpm/po/POTFILES
    config.status: creating lib/libalpm/po/Makefile
    config.status: creating po/POTFILES
    config.status: creating po/Makefile
    pacman:
    Build information:
    source code location : .
    prefix : /usr/local
    sysconfdir : /usr/local/etc
    conf file : /usr/local/etc/pacman.conf
    localstatedir : /usr/local/var
    database dir : /usr/local/var/lib/pacman/
    cache dir : /usr/local/var/cache/pacman/pkg/
    compiler : gcc -std=gnu99
    compiler flags : -g -O2 -Wall
    defines : -DHAVE_CONFIG_H
    Architecture : x86_64
    Architecture flags : -march=x86-64
    Host Type : x86_64-unknown-linux-gnu
    Filesize command : stat -L -c %s
    In-place sed command : sed -i
    libalpm version : 6.0.3
    libalpm version info : 6:3:0
    pacman version : 3.5.3
    using git version : no
    Directory and file information:
    root working directory : /
    package extension : .pkg.tar.gz
    source pkg extension : .src.tar.gz
    build script name : PKGBUILD
    Compilation options:
    Run make in doc/ dir : yes
    Doxygen support : no
    debug support : no
    I'm sure libtool is installed. I had a working copy of pacman but a bad "make install" destroyed that too. Any help?
    Last edited by newdave (2011-07-07 05:46:27)

    falconindy wrote:
    And where's the error? Other than the completely wrong paths being set for ./configure, there is none. That's a successful make.
    newdave wrote:P.S. I must add that currently pacman is broken on my system so " makepkg -s " does not work (error: no usable package repositories configured.)
    P.P.S note the word configure. this is user error as you've not uncommented any mirrors from /etc/pacman.d/mirrorlist. I strongly suggest you do one of two things:
    1) If you're insistent on compiling pacman by hand, use the configure flags from the package in ABS.
    2) Backup your pacman.conf/makepkg.conf, download a pacman package, and extract it to root, and then restore your config files. After fixing your mirrorlist, reinstall pacman with pacman, using pacman -Sf pacman
    I identified some error keywords in the make output and thought the make had failed. but apparently I was wrong. As you said the make was succesful( sorry for noobish mistake). As to the pacman breakage, the problem was with two duplicate copies of  pacman in /usr/bin/pacman and  /usr/local/bin/pacman ! just removed /usr/local/bin/pacman and pacman got fixed...
    Anyway, Thank you all for your help.

  • SiS Mirage 3 671/771 - Can't make it work on Arch64...

    Hi folks! I'm new to the forum (first topic! yay! ) and also new to Arch Linux. I am a former Slack user, although I was using Kubuntu 9.10 till yesterday (shiped with my new notebook...).
    The thing is: I formated this notebook. Made a Dual Boot (Win + Arch). Installation worked just fine, i have a fully functional Arch environment. But the problem is about Xorg. The Videoboard is a SiS Mirage 3 671/771, so I installed xf86-driver-sis and xf86-driver-sisusb with Shaman (Chakra + tools are installed as well). But if I update my xorg.conf to use any of them, the X11 won't start, returning "No screens found" error. Using VESA, weird stuff happens... Strange artifacts on screen, "choppy" moving/resizing windows...
    Before formating the machine I checked Kubuntu's drivers and xorg.conf (made a copy of the last one), and Kubuntu was using "sis671" driver, and everything was working perfectly, including some (I repeat: SOME) of the Desktop Effects. Searching through the forum, I found two posts about this issue but nothing described there worked for me. Links for those posts:
    Sis graphics driver on linux?
    [Solved] Sis mirage3/sis 671
    This last one says [Solved], but i couldn't find clear instructions on how the author did it. Apparently, installing this url's drivers worked for a lot of people, but I can't manage to install/compile/use them.
    I'm using Arch64, for my computer is a Pentium DualCore T4300, 4Gb RAM, and ArchWiki says Arch32 doesn't support more than 3Gb RAM. Can this be the problem for me? Maybe the only people who actually installed the drivers from that URL are those using Arch32...
    I don't have to say everything works fine in Window$... crappy-SiS refuses to release a decent 3D driver for SiS Mirage on Linux, but work just fine with M$ OS. This annoys me...
    Afterall, is there anyone who can help me compiling/installing/making-work this crappy video-board? If I could make it work just like the default Kubuntu installation, it would be great!
    Sorry for the long (double)post and my awful english (I'm Brazilian),
    And thanks to all in advance.

    @mikkle, thank you so much! I followed the instructions to downgrade the xorg-server, installed the 64 bit driver and now it works perfectly! I have my resolution of 1280x800px and some of the desktop effects on KDE 4.3 (Chakra Project).
    Anyway, if anybody else goes through the same and would like to know how to proceed, I will describe the steps here. First, I upgraded the system:
    $ pacman -Syy
    $ pacman -Syu
    Then, after everything was done, I followed the instructions at the Arch Wiki: Downgrading Packages to downgrade xorg-server. Also did the trick to stop pacman from updating xorg-server.
    After the downgrade, I installed SiS drivers from this website (I used the one precompiled for Ubuntu 64 bits).
    Then I proceeded to reinstall Chakra project (uninstall it an install like described at Chakra`s website). About xorg.conf file, it is exactly as the one above, with the obvious difference to use "sis671" instead of "vesa" at the Driver field, looking like this:
    Section "Device"
    Identifier "Card0"
    Driver "sis671"
    All of those steps took me about a day or so to perform, but I would type one command and go out for a coffee, a smoke, some chating...... and come back after two, maybe three hours. I believe that with some more dedication (and a better internet connection) it can't take more than 8 hours.
    One last recommendation: if anyone will perform the same steps, make sure to read everything, downloading everything you believe will use, and really understanding the procedure before doing it! Seriously, I mean it! Understanding the procedure is the most important item here! Other than that, it is pointless to mess so much with your system, and in that case I would strongly recommend the use of Ubuntu (or anything alike...). Of course I had some other complications, it wasn't as simple as it sounds, but my knowledge of Linux was essential on solving it, knowledge that I acquired in years using Slackware (that has the same philosophy as Arch), reading tons of tutorials like those and really understanding all of them... The only reason I changed to Arch is Pacman (makes my life go faster)!
    Thanks again to everyone that helped! Can anyone add a [SOLVED] to the thread's title?!

  • New ideas for pacman features

    I'd like to start a discussion about pacman and some features I would like to see in it.
    If I compile something with srcpac instead of installing with pacman, it would be nice if pacman remembered that I did so and recompiled the package next time I get an update of it. For instance: I compile my own (beyond) kernel, so I have to compile the kernel modules I use too. It would be nice if it could happen automatically: the kernel modules already get updated with the new kernel, so it would be just a matter of remembering that I like to compile these packages.
    srcpac already supports the automatic alteration of a PKGBUILD, but it would be nice to have a more systematic approach like the make.conf file on a BSD system. This would make it easier to compile some packages with other than the default options of the PKGBUILD. The current grep method is too heavily depending on the format of the PKGBUILD and fails when the maintainer changes the PKGBUILD.
    What are your ideas/opinions?

    Dusty wrote:This sounds more like a srcpac feature than a pacman feature. Srcpac isn't an official part of Arch Linux, so integrating anything into pacman isn't likely to happen.
    Why should these programs be separated? I think it would be wonderful to have one package manager where you can choose what to compile and what to take from binary packages. While I like binary packages, now and again there are packages I have to compile and it would be nice if it could be done automatically. makepkg and srcpac are fine for installing these packages, but not when updating the system. An easier and more robust approach to changing PKGBUILDS automatically by using variables that can be defined in a BSD-like make.conf file would be great.

  • Pacman errors - libwnck and libxres

    Since I did a Pacman -Syu a lot of programs I try to install come up with the error: cannot resolve dependencies for "libwnck": "libxres" is not in the package set. So I tried to install either of these packages seperately but then pacman reports that they are not found in the database. Any ideas?

    Fixed
    Looks like it was the mirrors. After pacman -Syu it backed up all my old /etc/pacman.d/*.conf files as .pacnew. After restoring them everything works again... at least I think. It makes me wonder what the benefit was of updating them in the first place though.
    Last edited by joewhite (2007-02-19 23:41:22)

  • Pacman 4.1 Released

    Pacman 4.1 has just been released to [testing] with some fantastic and long awaited features, including:
    tight integration between the package manager and systemd
    colour support added
    checkupdates merged
    and more...
    Check out Allan's blog post for all the details:
    http://allanmcrae.com/2013/04/pacman-4-1-released/

    opt1mus wrote:
    Faither wrote:
    wulax wrote:I have a headless server running Arch and would like to be notified when it needs to be rebooted. Will pacmand be able to send pop-ups remotely to my desktop or phone?
    You could use the "--beep" function for that.
    I'd also want to suggest a new config file for this feature:
    pacman-beep.conf
    With this we can make it play different sounds/songs like "For Elise" before a reboot...
    -n --notify-sound=/foo/bar #default --notify-sound="/etc/pacman.d/Also\ Sprach\ Zarathustra.flac"
    The problem with things like this is that excessive customisation would make technical support a nightmare.
    We need sane defaults, which can't be modified except on an enterprise-level edition of Arch.

  • Pacman completers for IPython

    First off, hay all, I'm pretty much a brand-new ubuntu convert, although I have used Arch several times in the past on my VM's. Actually a Chakra user, but posting this here since I thought it might benefit a few arch users who may happen to use IPython.
    As a Debian user primarily, I grew fond of IPython's handy aptitude/apt-get tab completers for installing packages, and I found myself in withdrawal after switching to Arch since I was trying to tab-complete all my package names when installing stuff via pacman.
    So, here's a very quick and dirty completer that uses the very useful custom completer functionality in IPython. It's far from perfect, complete, or possibly useful depending on what end of the leet spectrum you're on, but I'm hoping a few poor folks like me who abuse the tab key will find this somewhat useful.
    # pacman_search.py
    """Pacman(-frontend) search generator and custom completer for IPython.
    To use, import this module from ~/.ipython/ipy_user_conf.py, and somewhere in
    main(), after `ip` is defined, add the following:
    ip.set_hook('complete_command', pacman_search.completer, str_key='smth')
    Where you would replace 'smth' with pacman, any pacman frontend you use, or an
    IPython alias. If you are using something other than pacman, make sure to set
    the constant APP before you hook the completer.
    __author__ = 'mini-man <mini.mcmidget AT gmail.com>'
    __license__ = 'GPLv3'
    __version__ = 0, 0, 1
    import os
    import re
    # Set this to a pacman frontend.
    APP = 'pacman'
    # Matches output from `<app> -Ss <search-term>`:
    REGEXES = {
    'pacman': '^(.+?)/(.+?)\s',
    'yaourt': '^.+?\[1;\d+m(.+?)/.+?\[1m(.+?)\s'
    def memoize(func):
    """Memoizes a generator."""
    def inner(arg):
    if isinstance(arg, list):
    arg = tuple(arg)
    for key, val in inner.cache.iteritems():
    if arg.startswith(key):
    for i in val:
    yield i
    return
    tmp = []
    for i in func(arg):
    tmp.append(i)
    yield i
    inner.cache[arg] = tmp
    inner.cache = {}
    return inner
    @memoize
    def search(term):
    """Does a search with the specified term and returns parsed results."""
    out = os.popen('%s -Ss %s' % (APP, term))
    for ln in out:
    m = re.match(REGEXES[APP], ln)
    # Throwing away .group(1) because atm there's no need for it...
    if m and m.group(2).startswith(term):
    yield m.group(2)
    def completer(self, event):
    """IPython custom completer for pacman package searching."""
    cmd_param = event.line.split()
    if event.line.endswith(' '):
    cmd_param.append('')
    if cmd_param[0] == 'sudo':
    cmd_param = cmd_param[1:]
    if cmd_param[1].startswith('-S'):
    return list(search(cmd_param[2]))
    Last edited by mini-man (2009-02-10 16:34:27)

    Do you actually use IPython as your main shell? I use it extensively for development, but when I started trying to use it as a shell I found it a bit clunky, especially (ironically) for development -- my python namespace got clogged and if I was testing a project and needed to change a module it was hard to pick up the changes.
    Just curious about your experiences using IPython as a shell.
    Dusty

  • Pacman -Syu fscked up my system

    I ran in a disk-full situation while running pacman -Syu. This totally and irreversably ruined my system . After downloading all packages (everything since the last full update of 20 august) it ran the usual pacman checks and then started installing the packages. After a few succesfull installs the / filesystem was full and installing failed from thereon. Yet pacman went on and on with the remaining packages, including a new kernel which also failed miserably and from there it went nasty. Messages from ldconfig about invalid ELF headers in libraries etc.. Yet pacman continued like nothing happened.
    After it had finally finished, my system was unusable and also beyond repair. First i freed up some disk space (/bin/rm still worked). But pacman would not run anymore (segmentation error). Pacman --debug also crashed. Just about everything i tried to start, failed with /urs/lib/libetcetera errors about invalid ELF headers.
    Finally i tried rebooting but that didn't work (it could not locate the root filesystem), which was no surprise having seen all the error messages during the installation of the kernel package.
    I'm left with no alternative but to download a fresh iso image and continue from there.
    With all the checks from pacman during its upgrades, apparently there is no check or warning for a safe marging of free diskspace. Wouldn't that be a nice feature? It also would be nice if pacman would just stop after the first failed package.

    11639 is probably about the same issue. Although this person could still use pacman to repair his system. I can imagine more people could run into this situation.
    I see pacman makes a estimate on required disk size before installation. Maybe just add some percentage extra as a safety margin?
    And again, don't let pacman continue after the first failed package. A simple "Errors occured. Continue Y/n?" would be enough.

  • [SOLVED] makepkg ignoreing CFLAGS

    It seems no matter what I do makeflags ignores my CFLAGS and CXXFLAGS options.
    I have added
    CFLAGS="-march=sandybridge -mtune=sandybridge -O3 -pipe"
    to all the locations that makepkg.conf has been installed..
    /etc/makepkg.conf
    /home/jwdev/abs/chroot/jwdev/etc/makepkg.conf
    /home/jwdev/abs/chroot/root/etc/makepkg.conf
    /var/abs/core/pacman/makepkg.conf
    as well as to the makechrootpkg command
    mkarchroot -C /etc/pacman.conf -M /etc/makepkg.conf $CHROOT/root base-devel
    arch-nspawn $CHROOT/root pacman -Syu
    cd $1
    makechrootpkg -c -r $CHROOT -- CFLAGS="-march=sandybridge -mtune=sandybridge -O3 -pipe" CXXFLAGS="-march=sandybridge -mtune=sandybridge -O3 -pipe"
    But still, when I run makepkg I see...
    g++ -c -pipe -O2 -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4 -Wall
    This is the case if I makepkg or makechrootpkg
    is there some otehr secert location for these args? or are they hardcoded in
    I do see that some packages have hardcoded args, like libaio, which kind of defeats the point of abs
    build() {
    cd "$srcdir/$pkgname-$pkgver"
    CFLAGS="-march=${CARCH/_/-} -mtune=generic -O2 -pipe"
    make
    but in my test case, smplayer, this is not the case
    build() {
    cd "$pkgname-$pkgver"
    make PREFIX=/usr \
    DOC_PATH="\\\"/usr/share/doc/smplayer\\\"" \
    QMAKE_OPTS=DEFINES+=NO_DEBUG_ON_CONSOLE
    thanks
    UPDATE:  running makepkg on "joe" I see that the CFLAGS are correct... so it seems that only some (all but 1 so far actually) packages respect the makepkg? while the other just do their 'own thing'?  I am new to Arch, so maybe I am missing a huge piece of information
    Last edited by ntisithoj (2015-03-17 06:35:08)

    The trick desribed in wiki:
    https://wiki.archlinux.org/index.php/makepkg#CFLAGS.2FCXXFLAGS.2FCPPFLAGS_in_makepkg.conf_do_not_work_for_QMAKE_based_packages
    works only with those sources, that use qmake (qmake-qt4) for preconfigure. In those case, you should to define QMAKE variable in PKGBUILD and next invoke it in "build" section. See example of QupZilla that works for me (it's modified qupzilla-qt5-qtwebkit-git's PKGBUILD by Alex Talker):
    pkgname=qupzilla-qt5-qtwebkit-git
    pkgver=r3348.0c37b62
    pkgrel=1
    pkgdesc="A new and very fast open source browser based on WebKit core, written in Qt Framework."
    arch=('i686' 'x86_64')
    url="http://qupzilla.com/index.php"
    license=('GPL')
    depends=( 'qt5-base' 'qt5-script' 'qt5-webkit')
    makedepends=('git')
    provides=('qupzilla' 'qupzilla-git')
    conflicts=('qupzilla' 'qupzilla-git' 'qupzilla-qt5-git')
    source=('git+https://github.com/QupZilla/qupzilla.git')
    md5sums=('SKIP')
    CFLAGS="-march=native -mtune=bdver2 -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"
    CXXFLAGS="-march=native -mtune=bdver2 -O2 -pipe -fstack-protector-strong --param=ssp-buffer-size=4"
    pkgver() {
    cd qupzilla
    printf "r%s.%s" "$(git rev-list --count HEAD)" "$(git rev-parse --short HEAD)"
    build() {
    cd "$srcdir/qupzilla"
    export USE_WEBGL="true"
    export KDE_INTEGRATION="true"
    export QUPZILLA_PREFIX="/usr/"
    export USE_LIBPATH="/usr/lib"
    qmake-qt5 "$srcdir/qupzilla/QupZilla.pro" \
    PREFIX=/usr \
    CONFIG+=LINUX_INTEGRATED \
    INSTALL_ROOT_PATH="$pkgdir" \
    QMAKE_CFLAGS_RELEASE="${CFLAGS}" \
    QMAKE_CXXFLAGS_RELEASE="${CXXFLAGS}"
    make
    package() {
    cd ${srcdir}/qupzilla
    make INSTALL_ROOT="$pkgdir/" install
    Modified sections are:
    - in "headers" - where I add CFLAGS="something" and CXXFLAGS="something" variable and
    - in "build" section by add:
    QupZilla.pro to
    qmake-qt5 "$srcdir/qupzilla/
    in original PKGBUILD and
    CONFIG+=LINUX_INTEGRATED \
    INSTALL_ROOT_PATH="$pkgdir" \
    QMAKE_CFLAGS_RELEASE="${CFLAGS}" \
    QMAKE_CXXFLAGS_RELEASE="${CXXFLAGS}"
    But, in case of smplayer, it looks like, that is "preconfigured". There isn't *.pro file, you don't use "qmake" to preconfigure sources, and typical configuration for it is only:
    make
    sudo make install
    because everything else is in Makefile.txt. You should use another trick (I don't know which will be correct).

  • Credit memo price issue.

    Dear Experts,
    Issue:
    When I am making Credit memo req with VA01 then price is coming but when I am enter creddit req to memo with the doc no in VF01 and execute then price is not coming, please let me know where i can do correction so that i can get the right output with price.
    Its very urgent please response ASAP.
    Thanks
    Smith

    Dear Raghu.k,
    Thanks to all as per you all anyls found as mentioned below.
    When I am check the condition in vf02 then the ZPR3(Manual in credit req memo) is coming in yellow sign. I dnt know why and whn I am double click on ZPR3 then at Control Option there is one option tab INACTIVE:(W)The document item is statistical.
    I think if It will be active then ZPR3 will be green, would you please tell me where should I make conf or change it to get it active.
    One more thing is there when I am check the condition at Header level then no C.type is there.
    Please tell me the steps what should I do. its urgent plz
    Thanks.
    Smith

  • Mirrorlist Updating by way of cronie

    Goal
    I have a pfSense router with a squid cache. This caches archlinux packages. I have already wrote some (noobish/poor/mediocre) scripts on my home server to download all the packages I have. So when the script runs, it downloads the packages to the /tmp dir, in the process updating any contents of the router's cache. However, I have many arch systems in this network, and sometimes their mirrorlists differ, so we must keep those consistent.
    Therefor, the end goal of this post is to update the mirrorlist periodically based on a set of criteria. The criteria is basically that it pulls a new mirrorlist from https://www.archlinux.org/mirrorlist/?c … _status=on . This is preferably in a script, placed in /etc/cron.hourly to be ran by the cronie daemon.
    What I have
    On the server I have a script with the executable bit as follows:
    /etc/cron.hourly/archlinux_packages
    #!/bin/sh
    rm -R /tmp/pacman
    list=$(</srv/data/isos/linux/archlinux/scripts/archlinux_packages)
    mkdir -p /tmp/pacman/{i686,x86_64}/{cachedir,dbpath}
    wget "https://projects.archlinux.org/svntogit/packages.git/plain/trunk/pacman.conf.i686?h=packages/pacman" -O "/tmp/pacman/i686.conf"
    wget "https://projects.archlinux.org/svntogit/packages.git/plain/trunk/pacman.conf.x86_64?h=packages/pacman" -O "/tmp/pacman/x86_64.conf"
    pacman -Syw --noconfirm --config="/tmp/pacman/i686.conf" --cachedir="/tmp/pacman/i686/cachedir" --dbpath="/tmp/pacman/i686/dbpath" --arch=i686 $list
    pacman -Syw --noconfirm --config="/tmp/pacman/x86_64.conf" --cachedir="/tmp/pacman/x86_64/cachedir" --dbpath='/tmp/pacman/x86_64/dbpath' --arch=x86_64 $list
    rm -R /tmp/pacman
    The archlinux_packages file in line two is a plain text, space separated file of all packages to be downloaded. Following is an excerpt:
    base base-devel audacity geany gparted k3b
    On the server and every client machine I have a script with the executable bit as follows:
    /etc/cron.hourly/mirrorlist_update
    #!/bin/sh
    wget "https://www.archlinux.org/mirrorlist/?country=CA&protocol=http&ip_version=4&use_mirror_status=on" -O /etc/pacman.d/mirrorlist
    sed -i 's/^#Server/Server/g' "/etc/pacman.d/mirrorlist"
    Simple stuff. I stole line three from someone. I wish I could give credit.
    Yes, I have enabled/started the cronie daemon/service on all systems.
    Problem
    Scripts don't appear to be running. I have added logging to the mirrorlist_update script (>> /tmp/mirrorlist_update) and the file is not created.
    Scripts do run as root, right?
    Here is some possibly interesting output:
    # run-parts --test /etc/cron.hourly
    /etc/cron.hourly/0anacron
    /etc/cron.hourly/archlinux_packages
    /etc/cron.hourly/mirrorlist_update
    Also, the contents of all the /etc/pacman.d/mirrorlist files should have today's date (2014-09-19) in them, but instead they have 2014-09-18. This is from yesterday when I had tested them manually.
    I'm kinda stuck at this point. I can't prove it, but at one point during testing yesterday I was SSH'd into my server, and the time stamps on the /etc/pacman.d/mirrorlist file were accurate, and I could see the file structure in /tmp being made and populated. Is it a Schrodinger problem where I need to keep an eye on it for it to run?
    Any help is greatly appreciated. User error is great.
    I probably didn't RTFM enough like usual, right?

    I'd suggest you do not use the squid cache. Simply run pacserve on all arch machines to share packages, let your home server download the packages regularily while it runs pacserve constantly. Or maybe even build a full local mirror and use that on all machines.
    http://xyne.archlinux.ca/projects/pacserve/
    Last edited by progandy (2014-09-19 22:58:44)

  • RFC: Queries about Arch culture and community

    Good day everyone,
    This is a request for opinions from the Arch community, especially the Arch developers, Trusted Users, and long time users. I am writing a review about Arch Linux which I hope to publish within the next month or so. Unlike most distro reviews, which are actually distro installation reviews, I have devoted a lot of space to The Arch Way, unique technical qualities of Arch, day to day use and maintenance of Arch, and the Arch community. In my view, the community of a distro is much more important than its installation process.
    If I may, I would like to pose some questions about the Arch community. FWIW, I have been quietly participating in the Arch community myself for some months now, contributing material to the wiki. Anyway, please take a look at the queries below, and comment on any as you see fit.
    Thank you,
    Luke Seubert
    1. Despite its modest size, Arch has a very enthusiastic community, as evidenced by its internationalization projects, derivative distros, 3rd party repositories, Arch schwag, active forums and wiki, etc. Is this statement true or false, and if Arch does have an especially enthusiastic community, why?
    2. Arch is deeply conservative, refusing to deviate from core principles. Still, within these bounds, Arch permits a wide array of innovation. Are these statements true or false, and why? If true, what are the pros and cons of such conservatism? If false, in what way has Arch deviated from its core principles or resisted innovation?
    3. The Arch community is fairly harmonious, with little bickering, flamewars, forks or threats to fork, etc. Is this statement true or false, and why? (I have my own theory on the why of this one, and the answer in brief is... dogfood.)
    4. How good or bad a job is Arch doing in cultivating new Trusted Users and Arch developers? Does it have a formal mentoring process? It seems the most direct path to TU status is to put together packages in AUR, and eventually have them voted into Community based upon quality and popularity. However, at some point, virtually all of the popular packages will already be in Community or Extra. How does an AUR uploader become a Trusted User then?
    5. Hypothetical Scenario:
    The Chakra Project successfully completes in alpha, beta, and release candidate Live CD testing, and releases its Live CD - version 1.0 - with the GUI easy Tribe installer, to wide acclaim - DistroWatch even raves about it. Suddenly, there are lots of new Arch users, who never went through the traditional Arch install process, who never "paid their Arch dues", and who are not nearly as clueful because they never RTFW. They are flooding IRC and webforums with really, uh, "basic" questions, and suggesting/demanding new features. How does the Arch community handle this abrupt change in its culture? Has it dealt with such culture shocks before?
    6. If only you too could lift cars over your head, would you be more cool, less cool, or as cool as Phrakture, and why? What if you could only lift cars over your head after eating a can of spinach and slamming a six pack of Red Bull? Then how cool/not cool would you be by comparison?
    Last edited by lseubert (2009-08-08 13:45:07)

    Allan wrote:
    Here are my opinions on these questions and do not necessarily reflect other Arch devs...
    1. True.  I believe part of the enthusiastic community comes from the fact that Arch requires you to set up your system for yourself.  So people become very proud of their achievement of getting their system setup exactly as they like it.
    This is an excellent point. There is a nice sense of pride that comes from tweaking your Arch install to just the way you like it. And it is an involved process requiring some modicum of skill.
    Also, people have always been encouraged to contribute fixes or start projects to fulfill areas they see lacking.  Seeing your work become used by many others is always a good feeling.
    Yeah, I have noted this in my rough draft. Arch has amazingly low barriers to entry. Sign up for an AUR account, which is quick and automatic, and get to work. Your status and authority is derived from a roughly consensual meritocracy, as opposed to a hierarchical, bureaucratic process full of gatekeepers, aka potential gateclosers, like most distros.
    This simplicity extends to our package manager, which I believe is a major factor in making the AUR as popular as it is.  (Note that while pacman is developed primarily by Arch users, it aims not to be tied to any distro).
    Allan, could you clarify this comment? How does pacman make AUR popular? While I use pacman to access binaries from core, extra, and community; I use yaourt to handle PKGBUILDs from AUR. I don't quite follow you on this one.
    But as always, the principles guiding Arch do get bent when it is sensible to do so.  It was always said we don't split packages like many other distros, but we do some splitting these days (e.g. gcc-libs, KDE).  We now include info pages and other docs.
    Both of which are good moves. A system should have documentation built in, for those occasions when internet access is down. And I might actually take a look at KDE 4 once again, now that I wouldn't have to download a pile of unwanted packages.
    3. There are flame-wars every so often...  The last one that was probably quite obvious to many was changing rules governing the community repo (requiring votes or 1% usage as defined by pkgstats) and the move to using the official db-scripts (which may be seen as making the TUs less independent).
    That is a flamewar that I missed. How does Arch resolve difficult issues? There is no Constitution that I could find, nor any formal governing structure. Is it as simple as lengthy debate, and then Dred Overlord Phrakture decrees?
    I have never heard of a treat to fork the distro or components of it.  I guess that is because of the attitude of show us a working implementation of a good idea and it will possibly become official.
    Well, there aren't forks, but there are a lot of derivative distros, some of them with very different goals. And there are a lot of 3rd party repositories out there, outside of AUR. I wouldn't call that forking, but it is, I guess, extending. I think such experimentation is a good thing - really good ideas might be developed outside of even AUR, and eventually brought back into the Arch ecosystem. I believe some of Xyne's packages got started that way, yes?
    Here is an interesting factoid I came up with in my research:
    Packages Per Maintainer Ratio - how many packages on average does a maintainer support?
    For Debian, the P/M Ratio is 28
    When you add up all the Arch Devs and TUs, and divide out the packages in core, extra, and community, the Arch P/M Ratio is 67.
    Arch devs seem quite impressive, until you recall that they mostly maintain one version of each package and for only two architectures, whereas Debian devs support 11 architectures for 5 versions - experimental, unstable, testing, current stable, and old stable. (Ugh - is that brutal or what?)
    Seen in that light, one has to admire the very hardworking Debian devs, and wonder a bit about those Arch dev slackers. Yet another T-shirt idea! Change the first idea so it now reads, "I'm a slacker Arch developer, and I eat my own dogfood!"

  • Archlinux.log EOF.

    Well, I guess this is a goodbye.
    All in all, archlinux was a pleasant experience. Yet, there were points that were not satisfying me. Some were related to Arch, some others not at all, and some not even related to linux and computing.
    Basically:
    - Due to various reasons, I can't cope anymore with the rolling release model.
    - Recent progress in various areas (init, gnome, gtk, X, udev, hal, dbus, kernel, etc...) make some other distros attractive again (features, or lack of it that made me lean towards bleeding-edge previously).
    - Not to sound paranoid, but the lack of package signing in pacman makes me feel uneasy.
    - I like to experience some other things from time to time (and to their full extend, not just popping a livecd in, or in a VM)
    - Blah, blah, blah.
    So I picked up Ubuntu, which I installed (successfully) on many (both tech-savvy and computer illiterates) people computers beginning in the linux world, but never really used myself. I decided to take a look at 7.10 Tribe 5 and was really surprised to be able to match my current Arch in terms of technology. Surprised enough to stick with it.
    That said, I consider Arch an excellent distro, both a young one and one that will without a doubt thrive even more in the future, certainly matching the other big names. And I will certainly come back in a bunch of years...
    To close this post of mine, I'd like to thank both Judd Vinet & the devs, and the community altogether, which is a rather unique one, at least for its flameproofness. Oh yes I really enjoyed reading/asking questions like what's the best FS & the likes and actually get useful, educated answers, and 100% pollution-free.
    Thank you all, and see you later.
    Last edited by lloeki (2007-09-18 12:54:46)

    delphiki wrote:Its funny how after getting comfortable in slackware and coming to Arch how things that seem 'complicated' or 'too difficult' for some users seem 'natural' for me where what those users consider 'natural and easy' seems 'complicated and difficult'. I guess its just one of those things that KISS does to you after a long time
    So true, so true

Maybe you are looking for

  • Problem while uploading Portal Theme into R/3 System?

    Hello Guru's I am trying to upload Portal Theme into R/3 system. We have a program which will upload to a given path. T.Code SE38 Program name BSP_update_mimerepos. When I upload the theme using the program I get some folders, like Common, r, UR when

  • Medium in output type

    Dear all, I'm in the midst of figuring how ALE being sent out via message control. While looking at a Sales order's output type setting screen, under Medium column it contains: 1. Print output 2. Fax 3. Telex 4. External send 5. Simpal mail 6. Specia

  • F90 bug on solaris x86

    Hello, I have a short code to show a curious bug on solaris x86 when i compil it with f90 -O3. Where can i send it to show this bug ? Thanks

  • Create a Business partner

    Hi Specialist I have some invoices in my transaction FBL5N according to one customer.  But if I am try to display my worklist i can't see the invoices... THen I tried to check the business partner and it isnt exist. Could you let me know the program

  • What setting for .MP4 using Magic Video Converter?...

     What setting do you use for best video when converting video files to .MP4 using Magic Video Converter?? To play on Nokia N95 8gb. After you have chose to convert to MP4, you can chose a load of diffrent "setting/format" for the MP4 file. But what w