Recent

Author Topic: Lazarus 1.4.2 on OSX Yosemite 10.10.5  (Read 14028 times)

corpusgemini

  • New Member
  • *
  • Posts: 19
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #15 on: September 23, 2015, 10:02:07 pm »
I'm using Yosemite 10.10.5 and XCode 7.

I just tried the -ap option in Lazarus, no difference, still the same error.
The command that is generated, however, works well in a terminal window.

BR
Tony

Jonas Maebe

  • Hero Member
  • *****
  • Posts: 1071
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #16 on: September 23, 2015, 10:10:33 pm »
It's "-ap-", not "-ap" (which is the default). In any case, I doubt it will help.

What may be useful is to start "sudo fs_usage -w" in a terminal window, then compile in lazarus, stop fs_usage via ctrl-c and then search in the terminal window for all occurrences of the file that's missing to see
a) whether it was ever created, and
b) which process deleted it

littlepaul476

  • New member
  • *
  • Posts: 9
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #17 on: September 24, 2015, 12:03:35 am »
with -ap- switch:
Code: [Select]
Hint: (11030) Start of reading config file /etc/fpc.cfg
Hint: (11031) End of reading config file /etc/fpc.cfg
Free Pascal Compiler version 2.6.4 [2014/02/26] for i386
Copyright (c) 1993-2014 by Florian Klaempfl and others
(1002) Target OS: Darwin for i386
(3104) Compiling /Users/Petr/tmp/project1.lpr
(3104) Compiling unit1.pas
unit1.pas(27) Error: (9002) Can't create assembler file: lib/i386-darwin/unit1.s
unit1.pas(27) Error: (9032) Can't write resource file "lib/i386-darwin/unit1.lfm"
unit1.pas(27) Fatal: (10026) There were 2 errors compiling module, stopping
Fatal: (1018) Compilation aborted
Both files unit1.lfm and unit1.s are in lib/i386-darwin/

skalogryz

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2770
    • havefunsoft.com
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #18 on: September 24, 2015, 01:12:49 am »
with -ap- switch:
do you have "-g" and/or "-gl" switches in your command line? If you do, please remove them.

rb

  • Newbie
  • Posts: 3
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #19 on: September 24, 2015, 09:59:31 am »
everytime I want to compile a project, the message window gives this message:
Compile Project, Target: project1: Exit code 1, Errors: 1
Fatal: Compilation aborted


i had exactly the same issue.
Even create a totally new console application, it throws the same error.
On the other side, one of my existing projects still compile without errors.
After searching and testing around whats the difference, i found out in the old project the 2 compiler modes (debug, release) activated, which is not in the new project. 
After activating this 2 modes (project settings/compiler/configuration and targets/ modes/ Button'...'), also the new created application compile well and in both modes.

The compile error appears the first time after update to xcode 7.



Jonas Maebe

  • Hero Member
  • *****
  • Posts: 1071
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #20 on: September 24, 2015, 10:10:57 am »
everytime I want to compile a project, the message window gives this message:
Compile Project, Target: project1: Exit code 1, Errors: 1
Fatal: Compilation aborted


i had exactly the same issue.
Even create a totally new console application, it throws the same error.
On the other side, one of my existing projects still compile without errors.
After searching and testing around whats the difference, i found out in the old project the 2 compiler modes (debug, release) activated, which is not in the new project. 
After activating this 2 modes (project settings/compiler/configuration and targets/ modes/ Button'...'), also the new created application compile well and in both modes.

The compile error appears the first time after update to xcode 7.

The reason for the error is that the default FPC debug format for Darwin/i386 is no longer supported by Xcode 7.

The reason it happens with a new project is that by default, it is compiled in debug mode.

You can solve this by changing the debug format from "Stabs" or "Automatic" to "DWARF 2".

If you build for release mode, no debug information at all is generated, so that will also always work.

I don't know what happens if you activate both the release an debug profiles.

littlepaul476

  • New member
  • *
  • Posts: 9
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #21 on: September 28, 2015, 08:00:53 pm »
I finally installed Xcode 6.4 (side by side with Xcode 7 from MAS), used xcode-select command and now everything works fine. But it costs additional 6GB of space used by Xcode 6.4  :)

corpusgemini

  • New Member
  • *
  • Posts: 19
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #22 on: September 29, 2015, 03:15:11 pm »
I also reverted back to XCode 6.4 , and uninstalled Xcode 7. Maybe I'll use it when I read that it's easily implemented on these pages...
Thanks everyone for their support, appreciate it a lot.

BR,
Tony

tecurb

  • Newbie
  • Posts: 3
Re: Lazarus 1.4.2 on OSX Yosemite 10.10.5
« Reply #23 on: September 30, 2015, 10:03:35 am »
There is a little more to it than that; turning off debug the project is required but I also found that it needed to be turned off in LCL package(s) if they happened to be re-built because (for cocoa at least) debug is enabled by default.

everytime I want to compile a project, the message window gives this message:
Compile Project, Target: project1: Exit code 1, Errors: 1
Fatal: Compilation aborted


i had exactly the same issue.
Even create a totally new console application, it throws the same error.
On the other side, one of my existing projects still compile without errors.
After searching and testing around whats the difference, i found out in the old project the 2 compiler modes (debug, release) activated, which is not in the new project. 
After activating this 2 modes (project settings/compiler/configuration and targets/ modes/ Button'...'), also the new created application compile well and in both modes.

The compile error appears the first time after update to xcode 7.

The reason for the error is that the default FPC debug format for Darwin/i386 is no longer supported by Xcode 7.

The reason it happens with a new project is that by default, it is compiled in debug mode.

You can solve this by changing the debug format from "Stabs" or "Automatic" to "DWARF 2".

If you build for release mode, no debug information at all is generated, so that will also always work.

I don't know what happens if you activate both the release an debug profiles.

 

TinyPortal © 2005-2018