Sponsored Content
Top Forums UNIX for Dummies Questions & Answers XEmacs compilation errors not understandable Post 302569052 by BlueTower on Saturday 29th of October 2011 07:50:26 AM
Old 10-29-2011
I think the attachment was missing earlier. Now I have attached the jpeg
 

10 More Discussions You Might Find Interesting

1. Programming

xemacs

Hi Folks, Would like to download the xemacs editor for C. I searched the xemacs site but i donno the exact place of download. Can any one pass the URL or way to go thru and download the editor? Thanks in Advance, Nisha (4 Replies)
Discussion started by: Nisha
4 Replies

2. UNIX for Dummies Questions & Answers

Xemacs and emacs

Hi guys What is the difference between Xemacs and emacs. I assumed Xemacs runs only in X11. What about in Linux on KDE? Am I running Xemacs or emacs. Well it says emacs though. What is the advantage of one over other? What can I run on OS X ? SS (5 Replies)
Discussion started by: saurya_s
5 Replies

3. Shell Programming and Scripting

how to capture compilation errors with Makfile

Hello I have big compilation project when I run the top make file I have problem to find the errors that acres in the sub directories because the make file keeps Running the compilation. is there any way to perform summry of the errors when the Top makefile done running ? thanks (2 Replies)
Discussion started by: umen
2 Replies

4. AIX

Compilation of gettext produces relink errors

Hi, I'm in the process of compiling gnu gettext on a rs/6000 43p-260 running AIX 5.1 in 64bit-mode. The compilation itself runs fine as I understand it, however the installation itself fails like so: I'm pretty much clueless about this relink stuff, so if anyone has suggestions, I'll try... (0 Replies)
Discussion started by: töfte
0 Replies

5. Linux

c++ compilation errors

Hello every one, while compiling c++ modules. i am getting the following 2 errors. 1) /root/cc/unix-ce/root/subsys/cb/cdbh/include/cdbh_TransferFileHeader.h:111: error: âulong_tâ does not name a type /root/cc/unix-ce/root/subsys/cb/cdbh/include/cdbh_TransferFileHeader.h:118: error: âulong_tâ... (0 Replies)
Discussion started by: mannam srinivas
0 Replies

6. Programming

xtrlock compilation errors

Hello, Trying to compile xtrlock from source on a RHEL system. It has an Imakefile but not being familiar enough with that system getting errors running imake: #! Imakefile for xtrlock - X Transparent Lock #! #! Copyright (C)1993,1994 Ian Jackson #! #! This is free software; you can... (1 Reply)
Discussion started by: mgb
1 Replies

7. Shell Programming and Scripting

Compilation errors in running configure script

Hi all, I tried to cross compile Ghostscript-8.54 source. I am getting some errors during cross compilation. I have pasted the errors below. CC=arm-unknown-linux-gnu-gcc LD=arm-unknown-linux-gnu-ld ./configure --host=i686-pc-linux-gnu --target=arm-unknown-linux-gnu --without-x && make ... (2 Replies)
Discussion started by: siva4ever
2 Replies

8. UNIX for Dummies Questions & Answers

xemacs bindings help

Hi all , I would like to have a new binding so that if im having the cursur on a word, one shortcut click (say f3) whould find the next occurrence of the word in the text and so one. what is the right bind for it ? I tried but its wrong. thanks ! Zvika (1 Reply)
Discussion started by: zismad
1 Replies

9. Shell Programming and Scripting

Creating subset of compilation errors

I am compiling a fortran program using gfortran and the result looks as below I want to write a bash or awk script that will scan the information and output only problems within a range of line numbers Example: If I specify the file createmodl.f08, start line 1000 and end line 1100, I will... (8 Replies)
Discussion started by: kristinu
8 Replies

10. Shell Programming and Scripting

Shell script code not really understandable for me

I have a script: DAYS=10 print_usage() { echo "\n" echo "Usage: $PROG dir1 " echo " This program will delete all file/directories that are beyond " echo " 'x days' old." echo " -days - This flag allows you to define x... (3 Replies)
Discussion started by: digioleg54
3 Replies
GLGETFRAMEBUFFERATTA(3G)					    OpenGL 3.3						  GLGETFRAMEBUFFERATTA(3G)

NAME
glGetFramebufferAttachmentParameteriv - retrieve information about attachments of a bound framebuffer object C SPECIFICATION
void glGetFramebufferAttachmentParameter(GLenum target, GLenum attachment, GLenum pname, GLint *params); PARAMETERS
target Specifies the target of the query operation. attachment Specifies the attachment within target pname Specifies the parameter of attachment to query. params Specifies the address of a variable receive the value of pname for attachment. DESCRIPTION
glGetFramebufferAttachmentParameter returns information about attachments of a bound framebuffer object. target specifies the framebuffer binding point and must be GL_DRAW_FRAMEBUFFER, GL_READ_FRAMEBUFFER or GL_FRAMEBUFFER. GL_FRAMEBUFFER is equivalent to GL_DRAW_FRAMEBUFFER. If the default framebuffer is bound to target then attachment must be one of GL_FRONT_LEFT, GL_FRONT_RIGHT, GL_BACK_LEFT, or GL_BACK_RIGHT, identifying a color buffer, GL_DEPTH, identifying the depth buffer, or GL_STENCIL, identifying the stencil buffer. If a framebuffer object is bound, then attachment must be one of GL_COLOR_ATTACHMENTi, GL_DEPTH_ATTACHMENT, GL_STENCIL_ATTACHMENT, or GL_DEPTH_STENCIL_ATTACHMENT. i in GL_COLOR_ATTACHMENTi must be in the range zero to the value of GL_MAX_COLOR_ATTACHMENTS - 1. If attachment is GL_DEPTH_STENCIL_ATTACHMENT and different objects are bound to the depth and stencil attachment points of target the query will fail. If the same object is bound to both attachment points, information about that object will be returned. Upon successful return from glGetFramebufferAttachmentParameteriv, if pname is GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE, then params will contain one of GL_NONE, GL_FRAMEBUFFER_DEFAULT, GL_TEXTURE, or GL_RENDERBUFFER, identifying the type of object which contains the attached image. Other values accepted for pname depend on the type of object, as described below. If the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is GL_NONE, no framebuffer is bound to target. In this case querying pname GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME will return zero, and all other queries will generate an error. If the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is not GL_NONE, these queries apply to all other framebuffer types: o If pname is GL_FRAMEBUFFER_ATTACHMENT_RED_SIZE, GL_FRAMEBUFFER_ATTACHMENT_GREEN_SIZE, GL_FRAMEBUFFER_ATTACHMENT_BLUE_SIZE, GL_FRAMEBUFFER_ATTACHMENT_ALPHA_SIZE, GL_FRAMEBUFFER_ATTACHMENT_DEPTH_SIZE, or GL_FRAMEBUFFER_ATTACHMENT_STENCIL_SIZE, then params will contain the number of bits in the corresponding red, green, blue, alpha, depth, or stencil component of the specified attachment. Zero is returned if the requested component is not present in attachment. o If pname is GL_FRAMEBUFFER_ATTACHMENT_COMPONENT_TYPE, params will contain the format of components of the specified attachment, one of GL_FLOAT, GL_INT, GL_UNSIGNED_INT, GL_SIGNED_NORMALIZED, or GL_UNSIGNED_NORMALIZED for floating-point, signed integer, unsigned integer, signed normalized fixed-point, or unsigned normalized fixed-point components respectively. Only color buffers may have integer components. o If pname is GL_FRAMEBUFFER_ATTACHMENT_COLOR_ENCODING, param will contain the encoding of components of the specified attachment, one of GL_LINEAR or GL_SRGB for linear or sRGB-encoded components, respectively. Only color buffer components may be sRGB-encoded; such components are treated as described in sections 4.1.7 and 4.1.8. For the default framebuffer, color encoding is determined by the implementation. For framebuffer objects, components are sRGB-encoded if the internal format of a color attachment is one of the color-renderable SRGB formats. If the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is GL_RENDERBUFFER, then: o If pname is GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME, params will contain the name of the renderbuffer object which contains the attached image. If the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is GL_TEXTURE, then: o If pname is GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME, then params will contain the name of the texture object which contains the attached image. o If pname is GL_FRAMEBUFFER_ATTACHMENT_TEXTURE_LEVEL, then params will contain the mipmap level of the texture object which contains the attached image. o If pname is GL_FRAMEBUFFER_ATTACHMENT_TEXTURE_CUBE_MAP_FACE and the texture object named GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME is a cube map texture, then params will contain the cube map face of the cubemap texture object which contains the attached image. Otherwise params will contain the value zero. o If pname is GL_FRAMEBUFFER_ATTACHMENT_TEXTURE_LAYER and the texture object named GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME is a layer of a three-dimensional texture or a one-or two-dimensional array texture, then params will contain the number of the texture layer which contains the attached image. Otherwise params will contain the value zero. o If pname is GL_FRAMEBUFFER_ATTACHMENT_LAYERED, then params will contain GL_TRUE if an entire level of a three-dimesional texture, cube map texture, or one-or two-dimensional array texture is attached. Otherwise, params will contain GL_FALSE. Any combinations of framebuffer type and pname not described above will generate an error. ERRORS
GL_INVALID_ENUM is generated if target is not one of the accepted tokens. GL_INVALID_ENUM is generated if pname is not valid for the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE. GL_INVALID_OPERATION is generated if attachment is not the accepted values for target. GL_INVALID_OPERATION is generated if attachment is GL_DEPTH_STENCIL_ATTACHMENT and different objects are bound to the depth and stencil attachment points of target. GL_INVALID_OPERATION is generated if the value of GL_FRAMEBUFFER_ATTACHMENT_OBJECT_TYPE is GL_NONE and pname is not GL_FRAMEBUFFER_ATTACHMENT_OBJECT_NAME. SEE ALSO
glGenFramebuffers(), glBindFramebuffer() COPYRIGHT
Copyright (C) 2010 Khronos Group. This material may be distributed subject to the terms and conditions set forth in the Open Publication License, v 1.0, 8 June 1999. http://opencontent.org/openpub/. OpenGL 3.3 03/08/2011 GLGETFRAMEBUFFERATTA(3G)
All times are GMT -4. The time now is 07:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy