Iftikhar Burhanuddin on Fri, 07 Dec 2007 02:44:18 +0100

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

Re: running examples/extgcd.c on cygwin

I still haven't been able to make the extgcd executables run as desired on

One mistake I rectified was to specify the directory where the Pari bin,
include, lib and share directories are to be created, by running

./Configure --prefix=/exotic/dir/name

during installation (It is *clearly* specified in the INSTALL file and I
overlooked it the first time around.)

But these

"Info: resolving _avma by linking to __imp__avma (auto-import)"

messages seem to persist and I believe they are an indication of the
problem that I'm facing. After searching on the Web, I appended


to the LDFLAGS line of the Makefile but that doesn't get rid of the
message. The executables are built but

./extgcd-sta.exe and ./extgcd-dyn.exe

don't prompt me for x and y like they do on my Mac. This applies to both
the pari-2.3.2 and pari-2.4.1.alpha versions.

Also building libextgcd.dll, produces the following:

usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../i686-pc-cygwin/bin/ld: cannot
collect2: ld returned 1 exit status
make: *** [libextgcd.dll] Error 1

This doesn't bother me. All I want to do is work with Pari on cygwin and
be build and run *.exe's.

Any feedback?


On Thu, 29 Nov 2007, Iftikhar Burhanuddin wrote:

> Hi folks,
> Running the executable for the file examples/extgcd.c doesn't produce
> any output on cygwin/Windows XP and further I'm unable to decipher GDB's
> output.
> What is wrong?
> Regards,
> Ifti
> ====
> LocalAdmin@ThingFive ~/pari-2.3.2/examples
> $ make dyn
> /usr/bin/gcc -c -g -Wall -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer
> -I. -I/usr/local/include  extgcd.c
> /usr/bin/gcc -o extgcd-dyn -O3 -Wall -fno-strict-aliasing -fomit-frame-pointer
>   -Wl,--export-dynamic  extgcd.o -Wl,-rpath,/usr/local/lib -lm -L/usr/local/lib
> -lpari
> Info: resolving _avma by linking to __imp__avma (auto-import)
> Info: resolving _gen_0 by linking to __imp__gen_0 (auto-import)
> Info: resolving _gen_1 by linking to __imp__gen_1 (auto-import)
> Info: resolving _bot by linking to __imp__bot (auto-import)
> Info: resolving _win32ctrlc by linking to __imp__win32ctrlc (auto-import)
> LocalAdmin@ThingFive ~/pari-2.3.2/examples
> $ ./extgcd-dyn.exe
> LocalAdmin@ThingFive ~/pari-2.3.2/examples
> $ gdb extgcd-dyn.exe
> GNU gdb (cygwin-special)
> Copyright (C) 2006 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i686-pc-cygwin"...
> (gdb) break main
> Breakpoint 1 at 0x4012fc: file extgcd.c, line 30.
> (gdb) run
> Starting program: /home/LocalAdmin/pari-2.3.2/examples/extgcd-dyn.exe
> gdb: unknown target exception 0xc0000135 at 0x7c964ed1
> Program received signal ?, Unknown signal.
> Program exited with code 030000000465.
> You can't do that without a process to debug.
> (gdb)