You are not logged in.

#1 2020-10-19 14:21:38

miomio
Member
Registered: 2016-01-17
Posts: 167

How do I find what make options sw in repo had been compiled with?

[SOLVED]

For example, how do I find out what qemu from the repo via pacman was compiled with?

Useful to know because if I'm t-shooting a problem running, e.g. qemu, but the error is because of an option that wasn't passed to GCC when the software was built, then if I don't know how to check/find out it delays t-shooting.

https://at.projects.genivi.org/wiki/dis … celeration

Last edited by miomio (2020-10-19 14:45:17)

Offline

#2 2020-10-19 14:38:19

schard
Forum Moderator
From: Hannover
Registered: 2016-05-06
Posts: 2,609
Website

Re: How do I find what make options sw in repo had been compiled with?

You can see the used options in the PKGBUILD:

build() {
  _build full \
    --audio-drv-list="pa alsa sdl jack"

  _build headless \
    --audio-drv-list= \
    --disable-sdl \
    --disable-gtk \
    --disable-vte \
    --disable-brlapi \
    --disable-opengl \
    --disable-virglrenderer
}

_build() (
  cd build-$1

  ../${pkgname}-${pkgver}/configure \
    --prefix=/usr \
    --sysconfdir=/etc \
    --localstatedir=/var \
    --libexecdir=/usr/lib/qemu \
    --extra-ldflags="$LDFLAGS" \
    --smbd=/usr/bin/smbd \
    --enable-modules \
    --enable-sdl \
    --enable-slirp=system \
    --enable-xfsctl \
    "${@:2}"

  make

You could read them from any ELF binary also, iff the flag -frecord-gcc-switches would have been used via e.g.

readelf -p .GCC.command.line /usr/bin/qemu-system-x86_64

but it was not. This may be some nice feature to improve the move towards reproducible builds.

Last edited by schard (2020-10-19 14:39:30)


Inofficial first vice president of the Rust Evangelism Strike Force

Offline

#3 2020-10-19 14:39:29

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,104

Re: How do I find what make options sw in repo had been compiled with?

Look at the PKGBUILD https://wiki.archlinux.org/index.php/Arch_Build_System

Also you are asking many disjoint and unrelated leading questions towards your bigger issue. Instead of you opening a thread for each little thing you are having an issue with I'd suggest you collect your thoughts and ask for help with whatever actual issue you are having/problem you are trying to solve.

Offline

Board footer

Powered by FluxBB