[livecode] Re: Tidaly error

From: Keenan Mccracken <keenemccracken_at_gmail.com>
Date: Mon, 26 Nov 2018 09:39:03 -0500

Should I just reinstall Tidal from scratch maybe?

On Mon, Nov 26, 2018 at 9:37 AM Keenan Mccracken <keenemccracken_at_gmail.com>
wrote:

> Ah, I see. Tried and got:
>
> clang: warning: argument unused during compilation: '-nopie'
> [-Wunused-command-line-argument]
>
> cabal: Error reading local package.
>
> Couldn't find .cabal file in:
>
> On Mon, Nov 26, 2018 at 9:10 AM Alex McLean <alex_at_slab.org> wrote:
>
>> I think that just means the tidal library isn't installed.
>>
>> What happens if you try
>>
>> cabal update; cabal install
>>
>> from a terminal window?
>> On Mon, 26 Nov 2018 at 13:58, Keenan Mccracken <keenemccracken_at_gmail.com>
>> wrote:
>> >
>> > Hey--sorry for going MIA for a bit. Just installed using the installer
>> .dmg and after trying to run simple command in Tidal d1 $ "bd" I got this.
>> Not sure where to start:
>> >
>> > GHCi, version 8.4.3: http://www.haskell.org/ghc/ :? for help
>> > Prelude> Prelude>
>> > : error:
>> > Could not find module ‘Sound.Tidal.Context’
>> > It is not a module in the current program, or in any known package.
>> > :5:26: error: Variable not in scope: cpsUtils' :: IO (a0, b0, c0)
>> > :7:13: error: Variable not in scope: dirtSetters :: t0 -> IO (a0, b0)
>> :7:25: error: Variable not in scope: getNow :8:13: error: Variable not in
>> scope: dirtSetters :: t0 -> IO (a0, b0)
>> > :8:25: error: Variable not in scope: getNow
>> > :9:13: error: Variable not in scope: dirtSetters :: t0 -> IO (a0, b0)
>> :9:25: error: Variable not in scope: getNow
>> > :10:13: error: Variable not in scope: dirtSetters :: t0 -> IO (a0, b0)
>> :10:25: error: Variable not in scope: getNow
>> > :11:13: error: Variable not in scope: dirtSetters :: t0 -> IO (a0, b0)
>> > :11:25: error: Variable not in scope: getNow :12:13: error: Variable
>> not in scope: dirtSetters :: t0 -> IO (a0, b0)ve>:12:25: error: Variable
>> not in scope: getNow
>> > :13:13: error: Variable not in scope: dirtSetters :: t0 -> IO (a0, b0)
>> > :13:25: error: Variable not in scope: getNow :14:13: error:
>> > Variable not in scope: dirtSetters :: t0 -> IO (a0, b0) :14:25: error:
>> Variable not in scope: getNow
>> > :15:13: error:
>> > Variable not in scope: dirtSetters :: t0 -> IO (a0, b0) :15:25: error:
>> Variable not in scope: getNow
>> > :17:12: error: Variable not in scope: superDirtSetters :: t0 -> IO (a0,
>> b0) :17:29: error: Variable not in scope: getNow
>> > :18:12: error:
>> > Variable not in scope: superDirtSetters :: t0 -> IO (a0, b0) :18:29:
>> error: Variable not in scope: getNow
>> > :19:12: error: Variable not in scope: superDirtSetters :: t0 -> IO (a0,
>> b0) :19:29: error: Variable not in scope: getNow:20:12: error:
>> > Variable not in scope: superDirtSetters :: t0 -> IO (a0, b0) :20:29:
>> error: Variable not in scope: getNow :21:12: error:
>> > Variable not in scope: superDirtSetters :: t0 -> IO (a0, b0) :21:29:
>> error: Variable not in scope: getNow
>> > :22:12: error: Variable not in scope: superDirtSetters :: t0 -> IO (a0,
>> b0) :22:29: error: Variable not in scope: getNow
>> > :23:12: error: Variable not in scope: superDirtSetters :: t0 -> IO (a0,
>> b0)
>> > :23:29: error: Variable not in scope: getNow :24:12: error:
>> > Variable not in scope: superDirtSetters :: t0 -> IO (a0, b0) :24:29:
>> error: Variable not in scope: getNow
>> > :25:12: error: Variable not in scope: superDirtSetters :: t0 -> IO (a0,
>> b0) :25:29: error: Variable not in scope: getNow
>> > :28:13: error:
>> > • Variable not in scope: cps :: t -> t1 • Perhaps you meant ‘cos’
>> (imported from Prelude)
>> > active>:29:21: error: Variable not in scope: silence
>> > :29:31: error: Variable not in scope: d1 :: a0 -> m b0 :29:34: error:
>> Variable not in scope: d2 :: a0 -> m b0 :29:37: error: Variable not in
>> scope: d3 :: a0 -> m b0
>> > :29:40: error: Variable not in scope: d4 :: a0 -> m b0 :29:43: error:
>> Variable not in scope: d5 :: a0 -> m b0 :29:46: error: Variable not in
>> scope: d6 :: a0 -> m b0
>> > :29:49: error: Variable not in scope: d7 :: a0 -> m b0 :29:52: error:
>> Variable not in scope: d8 :: a0 -> m b0
>> > :29:55: error: Variable not in scope: d9 :: a0 -> m b0 :29:58: error:
>> Variable not in scope: c1 :: a0 -> m b0 :29:61: error: Variable not in
>> scope: c2 :: a0 -> m b0 :29:64: error: Variable not in scope: c3 :: a0 -> m
>> b0 :29:67: error: Variable not in scope: c4 :: a0 -> m b0
>> > :29:70: error: Variable not in scope: c5 :: a0 -> m b0 :29:73: error:
>> Variable not in scope: c6 :: a0 -> m b0 :29:76: error: Variable not in
>> scope: c7 :: a0 -> m b0
>> > :29:79: error: Variable not in scope: c8 :: a0 -> m b0 :29:82: error:
>> Variable not in scope: c9 :: a0 -> m b0 :30:17: error: Variable not in
>> scope: hush :: m a0
>> > tidal> tidal> Prelude| Prelude|
>> > eractive>:35:1: error: Variable not in scope: d1 :: [Char] -> t
>> >
>> > On Sat, Nov 3, 2018 at 10:34 AM Shawn Lawson <slawson1618_at_gmail.com>
>> wrote:
>> >>
>> >> Huh. If you don’t have an apple developer account already, then you
>> can make a free one and log into apple’s developer website and download the
>> installer .dmg manually. Looks like they released a new version of the CLTs
>> yesterday.
>> >>
>> >> https://developer.apple.com/download/more/
>> >>
>> >>
>> >> On Nov 3, 2018, at 8:45 AM, Keenan Mccracken <keenemccracken_at_gmail.com>
>> wrote:
>> >>
>> >> just tried to install the xcode command line tools through the
>> terminal and getting a message that says software can't install because
>> it's not currently available from the software update server??
>> >>
>> >> On Sat, Nov 3, 2018 at 8:33 AM Shawn Lawson <lawsos2_at_rpi.edu> wrote:
>> >>>
>> >>> Hi, I’m not on Mojave, but develop on OS X quite a bit.
>> >>>
>> >>> Random thought, do you have Apple’s Command Line Tools installed? You
>> may have to install Xcode first, then find, download and install the
>> Command Line Tools.
>> >>>
>> >>> Although, it looks like maybe Brew or MacPorts (if those are related
>> to your setup) could be at fault.
>> >>>
>> >>>
>> https://apple.stackexchange.com/questions/321858/xcrun-missing-installing-xcode-command-line-tools-not-fixing-issue
>> >>>
>> >>> Best,
>> >>> Shawn
>> >>>
>> >>>
>> >>>
>> >>> On Nov 3, 2018, at 8:24 AM, Keenan Mccracken <
>> keenemccracken_at_gmail.com> wrote:
>> >>>
>> >>> Hi all--running Mojave now and getting this when I boot up Tidal:
>> >>>
>> >>> xcrun: error: invalid active developer path
>> (/Library/Developer/CommandLineTools), missing xcrun at:
>> /Library/Developer/CommandLineTools/usr/bin/xcrun
>> >>> `gcc' failed in phase `gcc'. (Exit code: 1)
>> >>>
>> >>> Any ideas about where xcrun's run to and how I can get it back?
>> >>>
>> >>> Thanks!
>> >>> Keenan
>> >>> _______________________________________________
>> >>> Livecode mailing list -- livecode_at_we.lurk.org
>> >>> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>> >>>
>> >>>
>> >>> _______________________________________________
>> >>> Livecode mailing list -- livecode_at_we.lurk.org
>> >>> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>> >>
>> >> _______________________________________________
>> >> Livecode mailing list -- livecode_at_we.lurk.org
>> >> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>> >>
>> >>
>> >> _______________________________________________
>> >> Livecode mailing list -- livecode_at_we.lurk.org
>> >> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>> >
>> > _______________________________________________
>> > Livecode mailing list -- livecode_at_we.lurk.org
>> > To unsubscribe send an email to livecode-leave_at_we.lurk.org
>>
>>
>>
>> --
>> blog: http://slab.org/
>> _______________________________________________
>> Livecode mailing list -- livecode_at_we.lurk.org
>> To unsubscribe send an email to livecode-leave_at_we.lurk.org
>>
>


_______________________________________________
Livecode mailing list -- livecode_at_we.lurk.org
To unsubscribe send an email to livecode-leave_at_we.lurk.org
Received on Mon Nov 26 2018 - 14:39:24 GMT

This archive was generated by hypermail 2.4.0 : Sun Aug 20 2023 - 16:02:23 BST