Am 28.02.2013 22:18, schrieb Dan Fandrich: > On Thu, Feb 28, 2013 at 03:25:41PM +0100, Guillaume Rousse wrote: >> Build dependencies are usually specified in installation >> instructions. For humans, of course. You may also try to parse the >> outpout of ./configure (or equivalent) script. In both case, there is >> not garanty then every build dependency will get specified. > The other way is to work backwards by looking at the install dependencies > that rpmbuild discovered, or the NEEDED lines from objdump -x, and adding the > -devel versions of those libraries. That won't catch any compile-time-only > dependencies, though (like libtool, autoconf or flex) but it will give you > something to start from. Note also that some programs will automatically > discover what optional libraries are available at build time and configure > themselves accordingly. So, if you miss some BuildRequires, you might end up > with a binary that works but is missing features. > >>>> Dan Or you could try to use iurt, which basically does what the buildsystem does, but it either needs a local Mageia mirror, or fast internet connection, or some patience ;)
As the buildsystem can only be used by those with full packager accounts, iurt is the corresponding alternative for padawans and everybody else. https://wiki.mageia.org/en/Packagers_Mentoring_Howto#iurt
