comp.lang.idl-pvwave archive: archive » Building sharable object libraries for CALL

Home » Public Forums » archive » Building sharable object libraries for CALL_EXTERNAL

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: Building sharable object libraries for CALL_EXTERNAL [message #14670 is a reply to message #14591]

Sat, 13 March 1999 00:00

Octavi Fors
Messages: 13
Registered: March 1999

Junior Member

<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
"Eric J. Korpela" wrote:
<blockquote TYPE=CITE>In article <36E9649A.7F5C8B65@fajnm1.am.ub.es>,
 Octavi Fors  <octavi@fajnm1.am.ub.es> wrote:
 >
 >Hello,
 >
 >This is my first trial calling a C-routine from IDL with CALL_EXTERNAL,
 >and I have some problems with building routine.so file. It's just
a
 >test, so the routine it's very simple:
 >
 >Second, when I try to create routine.so with:
 >$ ld -o routine.so -z text routine.o (changing '-assert pure-text'
to
 >'-z text' because it's a SunOS Version 5.5.1)
I think you need to specify the -G flag to ld when creating a shared
 object file under Solaris.</blockquote>
I tried your advice with -G flag:
$ld -o routine.so -z text -G routine.o 
Text relocation remains     &am p;nbsp;     &am p;nbsp;     &am p;nbsp;    
referenced 
    against symbol     & ;nbsp;     & ;nbsp;     
offset      in file 
<unknown>                               
0x1c     &n bsp;  routine.o 
<unknown>                               
0x20     &n bsp;  routine.o 
.mul     &n bsp;     &n bsp;     &n bsp;     &n bsp;     &n bsp; 
0xb0     &n bsp;  routine.o 
.mul     &n bsp;     &n bsp;     &n bsp;     &n bsp;     &n bsp; 
0x120     & nbsp; routine.o 
mcount     & ;nbsp;     & ;nbsp;     & ;nbsp;     & ;nbsp;     
0x28     &n bsp;  routine.o 
ld: fatal: relocations remain against allocatable but non-writable sections 
 
 but it also seems to fail. The error message seems to indicate some
problem with
 relocations. What do you think?
 Taking a look at the routine.c code (it's in the first message), I
noticed that the
 **pointer (output) I'm passing back to IDL is malloced in the C-routine,
in line:
output=(float **)malloc(4*n);
  for(i=0;i<n;i++) output[i]=(float*)malloc(4*x*y);
Is there something wrong with this?
 I tried not to malloc output inside routine.c (commenting previous
lines), but last
 error messages still remains.
Any ideas are welcome.
Octavi.
--  
============================================================ ===== 
 
Octavi Fors Aldrich 
 
Astronomy Department
 Physics Faculty
 Avgda. Diagonal 647 
08028 Barcelona 
SPAIN 
 
Telf: 34-934021122 
Fax:  34-934021133 
e-mail: octavi@fajnm1.am.ub.es 
 
============================================================ =====
  </html>

Report message to a moderator

[Message index]

		Building sharable object libraries for CALL_EXTERNAL By: Octavi Fors on Fri, 12 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: rmlongfield on Wed, 17 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: korpela on Mon, 15 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: Octavi Fors on Sat, 13 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: David Foster on Mon, 22 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: Dr. G. Scott Lett on Mon, 22 March 1999 00:00
		Re: Building sharable object libraries for CALL_EXTERNAL By: Octavi Fors on Thu, 18 March 1999 00:00

Previous Topic:	Writing on X without X device (!)
Next Topic:	Re: Colour maps ... (BYTE_SCALE)

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Oct 12 14:56:05 PDT 2025

Total time taken to generate the page: 0.08543 seconds