Re: [LTP] ltp not compiling due to ballista error

Subrata Modak Wed, 25 Jul 2007 01:18:36 -0700

Has anybody encountered such problem(below) before as Daniel ??
Regards--
Subrata


Daniel Doughty wrote:

Thanks for the reply.

1)  I do have perl installed.

[EMAIL PROTECTED] ballista]# which perl
/usr/local/bin/perl
[EMAIL PROTECTED] ballista]# perl -version

This is perl, v5.8.8 built for x86_64-linux

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the ArtisticLicense or the

GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on

this system using "man perl" or "perldoc perl". If you have accessto the

Internet, point your browser at http://www.perl.org/, the Perl Home Page.

2)  permissions look good:

-rwxr-xr-x  1 root root 9482 Jun 28 05:19 ./configure

3)  tried and failed to run as root manually:

[EMAIL PROTECTED] ballista]# ./configure
-bash: ./configure: Permission denied

Really not sure what else is going wrong. I extracted the files asroot in /tmp with a gunzip ltp*.gz;tar xvf ltp*tar


Let me know if you think of anything else.

Thanks,
Dan

On 7/24/07, *Subrata Modak* <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote:


    Hi Daniel,
    There can be various reasons for which this is not behaving
    correctly.
    1) You must have Perl installed in your machine. ./configure
    looks for perl which actually generates the Makefile. Without
    Makefile being generated you cannot move forward,
    2) Check the permission bits in ./configure. You should have
    permissions to execute ./configure
    3) You can also try to execute the same under root privileges

    I have attached a doc which shows you success of latest LTP build
    (ltp-full-20070630)
    Regards--
    Subrata


    Daniel Doughty wrote:

    I should mention that the configure file doesn't exist where the
    Makefile is expecting it:

    [EMAIL PROTECTED] ltp-full-20070430]# cd
    /tmp/ltp-full-20070430/testcases/ballista
    [EMAIL PROTECTED] ballista]# ls
    ballista  create.sh   do_nothing.sh  Makefile  README

    and that make install fails miserably if I attempt to ignore the
    compile problem.

    Thanks,
    Dan

    On 7/21/07, * Daniel Doughty* <[EMAIL PROTECTED]
    <mailto:[EMAIL PROTECTED]>> wrote:

        I've tried the current and the last two full releases yet
        nothing will compile.  I've googled for problems for about
        an hour and can find no evidence of anyone else running into
        this.  Any ideas what's going on?:

        [EMAIL PROTECTED] tmp]# cd ltp-full-20070430
        [EMAIL PROTECTED] ltp-full-20070430]# make
        make[1]: Entering directory `/tmp/ltp-full-20070430/lib'
        cc -Wall  -I../include  -Wall    -c -o dataascii.o dataascii.c
        cc -Wall  -I../include  -Wall    -c -o databin.o databin.c
        cc -Wall  -I../include  -Wall    -c -o datapid.o datapid.c
        cc -Wall  -I../include  -Wall    -c -o file_lock.o file_lock.c
        cc -Wall  -I../include  -Wall    -c -o forker.o forker.c
        cc -Wall  -I../include  -Wall    -c -o get_high_address.o
        get_high_address.c
        cc -Wall  -I../include  -Wall    -c -o open_flags.o open_flags.c
        cc -Wall  -I../include  -Wall    -c -o parse_opts.o parse_opts.c
        cc -Wall  -I../include  -Wall    -c -o pattern.o pattern.c
        cc -Wall  -I../include  -Wall    -c -o random_range.o
        random_range.c
        cc -Wall  -I../include  -Wall    -c -o rmobj.o rmobj.c
        cc -Wall  -I../include  -Wall    -c -o search_path.o
        search_path.c
        cc -Wall  -I../include  -Wall    -c -o self_exec.o self_exec.c
        cc -Wall  -I../include  -Wall    -c -o string_to_tokens.o
        string_to_tokens.c
        cc -Wall  -I../include  -Wall    -c -o str_to_bytes.o
        str_to_bytes.c
        cc -Wall  -I../include  -Wall    -c -o tlibio.o tlibio.c
        cc -Wall  -I../include  -Wall    -c -o tst_cwd_has_free.o
        tst_cwd_has_free.c
        cc -Wall  -I../include  -Wall    -c -o tst_is_cwd_tmpfs.o
        tst_is_cwd_tmpfs.c
        cc -Wall  -I../include  -Wall    -c -o tst_kvercmp.o
        tst_kvercmp.c
        cc -Wall  -I../include  -Wall    -c -o tst_res.o tst_res.c
        cc -Wall  -I../include  -Wall    -c -o tst_sig.o tst_sig.c
        cc -Wall  -I../include  -Wall    -c -o tst_tmpdir.o
        tst_tmpdir.c
        cc -Wall  -I../include  -Wall    -c -o write_log.o write_log.c
        ar -cr libltp.a dataascii.o databin.o datapid.o file_lock.o
        forker.o get_high_address.o open_flags.o parse_opts.o
        pattern.o random_range.o rmobj.o search_path.o self_exec.o
        string_to_tokens.o str_to_bytes.o tlibio.o
        tst_cwd_has_free.o tst_is_cwd_tmpfs.o tst_kvercmp.o
        tst_res.o tst_sig.o tst_tmpdir.o write_log.o
        make[1]: Leaving directory `/tmp/ltp-full-20070430/lib'
        make[1]: Entering directory `/tmp/ltp-full-20070430/pan'
        cc -Wall  -w    -c -o pan.o pan.c
        cc -Wall  -w    -c -o zoolib.o zoolib.c
        cc -Wall  -w    -c -o splitstr.o splitstr.c
        cc   pan.o zoolib.o splitstr.o -lm  -o pan
        cc -Wall  -w    -c -o bump.o bump.c
        cc   bump.o zoolib.o -lm  -o bump
        cc -Wall  -w    -c -o scanner.o scanner.c
        lex -l -t scan.l > scan.c
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 179: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 179: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 133: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 133: warning, dangerous trailing context
        "scan.l ", line 160: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 160: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 111: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 111: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l", line 171: warning, dangerous trailing context
        "scan.l", line 171: warning, dangerous trailing context
        "scan.l", line 236: warning, dangerous trailing context
        "scan.l ", line 97: warning, dangerous trailing context
        "scan.l", line 97: warning, dangerous trailing context
        cc -Wall  -w    -c -o scan.o scan.c
        cc -Wall  -w    -c -o reporter.o reporter.c
        cc -Wall  -w    -c -o tag_report.o tag_report.c
        cc -Wall  -w    -c -o symbol.o symbol.c
        cc -Wall  -w    -c -o debug.o debug.c
        cc   scanner.o scan.o reporter.o tag_report.o symbol.o
        splitstr.o debug.o -lm  -o scanner
        rm scan.c
        make[1]: Leaving directory `/tmp/ltp-full-20070430/pan'
        make[1]: Entering directory `/tmp/ltp-full-20070430/testcases'
        make[2]: Entering directory
        `/tmp/ltp-full-20070430/testcases/ballista'
        cd ballista ; ./configure
        /bin/sh: ./configure: Permission denied
        make[2]: *** [.configured] Error 126
        make[2]: Leaving directory
        `/tmp/ltp-full-20070430/testcases/ballista'
        make[1]: *** [all] Error 2
        make[1]: Leaving directory `/tmp/ltp-full-20070430/testcases'
        make: *** [all] Error 2
        [EMAIL PROTECTED] ltp-full-20070430]# uname -a
        Linux db1.noneofyourbusinessthankyouverymuch.com
        <http://db1.noneofyourbusinessthankyouverymuch.com>
        2.6.9-42.0.10.ELsmp #1 SMP Tue Feb 27 09:40:21 EST 2007
        x86_64 x86_64 x86_64 GNU/Linux

--Triathlon isn't in my DNA. I wasn't born lean and long of

    limb.  I don't have the dolphinesque ease of Ian Thorpe.  I
    don't run a mile in 4 minutes.  I bought my bike used and half
    of my gear was handed down from friends.  But I am a triathlete

and I will be an Ironman because nothing can stop me.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Re: [LTP] ltp not compiling due to ballista error

Reply via email to