Re: undefined reference to `main' and strange gnat behaviour
On Wed, 2014-09-24 at 10:39 +0200, Gour wrote:
> On Tue, 23 Sep 2014 19:07:54 +0200
> Ludovic Brenta
> <ludovic@ludovic-brenta.org> wrote:
>
> > I suggest you "rm -f b~* *.o .ali" and call gnatmake again. I presume
> > there was an error wherein some file was modified in an editor but not
> > on disk?
>
> Be assured that I tried that in the very beginning, but it didn't work.
>
> > Anyway, I can only say: "works for me"...
>
> Now, you may laugh about it, but what can you say about this:
> $ emacs -nw hello.adb
> $ gnatmake hello.adb
> gcc-4.9 -c hello.adb
> gnatbind -x hello.ali
> gnatlink hello.ali
here gcc-4.9 is invoked
> $ vim hello.adb
> $ gnatmake hello.adb
> gnatbind -x hello.ali
> gnatlink hello.ali
here it is not...
Check file modification timestamps after each editor has finished : you
are looking for a reason why gnatmake thinks an object file is up to
date (newer than the source) when it is not...
- Brian
Reply to: