hatrick on Thu, 8 Feb 2001 14:29:36 +0000 (GMT+00:00)


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: pari & cygwin insurmountable difficulty saga -> gp builds! but...


--Hushpart_boundary_waaxXCGPVtkujCxbFowPjFqyGrbhBoSD
Content-type: text/plain

Hi all; thanks for the note on the extra __imp that should not be there,
 Gerhard;
I've modified Makefile.DLLs to contain the appropriate line, minus the IMP_MACRO;
the 5th echo also needs modification, and i indirect though reent_data to 
get the appropriate type:

Makefile.DLLs now echoes  the following:

echo '#include <stdio.h>'                               > dll_init.c
echo 'extern struct _reent *_impure_ptr;'               >> dll_init.c
echo 'extern __declspec(dllimport) struct _reent reent_data;'           
>> dll_init.c
echo '__attribute__((stdcall))'                         >> dll_init.c
echo 'int dll_entry(int handle, int reason, void *ptr)' >> dll_init.c
echo '{ _impure_ptr=&reent_data; return 1; }'   >> dll_init.c

this allows me to get much further;
now i get to building the dynamic version of gp... and almost make it... 
except there's no rule in the makefile for highlvl-dyn.o, whatnow-dyn.o;
i create appropriate rules for the makefile:

highlvl-dyn.o: .headers libpari_dll.h libpari_globals.h libpari.dll 
	$(CC) -c $(CFLAGS) $(CPPFLAGS) $(DYNFLAGS) -o highlvl-dyn.o ../src/gp/highlvl.c
whatnow-dyn.o: .headers libpari_dll.h libpari_globals.h libpari.dll 
	$(CC) -c $(CFLAGS) $(CPPFLAGS) $(DYNFLAGS) -o whatnow-dyn.o ../src/gp/whatnow.c

this allows gp-dyn.exe to compile!

before i get to euphoric about this i try ./gp-dyn.exe:
i append the result for your amusement:

$ ./gp-dyn.exe
      0 [main] gp-dyn 403 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
  26266 [main] gp-dyn 403 stackdump: Dumping stack trace to gp-dyn.exe.stackdump
Segmentation fault (core dumped)

oh well. looks like the stage Karim got to?
any ideas anybody?
i suspect this has something to do with dll_init.c.




--Hushpart_boundary_waaxXCGPVtkujCxbFowPjFqyGrbhBoSD--


IMPORTANT NOTICE:  If you are not using HushMail, this message could have been read easily by the many people who have access to your open personal email messages.
Get your FREE, totally secure email address at http://www.hushmail.com.