Sponsored Content
Top Forums Programming gcc 4.3.2 accept sys call warrning incompatible pointer type Post 302308987 by personificator on Monday 20th of April 2009 11:06:13 PM
Old 04-21-2009
ahh, thanks.
Thats weird that it would be different that the initializer.
 

10 More Discussions You Might Find Interesting

1. Programming

adv reqd on SIGCHLD on accept call

Hi, I have small problem. In my (concurrent)server programm, I am handling accept problem from client like this. sample of server code. /*******************/ end = 0; while (! end ) { sockfd = accept(...) if(sockfd == -1) { if (errno == EINTR) /* this is bcoz... (5 Replies)
Discussion started by: stevenjagan
5 Replies

2. Programming

Accesing structure member:Error:dereferencing pointer to incomplete type

$ gcc -Wall -Werror struct.c struct.c: In function `main': struct.c:18: error: dereferencing pointer to incomplete type $ cat struct.c #include <stdio.h> #include <stdlib.h> #include <string.h> /*Declaration of structure*/ struct human { char *first; char gender; int age; } man,... (3 Replies)
Discussion started by: amit4g
3 Replies

3. Programming

enable 64bit long type for gcc

hey, I believe I once saw a post in this forum, about enable an GCC option to enable long types. I simply cannot find it any more. Can anybody give me a hint? I am on 32bit Ubuntu, and I would like my int be really long. Also I need malloc() take long int argument too. I found it is necessary to... (6 Replies)
Discussion started by: patiobarbecue
6 Replies

4. UNIX for Dummies Questions & Answers

Why do I need to call make if I call gcc ?

Why do I need to call make if I call gcc ? I thought gcc already compiles the sources. thanks (1 Reply)
Discussion started by: aneuryzma
1 Replies

5. Programming

Dereferencing pointer to incomplete type

// Hello all, I am having this error "Dereferencing pointer to incomplete type " on these 2 lines: xpoint = my_point->x; ypoint = my_point->y; I am having no clue y this is happening. Any help would be greately appreciated!!!! #include<stdio.h> #include<string.h>... (2 Replies)
Discussion started by: mind@work
2 Replies

6. Programming

GCC - Incompatible Pointer Types

Hi guys, here is my code written in C and the compiler error message. int i; int (*a); for (i = 1;i <= 9;i++) a = (int *)malloc(sizeof(int) * 10);here is the error: incompatible types when assigning to type ‘int’ from type ‘int *’I want to make a two dimensional array. I... (2 Replies)
Discussion started by: majid.merkava
2 Replies

7. Programming

Compilation Error: dereferencing pointer to incomplete type

I am getting a dereferencing pointer to incomplete type error when i compile the following code on lines highlighted in red. Can anyone help me in identifying what is wrong in the code? #include<stdio.h> #include<stdlib.h> typedef struct{ int info; struct node* link ; } node; void... (3 Replies)
Discussion started by: sreeharshasn
3 Replies

8. Red Hat

Incompatible Level of gcc?

I'm compiling an application someone gave me. It uses XLC on a Power7, running Red Hat (4? 5?). It compiles and links, but I get the following message for every .o and .exe... xlc_r: 1501-274 (W) An incompatible level of gcc has been specified. I've tried googling on this error, and I'll I... (2 Replies)
Discussion started by: Harper21
2 Replies

9. Programming

Warning: pointer type mismatch

Hi all, I'm new programming in C, so I had the next message in my code: Dual.c:88:20: warning: pointer type mismatch in conditional expression : &clientSa.sin6.sin6.sin6_addr, Any help would be great #include <sys/socket.h> #include <netinet/in.h> #include <arpa/inet.h> #include... (1 Reply)
Discussion started by: godna
1 Replies

10. Programming

Incompatible data type fpos_t in C

This is from a program I wrote over in 1998 that I am trying to compile on a linux machine: void write_line (FILE *fp, int rec_no, line_rec *arec) { fpos_t woffset; woffset = (rec_no - 1) * sizeof(line_rec); fsetpos(fp,&woffset); fwrite(arec,sizeof(line_rec),1,fp); }On the line... (2 Replies)
Discussion started by: wbport
2 Replies
drand48(3C)															       drand48(3C)

NAME
drand48(), erand48(), lrand48(), nrand48(), mrand48(), jrand48(), srand48(), seed48(), lcong48() - generate uniformly distributed pseudo- random numbers SYNOPSIS
Obsolescent Interfaces DESCRIPTION
This family of functions generates pseudo-random numbers using the well-known linear congruential algorithm and 48-bit integer arithmetic. In the following description, the formal mathematical notation [low,high) indicates an interval including low but not including high. and return nonnegative double-precision floating-point values uniformly distributed over the interval [0.0,1.0). and return nonnegative long integers uniformly distributed over the interval [0,2^31). and return signed long integers uniformly distributed over the interval [-2^31,2^31). and are initialization entry points, one of which should be invoked before either or is called. (Although it is not recommended practice, constant default initializer values are supplied automatically if or is called without a prior call to an initialization entry point.) and do not require an initialization entry point to be called first. All the routines work by generating a sequence of 48-bit integer values, X[i], according to the linear congruential formula X[n+1] = (a*X[n] + c) modulo m n>=0 The parameter m = 2^48; hence 48-bit integer arithmetic is performed. Unless has been invoked, the default multiplier value a and the default addend value c are given by a = 0x5DEECE66D (base 16) = 0273673163155 (base 8) c = 0xB (base 16) = 013 (base 8) The value returned by any of the functions or is computed by first generating the next 48-bit X[i] in the sequence. Then the appropriate number of bits, according to the type of data item to be returned, are copied from the high-order (leftmost) bits of X[i] and transformed into the returned value. The functions and store the last 48-bit X[i] generated in an internal buffer; that is why they must be initialized prior to being invoked. The functions and require the calling program to provide storage for the successive X[i] values in the array specified as an argument when the functions are invoked. That is why these routines do not have to be initialized; the calling program merely has to place the desired initial value of X[i] into the array and pass it as an argument. By using different arguments, and allow separate modules of a large pro- gram to generate several independent streams of pseudo-random numbers; i.e., the sequence of numbers in each stream do not depend upon how many times the routines have been called to generate numbers for the other streams. The initializer function sets the high-order 32 bits of X[i] to the 32 bits contained in its argument. The low-order 16 bits of X[i] are set to the arbitrary value 0x330E (base 16). The initializer function sets the value of X[i] to the 48-bit value specified in the argument array. In addition, the previous value of X[i] is copied into a 48-bit internal buffer, used only by and a pointer to this buffer is the value returned by This returned pointer, which can be ignored if not needed, is useful if a program is to be restarted from a given point at some future time; use the pointer to get at and store the last X[i] value, and then use this value to reinitialize via when the program is restarted. The initialization function allows the user to specify the initial X[i], the multiplier value a, and the addend value c. Argument array elements param[0-2] specify X[i], param[3-5] specify the multiplier a, and param[6] specifies the 16-bit addend c. After has been called, a subsequent call to either or restores the default multiplier and addend values for a and c, specified above. Obsolescent Interfaces generate uniformly distributed pseudo-random numbers. WARNINGS
and are obsolescent interfaces supported only for compatibility with existing DCE applications. New multithreaded applications should use and SEE ALSO
rand(3C), random(3M), thread_safety(5), random(7). STANDARDS CONFORMANCE
drand48(3C)
All times are GMT -4. The time now is 03:36 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy