Here is the specific problem, I'm having because the build file isn't seemingly being utilized. Basically, perl-dbi is failing to build and giving this error:
openpkg:build:FATAL: errors occured while building: perl-dbi-5.8.8-2.20061018: perl-dbi searches a frood called 'sqlite' I'm using this command to generate the rebuild script after which it is executed giving the aforementioned error: openpkg build -r /usr/local/RPM/OPKG/TMP/2-STABLE-20061018/SRC -f /usr/local/RPM/OPKG/TMP/2-STABLE-20061018/SRC/updates_index.rdf -A -U The build file that resides at /usr/local/.openpkg/build (the generic opkg user account) contains the following lines which pertain to perl-dbi options: -Dperl-dbi::with_dbd_mysql = yes -Dperl-dbi::with_dbd_pgsql = yes -Dperl-dbi::with_dbd_sqlite = no Note here that I am disabling sqlite because we do not want it installed on our systems, so we don't build it. Thus, if perl-dbi were to build with default options, it would require sqlite which is what it is doing and why it looks like the build file is not being recognized/used. Also, perl-dbi is not the only package that is not building with the options we specified within the build file. This is actually a fairly serious issue for us because we change a lot of the default options in packages when we do our rebuild. Also, just to rule it out, I linked ~root/.openpkg to /usr/local/.openpkg and I even copied the same build file into my own ~/.openpkg and tried letting it build with each of these changes with no difference in outcome. :-( Anybody have any ideas why suddenly the build options in the build file would just stop being recognized? On Mon, 2007-05-14 at 14:34 -0700, David M. Fetter wrote: > Well, we run the openpkg build command on our build servers as the opkg > user account and I have the build file (which contains rpm build options > only) located under /usr/local/.openpkg/build which would be the opkg > user's home directory. Should this setup recognize the build file or do > I need to also have it reside in root's home directory? I would expect > the way I set it up to work but it's not because openpkg build is > generating a build script that does not have the options I specified in > the build file. > > On Sun, 2007-05-13 at 04:03 +0200, Torsten Homeyer wrote: > > Ralf S. Engelschall wrote: > > > On Fri, May 11, 2007, David M. Fetter wrote: > > > > > >> Is the ~/.openpkg/build file still being acknowledged by openpkg-tools? > > >> It seems that it is no longer being adhered too when doing the build to > > >> create the build script. I just want to make sure this method wasn't > > >> obsoleted somewhere along the lines. > > > > > > "openpkg build" honors it and it works just fine for me. Here is an > > > example ~rse/.openpkg/build from one of my private boxes: > > > > > > ---------------------------------------------------- > > > [/usr/opkg] > > > -r /v/openpkg/SRC/CURRENT > > > -P sudo > > > -N sudo > > > -E j2se > > > > > > [/v/p2p/sw] > > > -r /v/openpkg/SRC/CURRENT > > > -P sudo > > > -N sudo > > > > It's behavior chnaged some time ago due to the fact that certain actions > > within the openpkg command run under the different user IDs of the > > OpenPKG hirarchy. Linking my ~/.openpkg/build file to all the > > /PREFIX/.openpkg directories did the trick for me. > > > > Regards, > > Torsten > > -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu
signature.asc
Description: This is a digitally signed message part
