Recent

Author Topic: Fatal: Can't find unit interfaces used by project1  (Read 46242 times)

anderson5420

  • New Member
  • *
  • Posts: 16
Re: Fatal: Can't find unit interfaces used by project1
« Reply #15 on: February 13, 2011, 03:50:06 pm »
Well, there certainly is something strange or inconsistent going on here.

I had done a fresh install of Lazarus from the disk images in the correct order (fpc, fpc-src and lazarus):

lazarus-0.9.28.2-i386-macosx.dmg   
fpcsrc-2.2.4-intel-macosx.dmg   
fpc-2.2.4.intel-macosx.dmg

And I like others received the "Can't find unit Interface used by Project1" error right out of the box.  Hence my posts.

I just checked (re-checked actually) what options the default installation set, and it did set the default options as follows, and it did compile a blank form from Project1 without errors:

Environment | Options
   Lazarus directory: /Developer/Lazarus
   Compiler path: /usr/local/bin/ppc386
   FPC Source: /usr/local/share/fpcsrc

Project | Options
   All paths blank
   LCL Widget Type: default (Carbon beta)

Project | Inspector
   Required Packages
      LCL

But I and dozens other are not hallucinating when we say we have done the very same install before and tried to compile Project1 to a blank form and received the "Can't find unit Interfaces used by Project1" error.

I guess this may just fade into the sunset until somebody else brings it up again...
 


Phil

  • Hero Member
  • *****
  • Posts: 2750
Re: Fatal: Can't find unit interfaces used by project1
« Reply #16 on: February 15, 2011, 04:42:22 pm »
Any reason why you're not using Laz 0.9.29 and FPC 2.4.2?

I don't think you'll get much help for a version that few are using anymore.

Thanks.

-Phil

theo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1891
Re: Fatal: Can't find unit interfaces used by project1
« Reply #17 on: February 15, 2011, 05:44:25 pm »
Any reason why you're not using Laz 0.9.29 and FPC 2.4.2?
I don't think you'll get much help for a version that few are using anymore.

Phil, 0.9.28.2 is still the latest stable release.
http://sourceforge.net/projects/lazarus/files/

Phil

  • Hero Member
  • *****
  • Posts: 2750
Re: Fatal: Can't find unit interfaces used by project1
« Reply #18 on: February 15, 2011, 06:13:16 pm »
Yeah. Can you solve this?

Thanks.

-Phil

theo

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1891
Re: Fatal: Can't find unit interfaces used by project1
« Reply #19 on: February 15, 2011, 06:32:10 pm »
Yeah. Can you solve this?

Me? I can't afford a Mac. ;-)

But he could try a snapshot: http://www.hu.freepascal.org/lazarus/
« Last Edit: February 15, 2011, 06:35:03 pm by theo »

Phil

  • Hero Member
  • *****
  • Posts: 2750
Re: Fatal: Can't find unit interfaces used by project1
« Reply #20 on: February 15, 2011, 06:43:44 pm »
Already recommended that - hence my question.

Thanks.

-Phil

WalterK

  • New Member
  • *
  • Posts: 48
Re: Fatal: Can't find unit interfaces used by project1
« Reply #21 on: March 17, 2011, 11:08:08 pm »
Hi,

I was having this problem until I caught up, read the FAQ issue on this, and DOWNGRADED TO OLD SOFTWARE!!  Please, can someone roll a new release??

The problem I am now having with linking is this:

Hint: Start of reading config file /etc/fpc.cfg
Hint: End of reading config file /etc/fpc.cfg
Free Pascal Compiler version 2.2.4 [2009/04/05] for powerpc
Copyright (c) 1993-2008 by Florian Klaempfl
Target OS: Darwin for PowerPC
Compiling /tmp/project1.lpr
Compiling unit1.pas
Assembling unit1
Assembling project1
Linking /tmp/project1
/usr/bin/ld: /System/Library/Frameworks/Carbon.framework/Carbon load command 7 unknown cmd field
/usr/bin/ld: /System/Library/Frameworks/OpenGL.framework/OpenGL load command 7 unknown cmd field
/usr/bin/ld: /usr/lib//libiconv.dylib load command 7 unknown cmd field
/usr/bin/ld: /usr/lib//libc.dylib unknown flags (type) of section 9 (__TEXT,__dof_plockstat) in load command 0
/usr/bin/ld: /System/Library/Frameworks/Carbon.framework/Carbon load command 7 unknown cmd field
/usr/bin/ld: /System/Library/Frameworks/AGL.framework/AGL load command 7 unknown cmd field
/usr/bin/ld: /System/Library/Frameworks/OpenGL.framework/OpenGL load command 7 unknown cmd field
An error occurred while linking
Error: Error while linking

What am I doing wrong?

TIA.

Maurizio

  • Newbie
  • Posts: 1
Re: Fatal: Can't find unit interfaces used by project1
« Reply #22 on: January 10, 2012, 12:42:13 pm »
    Just for a future reference, I had the very same problems as Pat but was finally able to solve them.

    This is the context. Under Snow Leopard (10.6.8 ), I did a fresh installation of the following DMG files (downloaded from the Lazarus Sourceforge page):
    • fpc-2.4.2.intel-macosx.dmg
    • fpcsrc-2.4.2.intel-macosx.dmg
    • lazarus-0.9.30.2-i386-macosx.dmg
    and installed them in this order. Creating a blank project using Project|New Project… and then choosing "Application", the same error message seen by Pat about the missing "interfaces" unit appears. I checked the settings for Lazarus and the project (which I did
not change) and everything seemed ok:
  • The LCL is listed as a required package in the Project|Project inspector window;
  • Under Project|Project Options… I see these paths in the Compiler Options|Paths page: nothing for Other Unit Files, $(ProjOutDir) for Include Files, nothing for Libraries, lib/$(TargetCPU)-$(TargetOS) for Unit output directory. I also see that the LCL widget type is default (carbon);
  • From the command line I am able to start FPC, and it matches the version of the DMG I downloaded from the Lazarus site (2.4.2 [2010/11/09] for i386).
  • Under Environment|Options… I have /Developer/lazarus/ for Lazarus directory, /usr/local/bin/ppc386 for Compiler path, /usr/local/share/fpcsrc/ for FPC source directory and /tmp for Directory for building test projects.

I was able to solve the problem by recompiling the LCL following the instructions at this page: http://www.lazarussupport.com/lazarus/weblog/can-not-find-unit-interfaces.

[/list]
« Last Edit: January 10, 2012, 03:56:02 pm by Maurizio »

 

TinyPortal © 2005-2018