RE: [Libunwind-devel] libunwind library/source for Linux 64 bit

[POKHARAKAR Sandeep]

Hello Arun,

 

I am trying to compile this source manually with the gcc compiler, and not using configure for the same. Might be facing issues Because of this.

 

Thanks for your answers and prompt response. Those were really helpful.

 

Sandeep Pokharakar

This e-mail communication and any attachments are privileged and confidential and intended only for the use of the recipients named above. If you are not the intended recipient, please do not review, disclose, disseminate, distribute or copy this e-mail and attachments. If you have received this communication in error, please notify the sender immediately by email or telephone.

 

 

From: Arun Sharma [mailto:address@hidden
Sent: Friday, April 23, 2010 9:02 PM
To: POKHARAKAR Sandeep
Cc: address@hidden
Subject: Re: [Libunwind-devel] libunwind library/source for Linux 64 bit

 

On Fri, Apr 23, 2010 at 1:33 AM, POKHARAKAR Sandeep <address@hidden> wrote:

While compilation I am getting an error trace “_UPT_access_fpreg.c:207:3: error: #error Fix me”. Its seems to be b’caz of “HAVE_DECL_PTRACE_POKEUSER || HAVE_TTRACE” macros missing. And compilation happens at the else part of this “if HAVE_DECL_PTRACE_POKEUSER || HAVE_TTRACE”.

 

I am wondering what is the significance of these macros. Where are those defined. I could not locate their location.

 

When you run ./configure, it looks at header files such as <sys/ptrace.h> and defines these HAVE_* macros. If they're not getting defined, the small test program it uses to check failed. You need to look into your config.log to debug further.

 

Also, where is __USE_GNU defined? I am also getting few compilation issues b’caz of this. As my compiler does not find it.

 

configure.in defines _GNU_SOURCE. <features.h> defines _USE_GNU and possibly other macros based on _GNU_SOURCE.

 

From the nature of the problems you're posting here it smells like either your system header files are not installed correctly or you're using a different compiler. If you're on Linux/x86 with standard include files and gcc, you shouldn't be seeing these problems.

 

 -Arun