Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2011-12

Error building r33911

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Bart

Hi,

Just updated to r33911 and got a linking error when trying to build the IDE. Compiling went just fine, but when linking lazarus it went wrong:

Compiling resource ../units/i386-linux/lazarus.or
Linking ../lazarus
/home/bart/svnroot/lazarus/components/synedit/units/i386-linux/synedithighlighterxmlbase.o: In function `TSYNCUSTOMXMLHIGHLIGHTER__ENDFOLDLEVEL': /home/bart/svnroot/lazarus/components/synedit/synedithighlighterxmlbase.pas:162: undefined reference to `VMT_LCLPROC_TMETHODLIST'
lazarus.pp(137,1) Error: Error while linking
/home/bart/svnroot/lazarus/components/synedit/units/i386-linux/synedithighlighterxmlbase.o: In function `TSYNCUSTOMXMLHIGHLIGHTER__ENDFOLDLEVEL': /home/bart/svnroot/lazarus/components/synedit/synedithighlighterxmlbase.pas:162: undefined reference to `VMT_LCLPROC_TMETHODLIST'
/home/bart/svnroot/lazarus/ide/lazarus.pp(137,1) Error: Error while linking /home/bart/svnroot/lazarus/ide/lazarus.pp(137,1) Fatal: There were 1 errors compiling module, stopping

I used "Cleanup + build all" profile from within IDE. Using fpc 2.4.4
Linux GTK2

Any thoughts?

Bart

Reply by email

Mattias Gaertner
to Bart
Show quoted text 11 lines
Hi, Just updated to r33911 and got a linking error when trying to build the IDE. Compiling went just fine, but when linking lazarus it went wrong: Compiling resource ../units/i386-linux/lazarus.or Linking ../lazarus /home/bart/svnroot/lazarus/components/synedit/units/i386-linux/synedithighlighterxmlbase.o: In function `TSYNCUSTOMXMLHIGHLIGHTER__ENDFOLDLEVEL': /home/bart/svnroot/lazarus/components/synedit/synedithighlighterxmlbase.pas:162: undefined reference to `VMT_LCLPROC_TMETHODLIST'

This probably means there are still some old ppu files.

Show quoted text 10 lines
lazarus.pp(137,1) Error: Error while linking /home/bart/svnroot/lazarus/components/synedit/units/i386-linux/synedithighlighterxmlbase.o: In function `TSYNCUSTOMXMLHIGHLIGHTER__ENDFOLDLEVEL': /home/bart/svnroot/lazarus/components/synedit/synedithighlighterxmlbase.pas:162: undefined reference to `VMT_LCLPROC_TMETHODLIST' /home/bart/svnroot/lazarus/ide/lazarus.pp(137,1) Error: Error while linking /home/bart/svnroot/lazarus/ide/lazarus.pp(137,1) Fatal: There were 1 errors compiling module, stopping I used "Cleanup + build all" profile from within IDE.

How old is this IDE?
The better clean up of ppu files were implemented some weeks ago.

Mattias

Reply by email

Bart
to Mattias Gaertner
Mattias Gaertner wrote
This probably means there are still some old ppu files. How old is this IDE? The better clean up of ppu files were implemented some weeks ago.

I'm not really sure, several months I think.

I did a make clean all from commandline, and it built Lazarus just fine (at least it linked and I could start it, by then it was bed-time).

I didn't really encouter this kind of linker errors before.

Thanks for the answer.

Bye.

Bart

Reply by email

Marco van de Voort
to Bart
Bart wrote 12 lines
> How old is this IDE? > The better clean up of ppu files were implemented some weeks ago. I'm not really sure, several months I think. I did a make clean all from commandline, and it built Lazarus just fine (at least it linked and I could start it, by then it was bed-time). I didn't really encouter this kind of linker errors before. Thanks for the answer.

A way to avoid many of such cases is cleaning _before_ updating.

If you do [clean build update clean build update ] then if a file is moved in svn, the second clean will try to clean the new location and the old one is left and can cause problems.

Cleaning before updating solves this.

Reply by email

Bart
to Marco van de Voort
Marco van de Voort wrote 7 lines
A way to avoid many of such cases is cleaning _before_ updating. If you do [clean build update clean build update ] then if a file is moved in svn, the second clean will try to clean the new location and the old one is left and can cause problems. Cleaning before updating solves this.

Thanks for the advice.

Bart

Reply by email