Re: GNAT Mingw32 link error?

A large number of us have used gnat-3.15p for quite a long time. No one
has had any problem whatsoever. Thus, it is high probability that your
machine is more special than the rest of us. May be you should tell us
your problem in details. So, we can help you better.

AV

Gary Dumer wrote:
> I first downloaded 3.15p from an FTP site and installed it. I kept getting
> the same error. I even went so far as to remove ALL entries from the PATH
> and rebooted. Same error. Then I uninstalled that version and tried the one
> that comes with MingW32. I went through the same thing with the PATH and
> still got the same error. It looks less like a PATH problem and more like a
> LIB issue, but I don't have a clue what it could be. I agree that it should
> work without a problem, but it's not. So far, no one here seems to have the
> answer. Is there any other web forum that is dedicated to GNAT? If so, maybe
> someone there might be able to spot the problem
>
> Thanks... Gary.
>
> "Anh Vo" <anhvofrcaus@xxxxxxxxx> wrote in message
> news:1127766595.074507.289830@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> >I have successfullly used GNAT/MinGW for years. I am not going to guess
> > what went wrong. However, I strongly suggest to uninstall 3.4.2 and
> > replace it with MinGW/gcc-3.4.4 from MinGW.org. Of course, make sure it
> > is the first item in your path. Then, recompile and relink the
> > hello.adb. I believe that you will be a happy Ada programmer.
> >
> > AV
> >
> > GED wrote:
> >> I'm getting the following error...
> >>
> >> E:\Temp3\Examples>gnat make hello.adb
> >> gnatbind -x hello.ali
> >> gnatlink hello.ali
> >> E:/MinGW/lib/gcc/mingw32/3.4.2/adalib/libgnat.a(raise.o)(.text+0x8b5):
> >> undefined
> >> reference to `_Unwind_SjLj_RaiseException'
> >> E:/MinGW/lib/gcc/mingw32/3.4.2/adalib/libgnat.a(raise.o)(.text+0x8c5):
> >> undefined
> >> reference to `_Unwind_SjLj_ForcedUnwind'
> >> collect2: ld returned 1 exit status
> >> gnatlink: cannot call E:\MinGW\bin\gcc.exe
> >> gnatmake: *** link failed.
> >>
> >> Please help... Gary.
> >

.