#564: Cabal doesn't use LD options when testing linking ----------------------------+----------------------------------------------- Reporter: igloo | Owner: Type: defect | Status: new Priority: high | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.6.0.1 Severity: normal | Resolution: Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Comment (by duncan): Replying to [comment:5 igloo]:
Why is the Cabal user expected to know that Cabal isn't going to use ld when doing a link test?
They are not.
Why is Cabal not using ld for link tests?
I think the fact that there is a special flag for this case is a red herring; we might have needed to pass another flag, e.g. `--no-
Why should it? Autoconf uses (g)cc for link tests. trampoline`, for some reason. We have no options for extra generic cpp, cc or linker flags. The fact that you can always pass extra options whenever Cabal calls gcc or ld is somewhat orthogonal. The --PROG-option flags are there to save you the bother of writing a wrapper script for PROG, it does not mean that --PROG- option flags are somehow generic "cpp/cc/linker options" flags that will be used whenever we do some linking. They are literally only used when we call that PROG. -- Ticket URL: http://hackage.haskell.org/trac/hackage/ticket/564#comment:6 Hackage http://haskell.org/cabal/ Hackage: Cabal and related projects