[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Fwd: Powerpc user help requested wrt Bug#388423: stealth: empty package on powerpc

Hello debian-powerpc,

	We would appreciate some assistance while tracing a possibly bug of icmake on 
that architecture. The package which triggers and could help to reproduce 
that icmake issue is stealth 1.45-1 which could be found at:


Note: stealth 1.45-2 has been uploaded to Sid (which is fine now on powerpc), 
but that is just a work-around for the icmake issue, thus we are interested 
to track the icmake issue itself. Please read below for full description of 
the problem.

Please CC, we are not subscribed to debian-powerpc@l.d.o.
Thanks for your cooperation.

----------  Forwarded Message  ----------

Subject: Powerpc user help requested wrt Bug#388423: stealth: empty package on 
Date: Saturday 23 September 2006 15:07
From: "Frank B. Brokken" <f.b.brokken@rug.nl>
To: debian-mentors@lists.debian.org
Cc: George Danchev <danchev@spnet.net>, Francesco Paolo Lovergine 

Dear mentor-readers,

    Recently, I ran into the following problem, which I'm unable to solve
unless a powerpc (PPC) user is willing/able to assist by either performing
some tests in collaboration with me, or by (temporarily) offering me an

    Here's the problem:

On packages.debian.org [1], the PPC package of stealth 1.45-1 appears to
be empty. It's the only platform showing this peculiarity, and since I
currently have no access to a PPC, it's very hard to find out what caused
this. The buildd log [2] shows a strange series of three `rm -rf' logs,
instead of the proper installation.

    The following would be helpful:

    1. install `icmake', and obtain the stealth source package [1].

    2. Untar the stealth archive, and from the top-level directory
(stealth-1.45) run the following commands:

        ./build install /tmp

    This command will fail, since nothing has been built yet, but it
 shouldn't do the `rm -rf' things that show up in the buildd logs.

    If this works well and if stealth's other build-requirements are
 installed to, (libbobcat1-dev (>= 1.9.0), yodl (>= 2.01.03), g++ (>= 4.0.0),
 tetex-bin, tetex-extra, and gs | gs-gpl a full manual build might be

        ./build distclean
        ./build manual
        ./build man
        ./build program
    and then:
        ./build install /tmp

    Saving all output of the build process and making it available to me
 would of course be greatly appreciated.

    2. Another test would be to reorder the flow-control in the build script
and see what happens next. Looking at the build-script you'll see the
following code-section:

        option = element(1, argv);

        if (option == "clean")

        if (option == "distclean")

        if (option == "install")
            install(element(2, argv));

        if (option == "man")

        if (option == "manual")

        if (option == "program")

        One of the things that might be worth investigating is what happens
when these alternatives are reordered. E.g., by placing the
 clean-alternatives at the end:

        option = element(1, argv);

        if (option == "install")
            install(element(2, argv));

        if (option == "man")

        if (option == "manual")

        if (option == "program")

        if (option == "clean")

        if (option == "distclean")

    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 on the standard output stream. 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 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, receiving the binary .bim file would be

    As an alternative, if somebody could offer me a (temporary) account on
his/her PPC, I could perform the tests myself, which would of course reduce
the need to request and communicate the results of possibly many tests.

[1] http://packages.debian.org/unstable/admin/stealth

If you're able to help, its probably best to contact me on my
f.b.brokken@rug.nl address.

Thanks in advance for any offered assistance,

[Cc: George Danchev, Francesco Paolo Lovergine]

    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


pub 4096R/0E4BD0AB 2003-03-18 <people.fccf.net/danchev/key pgp.mit.edu>
fingerprint 1AE7 7C66 0A26 5BFF DF22 5D55 1C57 0C89 0E4B D0AB 

Reply to: