AMBER Archive (2007)

Subject: AMBER: Fwd: Serial "make" failure with xleap

From: Francesco Pietra (chiendarret_at_yahoo.com)
Date: Fri Jun 29 2007 - 12:26:54 CDT


I forgot to ask: is "make" failure really limited to xleap or to all leap?
The information below should tell.

--- Francesco Pietra <chiendarret_at_yahoo.com> wrote:

> Date: Fri, 29 Jun 2007 10:17:39 -0700 (PDT)
> From: Francesco Pietra <chiendarret_at_yahoo.com>
> Subject: Serial "make" failure with xleap
> To: amber_at_scripps.edu
>
> Hi all. Thanks for considering this installation issue. I agree with David's
> comments below and Bud's comments before. I must also add that, although not
> needed, a better look at the info on my system reveals that OpenGL is
> available
> on my system. What is only lacking is 3D acceleration. It is at 2D, am fine
> at
> that.
>
> On reading the comments and amber's manual, I would still be happy if xleap
> succumbs to "make". Debian is a standard linux, so this failure must be due
> to
> something that can be put in order. Though, I can't ask for so much attention
> to my system. The only move from my side is to recollect information - that
> is
> now sparse on the mailing list - on both the "make" attempt and the X system
> aid to perhaps someone discovering ON THE FLY where the remedy can be. It
> might
> help future debian users, if the issue has to do with debian at all.
>
> Sincere thanks to all in any case, I look forward enjoying with amber as soon
> as possible.
>
> francesco
>
> The information follows:
>
> MAKE ISSUE
>
> Other than chown, also run
>
> chgrp -R username
>
> on /usr/local/amber9
>
>
> cd $AMBERHOME/src/
>
> I removed previous config.h
>
>
> ./configure -static ifort_x86_64
>
> This created new config.h
>
>
> make clean
>
>
> make
>
>
> After a long session it exited with Error 2
>
> Those errors that I can see on the screen comprise:
>
> WcActCB.c:1448: error: expected declaration specifiers before XEvent.
>
> WcActCB.c:1448: error: expected declaration specifiers before Cardinal.
>
>
> WcActCB.c: In function WcDynamicActionACT:
>
> WcActCB.c:1450: error: expected declaration specifiers before Widget.
>
> WcActCB.c:1450: error: expected declaration specifiers before XEvent.
>
> WcActCB.c:1450: error: expected declaration specifiers before Cardinal.
>
>
> WcActBC.c: In function WcDynamicCallbackACT:
>
> WcActCB.c:1452: error: expected declaration specifiers before Widget.
>
> WcActCB.c:1452: error: expected declaration specifiers before XEvent.
>
> WcActCB.c:1452: error: expected declaration specifiers before Cardinal.
>
>
>
> WcActBC.c: In function WcRegisterWcActions:
>
>
> WcActCB.c:1461: error: expected declaration specifiers before XtAppContext.
>
> WcActCB.c:1463: error: expected = , , , ;, asm or __attribute__ befor
> WcActions
>
> WcActCB.c:1463 error: WcActions undeclared (first use in this function).
>
> WcActCB.c:1463 error: expected expression before ] token.
>
> WcActCB.c:1536: error: expected = , , , ;, asm or __attribute__ before
> already.
>
> WcActCB.c:1536: error: already undeclared (first use in this function).
>
> make[2]: *** [WcActB.o] Error 1.
>
> make[2]: Leaving dir '/usr/local/amber9/src/leap/src/Wc'
>
> make [1]: *** [install] Error 2
>
> make[1]: Leaving dir '/usr/local/amber9/src/leap'
>
> make: *** [serial] Error 2
> -
>
> If relevant, I have seen during the process calling "gcc" and "g++" (for
> openmpi I have used intel for both fortran, C and C++) (and all intels are
> activated at booth from my .bashrc).
>
> ______________________
> TEST
>
>
> cd $AMBEROME/test
>
> make test.serial
>
> All PASSED except leap:
>
> cd leap: ./Run.tleap
>
> Error: ./tleap -> ../../exe/teLeap does not exit
>
> make: *** [test.leap] Error 1
> _________________
>
> INFO ON X SYSTEM
>
> francesco_at_deb64:~$ lspci |egrep -i '(video|vga|display)'
> 81:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600]
> (rev
> a 2)
> francesco_at_deb64:~$
>
>
> francesco_at_deb64:~$ awk '/Section
> "(Module|Device|ServerFlags|extensions)"/,/EndSection/' /etc/X11/xorg.conf
> Section "Module"
> Load "bitmap"
> Load "dbe"
> Load "ddc"
> Load "dri"
> Load "extmod"
> Load "freetype"
> Load "glx"
> Load "int10"
> Load "record"
> Load "v4l"
> Load "vbe"
> EndSection
> Section "Device"
> Identifier "nVidia Corporation NV43 [GeForce 6600] (rev a2)"
> Driver "nv"
> # BusID "PCI:129:0:0"
>
> EndSection
> francesco_at_deb64:~$
>
>
> The following was run from console on gnome, that is when both X and gnome
> had
> been started
>
>
>
> francesco_at_deb64:~$ egrep '^\((EE|WW)\)' /var/log/Xorg.0.log (WW) The
> directory
> "/usr/X11R6/lib/X11/fonts/misc" does not exist.
> (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi" does not exist.
> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi" does not exist.
> (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does
> not
> exist.
> (WW) (1024x768,Generic Monitor) mode clock 94.5MHz exceeds DDC maximum 80MHz
> (WW) (1152x864,Generic Monitor) mode clock 108MHz exceeds DDC maximum 80MHz
> (WW) (1280x960,Generic Monitor) mode clock 108MHz exceeds DDC maximum 80MHz
> (WW) (1280x960,Generic Monitor) mode clock 148.5MHz exceeds DDC maximum 80MHz
> (WW) (1280x1024,Generic Monitor) mode clock 108MHz exceeds DDC maximum 80MHz
> (WW) (1280x1024,Generic Monitor) mode clock 135MHz exceeds DDC maximum 80MHz
> (WW) (1280x1024,Generic Monitor) mode clock 157.5MHz exceeds DDC maximum
> 80MHz
> (WW) (1600x1200,Generic Monitor) mode clock 162MHz exceeds DDC maximum 80MHz
> (WW) (800x600,Generic Monitor) mode clock 81MHz exceeds DDC maximum 80MHz
> (WW) (1600x1200,Generic Monitor) mode clock 175.5MHz exceeds DDC maximum
> 80MHz
> (WW) (800x600,Generic Monitor) mode clock 87.75MHz exceeds DDC maximum 80MHz
> (WW) (1600x1200,Generic Monitor) mode clock 189MHz exceeds DDC maximum 80MHz
> (WW) (800x600,Generic Monitor) mode clock 94.5MHz exceeds DDC maximum 80MHz
> (WW) (1600x1200,Generic Monitor) mode clock 202.5MHz exceeds DDC maximum
> 80MHz
> (WW) (800x600,Generic Monitor) mode clock 101.25MHz exceeds DDC maximum 80MHz
> (WW) (1600x1200,Generic Monitor) mode clock 229.5MHz exceeds DDC maximum
> 80MHz
> (WW) (800x600,Generic Monitor) mode clock 114.75MHz exceeds DDC maximum 80MHz
> (WW) (1792x1344,Generic Monitor) mode clock 204.8MHz exceeds DDC maximum
> 80MHz
> (WW) (896x672,Generic Monitor) mode clock 102.4MHz exceeds DDC maximum 80MHz
> (WW) (1792x1344,Generic Monitor) mode clock 261MHz exceeds DDC maximum 80MHz
> (WW) (896x672,Generic Monitor) mode clock 130.5MHz exceeds DDC maximum 80MHz
> (WW) (1856x1392,Generic Monitor) mode clock 218.3MHz exceeds DDC maximum
> 80MHz
> (WW) (928x696,Generic Monitor) mode clock 109.15MHz exceeds DDC maximum 80MHz
> (WW) (1856x1392,Generic Monitor) mode clock 288MHz exceeds DDC maximum 80MHz
> (WW) (928x696,Generic Monitor) mode clock 144MHz exceeds DDC maximum 80MHz
> (WW) (1920x1440,Generic Monitor) mode clock 234MHz exceeds DDC maximum 80MHz
> (WW) (960x720,Generic Monitor) mode clock 117MHz exceeds DDC maximum 80MHz
> (WW) (1920x1440,Generic Monitor) mode clock 297MHz exceeds DDC maximum 80MHz
> (WW) (960x720,Generic Monitor) mode clock 148.5MHz exceeds DDC maximum 80MHz
> (WW) (1280x768,Generic Monitor) mode clock 80.14MHz exceeds DDC maximum 80MHz
> (WW) (1280x800,Generic Monitor) mode clock 83.46MHz exceeds DDC maximum 80MHz
> (WW) (1152x864,Generic Monitor) mode clock 121.5MHz exceeds DDC maximum 80MHz
> (WW) (1400x1050,Generic Monitor) mode clock 122MHz exceeds DDC maximum 80MHz
> (WW) (1400x1050,Generic Monitor) mode clock 151MHz exceeds DDC maximum 80MHz
> (WW) (1400x1050,Generic Monitor) mode clock 155.8MHz exceeds DDC maximum
> 80MHz
> (WW) (1400x1050,Generic Monitor) mode clock 184MHz exceeds DDC maximum 80MHz
> (WW) (700x525,Generic Monitor) mode clock 92MHz exceeds DDC maximum 80MHz
> (WW) (1440x900,Generic Monitor) mode clock 108.84MHz exceeds DDC maximum
> 80MHz
> (WW) (1600x1024,Generic Monitor) mode clock 106.91MHz exceeds DDC maximum
> 80MHz
> (WW) (1680x1050,Generic Monitor) mode clock 147.14MHz exceeds DDC maximum
> 80MHz
> (WW) (1920x1200,Generic Monitor) mode clock 193.16MHz exceeds DDC maximum
> 80MHz
> (WW) (960x600,Generic Monitor) mode clock 96.58MHz exceeds DDC maximum 80MHz
> (WW) (1920x1200,Generic Monitor) mode clock 230MHz exceeds DDC maximum 80MHz
> (WW) (960x600,Generic Monitor) mode clock 115MHz exceeds DDC maximum 80MHz
> (WW) (1920x1440,Generic Monitor) mode clock 341.35MHz exceeds DDC maximum
> 80MHz
> (WW) (960x720,Generic Monitor) mode clock 170.675MHz exceeds DDC maximum
> 80MHz
> (WW) (2048x1536,Generic Monitor) mode clock 266.95MHz exceeds DDC maximum
> 80MHz
> (WW) (1024x768,Generic Monitor) mode clock 133.475MHz exceeds DDC maximum
> 80MHz
> (WW) (2048x1536,Generic Monitor) mode clock 340.48MHz exceeds DDC maximum
> 80MHz
> (WW) (1024x768,Generic Monitor) mode clock 170.24MHz exceeds DDC maximum
> 80MHz
> (WW) (2048x1536,Generic Monitor) mode clock 388.04MHz exceeds DDC maximum
> 80MHz
> (WW) (1024x768,Generic Monitor) mode clock 194.02MHz exceeds DDC maximum
> 80MHz
> (WW) NV(0): Failed to set up write-combining range (0xd0000000,0x10000000)
> (EE) AIGLX: Screen 0 is not DRI capable
> francesco_at_deb64:~$
> _______________________
> THE END
>
>
>
> --- "David A. Case" <case_at_scripps.edu> wrote:
>
> > On Thu, Jun 28, 2007, Francesco Pietra wrote:
> >
> > > As to why xleap resisted compilation, I remark that the X system - though
> > > perfectly functioning at 2D acceleration - lacks OpenGL,
> >
> > Bud's comments were excellent, but I will also point out that xleap has
> > no need for openGL. I can't remember your original problem anymore, but
> > it must be somewhere else. xleap was designed(!) to use almost nothing
> > except
> > xlib. The problems it didn't aniticpate (having been written in the
> 1980's)
> > were that both 32 and 64 bit X libraries would be available (or not
> > available)
> > on any given machine and that getting everything in sync could sometimes
> > be tricky.
> >
> > ...dac
> >
> > -----------------------------------------------------------------------
> > The AMBER Mail Reflector
> > To post, send mail to amber_at_scripps.edu
> > To unsubscribe, send "unsubscribe amber" to majordomo_at_scripps.edu
> >
>
>
>
>
>
>
>
>
____________________________________________________________________________________
> Moody friends. Drama queens. Your life? Nope! - their life, your story. Play
> Sims Stories at Yahoo! Games.
> http://sims.yahoo.com/
>

      ____________________________________________________________________________________
Fussy? Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7

-----------------------------------------------------------------------
The AMBER Mail Reflector
To post, send mail to amber_at_scripps.edu
To unsubscribe, send "unsubscribe amber" to majordomo_at_scripps.edu