On Apr 11, 2013, at 6:53 PM, Brandon Allbery wrote:
> /Developer should not exist on a machine with Xcode 4.2 or later installed,
> at all.
Unfortunately this is not completely true - there are some SDKs that still
install stuff in /Developer (NVIDIA comes to mind) but it's pretty obvious th
On Thu, Apr 11, 2013 at 7:41 PM, Richard A. O'Keefe wrote:
> The basic problem is that the University has a strict policy
> that academic staff must not have root access on any machine
> that is connected to the University network. I was given an
> administrator account so that I could resume the
The basic problem is that the University has a strict policy
that academic staff must not have root access on any machine
that is connected to the University network. I was given an
administrator account so that I could resume the printer and
install (some) stuff, but /Developer is owned by root,
On Thu, Apr 11, 2013 at 1:19 AM, Richard A. O'Keefe wrote:
> On 11/04/2013, at 12:56 PM, Brandon Allbery wrote:
> > Xcode 4.2 and on do not use /Developer at all. You have an older Xcode
> on your system somehow, which does not understand newer object files; you
> should remove the entire /Develop
On 11/04/2013, at 12:56 PM, Brandon Allbery wrote:
>
> Xcode 4.2 and on do not use /Developer at all. You have an older Xcode on
> your system somehow, which does not understand newer object files; you should
> remove the entire /Developer tree. (Xcode, in order to be distributable via
> the A
On Wed, Apr 10, 2013 at 8:36 PM, Richard A. O'Keefe wrote:
> /Developer/usr/bin/strip: object: /home/cshome/o/ok/.cabal/bin/cabal
> malformed object (unknown load command 15)
>
Xcode 4.2 and on do not use /Developer at all. You have an older Xcode on
your system somehow, which does not understand
Machine:an Intel Core 2 Duo desktop Mac.
OS: Mac OS X 10.7.4
Xcode: 4.6.1 (including command line tools)
Haskell:"Haskell Platform 2012.4.0.0 64bit.pkg"
downloaded today (GHC 7.4.2)
cabal update advised me to install a new cabal-install.
m% cab
Hi Johan,
On Mon, Oct 15, 2012 at 10:18 PM, Johan Tibell wrote:
>
> Fixed since Cabal-1.16.0.1:
>
> * Fixed warnings on the generated Paths module. The warnings are
> generated by the flag '-fwarn-missing-import-lists'.
I tested this issue with Cabal-1.16.0.2 and the issue was fixed.
Thanks,
On Mon, Oct 15, 2012 at 7:16 PM, Johan Tibell wrote:
> Hi all,
>
> I've created bug fix release candidates for Cabal and cabal-install to
> address the bugs found after the release.
Here's the list of fixed bugs:
Fixed since cabal-install-1.16.0:
* Fix installing from custom folder on Linux (#
Hi all,
I've created bug fix release candidates for Cabal and cabal-install to
address the bugs found after the release. If everyone could take some
time to try them out, especially those who had issues with the
previous releases. To install the release candidates run:
cabal install http://jo
10 matches
Mail list logo
