Hello,
Good to know that you could find a way to solve your issue.
Then, concerning your issue about classicthesis, I don't think it is anymore
related to Macports, as you now use the TeXLive distribution.
The present version of the package classicthesis (see
http://www.ctan.org/tex-archive
On Jul 26, 2012, at 21:15, Gunther H. Weber wrote:
> Hi,
>
> I am currently trying to upgrade my MacPorts install to Mountain Lion.
> Unfortunately qt4-mac does not seem to build. My plan was to upgrade
> everything else by uninstalling qt4-mac, i.e., typing "sudo port uninstall
> qt4-mac". H
Hi,
I am currently trying to upgrade my MacPorts install to Mountain Lion.
Unfortunately qt4-mac does not seem to build. My plan was to upgrade everything
else by uninstalling qt4-mac, i.e., typing "sudo port uninstall qt4-mac".
However, even after I do this followed by a "sudo port clean --all
On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia
wrote:
> I'd be interested in hearing "me too"s or "works for me"s from others on 10.7
> installing through XCode (as opposed to ML users or those going to
> connect.apple.com) to find out if this is a 1-off issue or something others
On Thu, Jul 26, 2012 at 11:31 AM, Jeremy Huddleston Sequoia
wrote:
> I'd be interested in hearing "me too"s or "works for me"s from others on 10.7
> installing through XCode (as opposed to ML users or those going to
> connect.apple.com) to find out if this is a 1-off issue or something others
On Jul 26, 2012, at 11:31, Jeremy Huddleston Sequoia wrote:
> Can you please file a bug report at http://bugreport.apple.com including:
>
> /var/log/system.log
> /var/log/install.log
> The output of otool -l /usr/bin/clang | grep uuid
> The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsC
On Jul 26, 2012, at 09:41, "Daniel J. Luke" wrote:
> On Jul 26, 2012, at 12:29 PM, Dominik Reichardt wrote:
>> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention
>> fluidsynth but that has a solution inthe tracker) and I'd like to move on :)
>> I think I once saw a men
On Jul 26, 2012, at 12:29 PM, Dominik Reichardt wrote:
> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention
> fluidsynth but that has a solution inthe tracker) and I'd like to move on :)
> I think I once saw a mention on how to proceed but can't find it anymore...
>From
Also,
Have you filed a ticket about w3m?
My guess is that w3m is failing because of boehmgc changes and not because of
Lion->ML changes.
--Jeremy
On Jul 26, 2012, at 09:29, Dominik Reichardt wrote:
> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention
> fluidsynth bu
On Jul 26, 2012, at 09:29, Dominik Reichardt wrote:
> how do I proceed past errors? my upgrade on ML fails on w3m (not to mention
> fluidsynth but that has a solution inthe tracker) and I'd like to move on :)
> I think I once saw a mention on how to proceed but can't find it anymore...
You sho
Hi William,
Can you please file a bug report at http://bugreport.apple.com including:
/var/log/system.log
/var/log/install.log
The output of otool -l /usr/bin/clang | grep uuid
The output of pkgutil --lsbom com.apple.pkg.DeveloperToolsCLI
Please let me know the radar number, so I can take a look
how do I proceed past errors? my upgrade on ML fails on w3m (not to mention
fluidsynth but that has a solution inthe tracker) and I'd like to move on :)
I think I once saw a mention on how to proceed but can't find it anymore...
Take care
Dominik
___
On Jul 26, 2012, at 11:15 a.m., Jeremy Lavergne wrote:
> You might consider installing the Command Line Tools from connect.apple.com.
This works for me, by the way. My /usr/bin/clang is now 4.0, and the
Preferences window indicates that the tools are installed, even after
restarting Xcode.
vq
On Jul 26, 2012, at 11:15 a.m., Jeremy Lavergne wrote:
>> However, my /usr/bin/clang is still the old version, and does not
>> match the one below /Applications/Xcode.app:
>
> Is that clang a symlink?
Nope.
>> Is this expected behaviour? It seems very odd to me. The other thing
>> that's odd is
> However, my /usr/bin/clang is still the old version, and does not
> match the one below /Applications/Xcode.app:
Is that clang a symlink?
> Humber:RailEasy williamg$ /usr/bin/clang --version
> Apple clang version 3.1 (tags/Apple/clang-318.0.61) (based on LLVM 3.1svn)
> Target: x86_64-apple-darw
Hi All,
This is slightly OT, for which apologies, but might have an impact on
a MacPorts installation, and I suspect people here might know how to
fix it.
I'm running up-to-date Mac OS 10.7, and have just installed Xcode 4.4
using the App Store. Next step is to install the Command Line Tools.
Wh
Hi,
I saw the same problem with my MacPort update today after the ML
installation.
The day before I also updated to xcode 4.4.
So I don't know exactly which of the 2 updates was responsible for the
problem but
for me it worked after reinstalling the command line tools in XCode...
Good Luck
--
On Jul 26, 2012, at 08:52, Damon McDougall wrote:
> (espeically
> since 10.6 doesn't have the App Store).
10.6 does of course have the App Store, since 10.6.8.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge
On Jul 26, 2012, at 08:52, Damon McDougall wrote:
> On Wed, Jul 25, 2012 at 03:58:58PM -0500, Ryan Schmidt wrote:
>>
>> On Jul 25, 2012, at 15:22, Jeremy Lavergne wrote:
>>
I'm still running Lion (but preparing for upgrading to Mountain Lion).
Update from Xcode from 4.3 to 4.4 i
On Wed, Jul 25, 2012 at 03:58:58PM -0500, Ryan Schmidt wrote:
>
> On Jul 25, 2012, at 15:22, Jeremy Lavergne wrote:
>
> >> I'm still running Lion (but preparing for upgrading to Mountain Lion).
> >>
> >> Update from Xcode from 4.3 to 4.4 is now available at the App Store.
> >>
> >> Will Xcode 4
On Jul 26, 2012, at 07:41, William H. Magill wrote:
> I am about to upgrade to Mountain Lion and I note that the Migration Document
> does not mention anything specifically about it.
>
> Are there any "differences" or particular "changes/gotchas" unique to
> Mountain Lion that need to be consi
I am about to upgrade to Mountain Lion and I note that the Migration Document
does not mention anything specifically about it.
Are there any "differences" or particular "changes/gotchas" unique to Mountain
Lion that need to be considered?
I've updated Macports itself and all of my installed por
22 matches
Mail list logo
