Hi all, I am trying to install agda through cabal but I get this: $ cabal install alex Resolving dependencies... [1 of 1] Compiling Main ( /tmp/alex-2.3.116333/alex-2.3.1/Setup.lhs, /tmp/alex-2.3.116333/alex-2.3.1/dist/setup/Main.o ) /tmp/alex-2.3.116333/alex-2.3.1/Setup.lhs:6:51: Warning: In the use of `buildVerbose' (imported from Distribution.Simple.Setup): Deprecated: "Use buildVerbosity instead" /tmp/alex-2.3.116333/alex-2.3.1/Setup.lhs:7:51: Warning: In the use of `defaultUserHooks' (imported from Distribution.Simple): Deprecated: "Use simpleUserHooks or autoconfUserHooks, unless you need Cabal-1.2 compatibility in which case you must stick with defaultUserHooks" Linking /tmp/alex-2.3.116333/alex-2.3.1/dist/setup/setup ... Warning: defaultUserHooks in Setup script is deprecated. Configuring alex-2.3.1... Preprocessing executables for alex-2.3.1... Building alex-2.3.1... [ 1 of 16] Compiling Set ( src/Set.hs, dist/build/alex/alex-tmp/Set.o ) [ 2 of 16] Compiling DFS ( src/DFS.hs, dist/build/alex/alex-tmp/DFS.o ) [ 3 of 16] Compiling Sort ( src/Sort.hs, dist/build/alex/alex-tmp/Sort.o ) [ 4 of 16] Compiling CharSet ( src/CharSet.hs, dist/build/alex/alex-tmp/CharSet.o ) [ 5 of 16] Compiling Map ( src/Map.hs, dist/build/alex/alex-tmp/Map.o ) [ 6 of 16] Compiling Paths_alex ( dist/build/autogen/Paths_alex.hs, dist/build/alex/alex-tmp/Paths_alex.o ) [ 7 of 16] Compiling Util ( src/Util.hs, dist/build/alex/alex-tmp/Util.o ) [ 8 of 16] Compiling AbsSyn ( src/AbsSyn.hs, dist/build/alex/alex-tmp/AbsSyn.o ) [ 9 of 16] Compiling ParseMonad ( src/ParseMonad.hs, dist/build/alex/alex-tmp/ParseMonad.o ) [10 of 16] Compiling Scan ( dist/build/alex/alex-tmp/Scan.hs, dist/build/alex/alex-tmp/Scan.o ) [11 of 16] Compiling Output ( src/Output.hs, dist/build/alex/alex-tmp/Output.o ) [12 of 16] Compiling Info ( src/Info.hs, dist/build/alex/alex-tmp/Info.o ) [13 of 16] Compiling NFA ( src/NFA.hs, dist/build/alex/alex-tmp/NFA.o ) [14 of 16] Compiling DFA ( src/DFA.hs, dist/build/alex/alex-tmp/DFA.o ) [15 of 16] Compiling Parser ( dist/build/alex/alex-tmp/Parser.hs, dist/build/alex/alex-tmp/Parser.o ) [16 of 16] Compiling Main ( src/Main.hs, dist/build/alex/alex-tmp/Main.o ) Linking dist/build/alex/alex ... Installing executable(s) in /home/pmatos/.cabal/bin pmatos@drserver ~ $ cabal install agda Resolving dependencies... Configuring Agda-2.2.2... cabal: alex version >=2.0.1 && <3 is required but it could not be found. cabal: Error: some packages failed to install: Agda-2.2.2 failed during the configure step. The exception was: exit: ExitFailure 1 As you can see, I had just finished installing alex 2.3.1, so why does cabal still request alex >=2.0.1 && <3? Cheers, Paulo Matos
On Fri, 2009-06-19 at 15:35 -0500, Jake McArthur wrote:
Paulo J. Matos wrote:
As you can see, I had just finished installing alex 2.3.1, so why does cabal still request alex >=2.0.1 && <3?
Probably you don't have alex in your PATH.
- Jake
Shouldn't cabal make sure the library it installs are in PATH? or at least, they are in the PATH of the apps built by cabal itself? Cheers, Paulo Matos
On Fri, Jun 19, 2009 at 11:20 PM, Paulo J. Matos<pocmatos@gmail.com> wrote:
Shouldn't cabal make sure the library it installs are in PATH?
This would require modifying the path (since there may be no writable location on the existing path). But the PATH is set by a combination of several programs written in Turing-complete languages (shell script), and those programs themselves are in unknown locations (depending on the shell in use).
or at least, they are in the PATH of the apps built by cabal itself?
This is a possibility. But surely you're one day going to want to run your cabal-installed programs yourself (there are some pretty handy ones), so the easiest thing is to extend your path. It might be a good idea for cabal-install to warn that its bin directory is not in your path when you install an executable. --Max
On Fri, 2009-06-19 at 23:35 +0200, Max Rabkin wrote:
On Fri, Jun 19, 2009 at 11:20 PM, Paulo J. Matos<pocmatos@gmail.com> wrote:
Shouldn't cabal make sure the library it installs are in PATH?
This would require modifying the path (since there may be no writable location on the existing path). But the PATH is set by a combination of several programs written in Turing-complete languages (shell script), and those programs themselves are in unknown locations (depending on the shell in use).
or at least, they are in the PATH of the apps built by cabal itself?
This is a possibility. But surely you're one day going to want to run your cabal-installed programs yourself (there are some pretty handy ones), so the easiest thing is to extend your path.
You're right. Added .cabal/bin to path and everything is ok.
It might be a good idea for cabal-install to warn that its bin directory is not in your path when you install an executable.
Yep, might be an interesting idea for warning. :)
--Max
Am Freitag 19 Juni 2009 23:41:05 schrieb Paulo J. Matos:
It might be a good idea for cabal-install to warn that its bin directory is not in your path when you install an executable.
Yep, might be an interesting idea for warning. :)
This has been discussed in connection to the question where cabal should by default install things. IIRC, the plan is to have cabal display a message on first startup asking the user for the default install location [of binaries] and telling them to make sure it's in the path.
participants (4)
-
Daniel Fischer -
Jake McArthur -
Max Rabkin -
Paulo J. Matos