Dear Niko Tyni, you wrote: > > Package: stealth > Version: 1.45-1 > Severity: important > > Hi, > > as seen on packages.debian.org [1], the powerpc package of stealth 1.45-1 > is empty. I don't see anything obviously wrong in the buildd log [2], > so I have no idea if this is a buildd problem. > > [1] http://packages.debian.org/unstable/admin/stealth > [2] > http://buildd.debian.org/fetch.php?&pkg=stealth&ver=1.45-1&arch=powerpc&stamp=1157481042&file=log&as=raw >
As George already wrote: thanks for reporting this problem. As you also have read, your problem was confirmed by othre powerpc users, although I'd rather had them report the *solution* :-) Looking at the build logs, the impression is formed that when the build script should do `install' it actually does a `clean'. Now solving the problem (or even getting confirmation of the impression we have) is complicated by the fact that neither George nor I has access to a powerpc. Maybe you can help doing the following: 1. A simple test would be to do things `by hand'. E.g., from the directory in which you found the build-script, do ./build distclean ./build manual ./build man ./build program and, e.g, ./build install /tmp If this works it would at least tell us that it's not a pure icmake-related problem. 2. Another test would be to reorder the flow-control in the build script. Looking at the build-script you'll see the following code-section: option = element(1, argv); if (option == "clean") clean(0); if (option == "distclean") clean(1); if (option == "install") install(element(2, argv)); if (option == "man") manpage(); if (option == "manual") manual(); if (option == "program") program(); One of the things that might be worth investigating is what happens when these alternatives are reorederen. E.g., by placing the clean-alternatives at the end: option = element(1, argv); if (option == "install") install(element(2, argv)); if (option == "man") manpage(); if (option == "manual") manual(); if (option == "program") program(); if (option == "clean") clean(0); if (option == "distclean") clean(1); followed by rebuilding the package. 3. Finally, I would be interested in inspecting the compiled build script. To obtain the compiled script, the following would be required: $ mv build build.im $ icmake -c build.im $ mv build.im build This produces a file build.bim which is the byte-compiled script. The command `icmun build.bim' should produce (after some initial tables) a long list of assembler-like instructions. It would be nice to know if icmun runs fine on the build.bim file, and I would very much like to have that .bim file. It's probably a lot of things to ask, but I would greatly appreciate your help by performing as many of the above tests as possible. If you run a test, could you save the produced output on file, and send me the output? With test 3 the output is not useful. Instead, the binary .bim file would be appreciated. My apologies for the inconvenience, caused by not having access to a power PC. Kind regards, [Cc: George Danchev] -- Frank B. Brokken Computing Center, University of Groningen (+31) 50 363 9281 Public PGP key: http://pgp.surfnet.nl:11371/ Key Fingerprint: 8E36 9FC4 1DAA FCDF 1A0D B19F DAC4 BE50 38C6 6170
signature.asc
Description: Digital signature