> Am 06.01.2016 um 00:50 schrieb fink-users-requ...@lists.sourceforge.net:
> 
> Date: Tue, 05 Jan 2016 23:50:28 +0100
> From: Ralf H?ling <hoel...@mac.com>
> Subject: [Fink-users] Lazarus Broken Package?
> To: fink-users@lists.sourceforge.net
> Cc: karl-michael.schind...@web.de
> Message-ID: <6c67f29c-7cc7-4bd2-8370-5ffcfad1b...@mac.com>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi,
> when trying to install Lazarus-aqua on my MBP with Mac OSX 10.9.5 I get the 
> following error message:
> 
> make -C utils all
> make[2]: Entering directory 
> '/sw/src/fink.build/fpc-cross-common-3.0.0-1/fpc-3.0.0/compiler/utils'
> make[2]: Leaving directory 
> '/sw/src/fink.build/fpc-cross-common-3.0.0-1/fpc-3.0.0/compiler/utils'
> make[1]: Leaving directory 
> '/sw/src/fink.build/fpc-cross-common-3.0.0-1/fpc-3.0.0/compiler'
> make: *** No rule to make target 'mipsep'.  Stop.
> make: Leaving directory 
> '/sw/src/fink.build/fpc-cross-common-3.0.0-1/fpc-3.0.0/compiler'
> ### execution of /tmp/fink.gY696 failed, exit code 2
> ### execution of /tmp/fink.S2bRt failed, exit code 2
> Removing runtime build-lock...
> Removing build-lock package...
> /sw/bin/dpkg-lockwait -r fink-buildlock-fpc-cross-common-3.0.0-1
> (Reading database ... 195241 files and directories currently installed.)
> Removing fink-buildlock-fpc-cross-common-3.0.0-1 ...
> Failed: phase compiling: fpc-cross-common-3.0.0-1 failed
> 
> Before reporting any errors, please run "fink selfupdate" and try again.
> 
> [...]
> Is there anything I can do?
> Best regards
> Ralf

Typo (mispep -> mipsel). My fault. Corrected in current version. Please try 
again.

Best

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to