Software error:
Can't locate Math/Random/ISAAC.pm in #INC (#INC contains: . lib /usr/local/lib/perl5 /usr/local/share/perl5 /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5 /usr/share/perl5) at Bugzilla/RNG.pm line 28.
BEGIN failed--compilation aborted at Bugzilla/RNG.pm line 28.
Compilation failed in require at Bugzilla/Util.pm line 50.
BEGIN failed--compilation aborted at Bugzilla/Util.pm line 50.
Compilation failed in require at Bugzilla/Error.pm line 33.
BEGIN failed--compilation aborted at Bugzilla/Error.pm line 33.
Compilation failed in require at Bugzilla/Install/Filesystem.pm line 31.
BEGIN failed--compilation aborted at Bugzilla/Install/Filesystem.pm line 31.
Compilation failed in require at Bugzilla/Config.pm line 38.
BEGIN failed--compilation aborted at Bugzilla/Config.pm line 38.
Compilation failed in require at Bugzilla.pm line 38.
BEGIN failed--compilation aborted at Bugzilla.pm line 38.
Compilation failed in require at /var/www/html/bugzilla/index.cgi line 34.
BEGIN failed--compilation aborted at /var/www/html/bugzilla/index.cgi line 34.
For help, please send mail to the webmaster (root#localhost), giving this error message and the time and date of the error.
This is the error given on executing the file index.cgi in server
This mostly looks like a missing library. You can gets informations on this by looking at the output of:
./checksetup.pl --check-modules
see: Bugzilla Installation
If this is not sufficient for you, you would need to post more informations here ( version of Bugzilla, os, etc... )
Alexis
Edit:
The original error indicate a missing module: at least you will need to install Math::Random:ISAAC. The full missing requirements should be displayed by checksetup.pl, but it seems in some occasions this also crashes when ISAAC is missing ( see 4.2: checksetup.pl crashes when Voting extension enabled )
Related
After I logged in our website,
Parse error: syntax error, unexpected T_ECHO, expecting T_PAAMAYIM_NEKUDOTAYIM in /home/hyuny276/public_html/ubpserver.com/view/template/common/home.tpl on line 291
line 291:
%</td -->
There must be any syntax error in your home.tpl
Check if any PHP tag is not closed at line 291.
Check if any semicolon in PHP code is left at line 291.
You can check syntax error in Netbeans IDE for PHP. Just open the file in IDE.
Hope it helps.
I would be glad to make the code documentation of our big project, http://www.diracprogram.org, which is a mixture of F90, F77, Fortran include files, C and C++ source code files. Plus a lot of preprocessor statements (mainly in Fortran files).
I am using Doxygen 1.8.6, and playing with the Doxygen.in configuration file and the doxygen debug statements.
Fortran is the main language.
As you can see, there is a lot of errors. Any clue how to track, understand them and then adapt the Fortran source files accordingly?
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/utils/mx2fit.F90 line: 621, state: 21
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/utils/polfit.F90 line: 168, state: 21
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/utils/twofit.F90 line: 310, state: 21
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/amfi/amfi3.F line: 2824, state: 4
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/cc_external/hsfscc/chp_11a.F90 line: 1993, state: 21
********************************************************************
parse error in end <scopename>********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/dirac/dirbss.F line: 7884, state: 6
********************************************************************
/home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/include/dcbgascip.h:37: warning: Found ';' while parsing initializer list! (doxygen could be confused by a mac
ro call without semicolon)
/home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/include/dcbham.h:50: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro
call without semicolon)
parse error in end <scopename>********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/krmc/krmcgascip.F line: 4684, state: 6
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/reladc/adccore.F line: 7170, state: 19
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/reladc/adcdble.F line: 2871, state: 10
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/reladc/adcdiag.F line: 4813, state: 10
********************************************************************
********************************************************************
Error in file /home/ilias/Dokumenty/Work/QCH/software/dirac_git/working_trunk/src/reladc/adcexci.F line: 1995, state: 10
********************************************************************
make[3]: *** [CMakeFiles/doxygen] Segmentation fault (core dumped)
make[3]: Target `CMakeFiles/doxygen.dir/build' not remade because of errors.
make[2]: *** [CMakeFiles/doxygen.dir/all] Error 2
make[1]: *** [CMakeFiles/doxygen.dir/rule] Error 2
make[1]: Target `doxygen' not remade because of errors.
make: *** [doxygen] Error 2
First I assume that the code compiles correctly.
It is also advised to upgrade to the newest version of doxygen (currently 1.8.8) as a number of problems might be solved.
Best way to track down is (unfortunately in case of the state errors the reported line number is, most of the time, of no use):
- study the doxygen code
- for each file run doxygen on it separately and try to solve the problem by e.g. reducing the file till the error disappears and conclude from this what was wrong.
- build doxygen yourself and run with flex in debug mode / add print statements
For each of the *.F90 lines you should see in the output line similar to:
Preprocessing .../a.F90...
Parsing file .../a.F90...
for each *.f90 file:
Reading .../a.f90...
Parsing file .../a.f90...
for each *.F file:
Preprocessing .../a.F...
Prepassing fixed form of .../a.F
Parsing file ...a.F...
for each *.f file:
Reading .../a.f...
Prepassing fixed form of .../a.f
Parsing file .../a.f...
When this is not the case the file is not properly recognized as free formatted Fortran / fixed formatted code and doxygen might get confused.
This can be accomplished by defining in the Doxyfile:
EXTENSION_MAPPING = f=FortranFixed f90=FortranFree
(this is possible since version 1.8.7 of doxygen)
when this is not possible set in the first column of the first line of a *.f / .F file a 'C'. 'c' or ''.
On the site of www.diracprogram.org I could not find the source code, is it possible to share (part?).
Now something about the different states, they come from fortranscanner.l (for a solution I have to make a guess):
state: 4
SubprogBody: probably due to not properly closed / recognized subroutine body in fixed formatted code (as it is a .F file, so add 'C' ...)
state: 6
Start: probably due to not properly closed / recognized start condition in fixed formatted code (as it is a .F file, so add 'C' ...)
state: 10
ModuleBody: probably due to not properly closed / recognized module body in fixed formatted code (as it is a .F file, so add 'C' ...)
state: 19
InterfaceBody: probably due to not properly closed / recognized interface in fixed formatted code (as it is a .F file, so add 'C' ...)
state: 21
String: string not properly closed string or string quotes somewhere in comment
I just moved over to a new MacBook Air (10.8) and a 64-bit project that compiled before gives me Shell Script Invocation Error: /bin/sh failed with exit code 2
It looks like XCode 4.6 is failing on one of the intermediate files, saying unexpected EOF while looking for matching '"' in a file ending in .sh:
/Users/billferster/Library/Developer/Xcode/DerivedData/MovingPicture-hcmztqjnatzylkburxulgmdynyqg/Build/Intermediates/MovingPicture.build/Debug/MovingPicture.build/Script-E004D330137B9E5B00FDC604.sh: line 6: unexpected EOF while looking for matching `"'
/Users/billferster/Library/Developer/Xcode/DerivedData/MovingPicture-hcmztqjnatzylkburxulgmdynyqg/Build/Intermediates/MovingPicture.build/Debug/MovingPicture.build/Script-E004D330137B9E5B00FDC604.sh: line 7: syntax error: unexpected end of file
Command /bin/sh failed with exit code 2
Any ideas how to fix this?
Thank
Bill
it was was it said it was. A missing "
I use openSUSE as my OS,and gdb 7.5. I want to debug my programs with gdb, with breakpoints. But when I make a breakpoint, and then run my program, gdb informs me as follows :
Error in re-setting breakpoint 1: malformed linespec error: unexpected string, ".cpp"
Its same in all of my programs. Also, when run to the breakpoint ,the program doesnt' stop at all. Can any one tell me what's wrong?
I download the latest gdb and install it ,the former message is gone ,but when run gdb it tells me that :
warning: Could not load shared library symbols for linux-gate.so.1. Do you need "set solib-search-path" or "set sysroot"?
how to slove this problem?
There is a known bug in gdb 7.5 where the debugger fails to parse the linespec when the source file name starts with a decimal digit. See this message for details.
Try renaming the file and update gdb from your distribution repository. If the bug persists, file a bug with your distribution maintainers.
See a sample session from a bug report submitted to gdb bugzilla.
(gdb) b 3
Breakpoint 1 at 0x4004c3: file 2.c, line 3.
(gdb) r
Starting program: /home/teawater/tmp/a.out
Error in re-setting breakpoint 1: malformed linespec error: unexpected string, ".c"
Error in re-setting breakpoint 1: malformed linespec error: unexpected string, ".c"
Error in re-setting breakpoint 1: malformed linespec error: unexpected string, ".c"
Error in re-setting breakpoint 1: malformed linespec error: unexpected string, ".c"
I use "b + linenumber"
This defines a breakpoint relative to the current line, see als Specifying a Location. With the code from your comment below, the following would work:
$ gdb ./main
(gdb) b +5
Breakpoint 1 at 0x40139c: file main.cpp, line 6.
(gdb) run
[New Thread 1528.0x1930]
Breakpoint 1, main () at main.cpp:5
5 while(scanf("%d%d",&a,&b)!=EOF)
Unless there is a good reason to specify relative line numbers, I suggest that you use absolute line numbers or function names:
(gdb) b main
Breakpoint 1 at 0x401395: file main.cpp, line 3.
(gdb) b main.cpp:6
Breakpoint 1 at 0x40139c: file main.cpp, line 6.
I am using gdb to debug a fortran90 program, myprog.f90, that uses some modules, say mod1 and mod2.
I launch gdb...
$ gdb ./program
and try to set a line break...
(gdb) break 80
but I receive the error "No line 80 in file 'mod1.f90'".
So although I am trying to set a line break in myprog.f90, it's trying to set the line break in the first module of the program mod1.
How do I break a line in and step through myprog.f90?
Thank you.
Do this:
(gdb) break myprog.f90:80
See also documentation on setting breakpoints, and on location specification.