Sponsored Content
Operating Systems Solaris Porting C++ 32-bit code on 64-bit Solaris Post 302273511 by pludi on Monday 5th of January 2009 02:14:51 AM
Old 01-05-2009
That's probably because you're passing len1 by-value instead of by-reference. I'm guessing you rather want fun(l), instead of fun(len1).
 

7 More Discussions You Might Find Interesting

1. Programming

copying or concatinating string from 1st bit, leaving 0th bit

Hello, If i have 2 strings str1 and str2, i would like to copy/concatenate str2 to str1, from 1st bit leaving the 0th bit. How do i do it? (2 Replies)
Discussion started by: jazz
2 Replies

2. AIX

porting an application on 64-bit AIX version 5

Hi all, I am facing problem in porting to 64 bit AIX especially with compiling options to compile and run under 64 bit kernel.Can any one put some light on the issue thanks in advance vishal (14 Replies)
Discussion started by: vishalzone2002
14 Replies

3. Solaris

Solaris 64-bit to 32-bit

I had previous implemented the following in my menu.lst to be able to get to 32-bit operations. # title Solaris 10 32-bit root (hd0,0,a) kernel /platform/i86pc/multiboot kernel/unix module /platform/i86pc/boot_archive </code> Now, it is not working as I get the following error : ... (0 Replies)
Discussion started by: praveenr
0 Replies

4. Red Hat

No Error for 64-bit porting

I am just trying to get the warning while compiling for 64-bit on Linux >> uname -a Linux mms4.es.cpth.ie 2.6.9-22.ELsmp #1 SMP Mon Sep 19 18:00:54 EDT 2005 x86_64 x86_64 x86_64 GNU/Linux =================================== Written test.c file which conatin : #include<stdio.h>... (1 Reply)
Discussion started by: amit_27
1 Replies

5. SuSE

64 bit Porting Problem !!!

Dear All, I am trying to build my code (currently functioning on 32bit) on 64 bit SUSE machine. I am getting following error: warning: initializer element is not computable at load time dau.gss.c:275: error: initializer element is not constant dau.gss.c:275: error: (near initialization for... (10 Replies)
Discussion started by: skaushal.schip
10 Replies

6. Solaris

Solaris os 32 bit or 64 bit

:confused: how to find out wether my os is 32 bit or 64 bit. I am using Solaris 5.6. also i want to know the difference between 32 bit and 64bit os. any help will be much appreciated as i am in urgent need of this information (6 Replies)
Discussion started by: asalman.qazi
6 Replies

7. Shell Programming and Scripting

How to handle 64 bit arithmetic operation at 32 bit compiled perl interpreter?H

Hi, Here is the issue. From the program snippet I have Base: 0x1800000000, Size: 0x3FFE7FFFFFFFF which are of 40 and 56 bits. SO I used use bignum to do the math but summing them up I always failed having correct result. perl interpreter info, perl, v5.8.8 built for... (0 Replies)
Discussion started by: rrd1986
0 Replies
funimageput(3)							SAORD Documentation						    funimageput(3)

NAME
FunImagePut - put an image to a Funtools file SYNOPSIS
#include <funtools.h> int FunImagePut(Fun fun, void *buf, int dim1, int dim2, int bitpix, char *plist) DESCRIPTION
The FunImagePut() routine outputs an image array to a FITS file. The image is written either as a primary header/data unit or as an image extension, depending on whether other data have already been written to the file. That is, if the current file position is at the begin- ning of the file, a primary HDU is written. Otherwise, an image extension is written. The first argument is the Funtools handle returned by FunOpen(). The second buf argument is a pointer to a data buffer to write. The dim1and dim2 arguments that follow specify the dimensions of the image, where dim1 corresponds to naxis1 and dim2 corresponds to naxis2. The bitpix argument specifies the data type of the image and can have the following FITS-standard values: o 8 unsigned char o 16 short o 32 int o -32 float o -64 double When FunTableRowPut() is first called for a given image, Funtools checks to see if the primary header has already been written (by having previously written an image or a binary table.) If not, this image is written to the primary HDU. Otherwise, it is written to an image extension. Thus, a simple program to generate a FITS image might look like this: int i; int dim1=512, dim2=512; double *dbuf; Fun fun; dbuf = malloc(dim1*dim2*sizeof(double)); /* open the output FITS image, preparing to copy input params */ if( !(fun = FunOpen(argv[1], "w", NULL)) ) gerror(stderr, "could not FunOpen output file: %s ", argv[1]); for(i=0; i<(dim1*dim2); i++){ ... fill dbuf ... } /* put the image (header will be generated automatically */ if( !FunImagePut(fun, buf, dim1, dim2, -64, NULL) ) gerror(stderr, "could not FunImagePut: %s ", argv[1]); FunClose(fun); free(dbuf); In addition, if a Funtools reference handle was specified when this table was opened, the parameters from this Funtools reference handle are merged into the new image header. Furthermore, if a reference image was specified during FunOpen(), the values of dim1, dim2, and bit- pix in the calling sequence can all be set to 0. In this case, default values are taken from the reference image section. This is useful if you are reading an image section in its native data format, processing it, and then writing that section to a new FITS file. See the imblank example code. The data are assumed to be in the native machine format and will automatically be swapped to FITS big-endian format if necessary. This behavior can be over-ridden with the convert=[true|false] keyword in the plist param list string. When you are finished writing the image, you should call FunFlush() to write out the FITS image padding. However, this is not necessary if you subsequently call FunClose() without doing any other I/O to the FITS file. SEE ALSO
See funtools(7) for a list of Funtools help pages version 1.4.2 January 2, 2008 funimageput(3)
All times are GMT -4. The time now is 10:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy