> [Harald Hanche-Olsen (2012-03-04 21:38:46 UTC)]
>
>> [Harald Hanche-Olsen (2012-03-04 21:30:49 UTC)]
>>
>> > How exactly does it determine where to copy the accepted license from?
>>
>> I got it; by examining $HOME, which is not changed by sudo.
>
> So here is a suggestion for making it mor
[Harald Hanche-Olsen (2012-03-04 21:38:46 UTC)]
> [Harald Hanche-Olsen (2012-03-04 21:30:49 UTC)]
>
> > How exactly does it determine where to copy the accepted license from?
>
> I got it; by examining $HOME, which is not changed by sudo.
So here is a suggestion for making it more robust:
If
[Harald Hanche-Olsen (2012-03-04 21:30:49 UTC)]
> How exactly does it determine where to copy the accepted license from?
I got it; by examining $HOME, which is not changed by sudo. My problem
is in the way I run my macports upgrades: I run "sudo es" (es is my
login shell of choice), and I run th
[Rainer Müller (2012-03-04 21:19:54 UTC)]
> On 2012-03-04 21:43 , Harald Hanche-Olsen wrote:
> > So what is the trick required to have the macports user "accept" the
> > XCode license agreement?
>
> MacPorts 2.0.4 just copies the agreement to the license from the home
> directory of the user ex
On 2012-03-04 21:43 , Harald Hanche-Olsen wrote:
> I notice that with the upgrade to macports 2.0.4, there is now a
> proper home for the macports user. But still, I am getting the
> dreaded error message. Worse, I seem to be unable to to get rid of
> it. I have tried "sudo -u macports xcodebuil
[Anthony Michael Agelastos (2012-02-18 16:22:05
UTC)]
On Feb 18, 2012, at 5:45 AM, Aljaž Srebrnič wrote:
> unfortunately this doesn't work, probably because the license
agreement is stored in the home directory of the user (which is
/var/empty for macports user)
For situations such as th
On Fri, Mar 2, 2012 at 10:23 PM, Brandon Allbery wrote:
> On Fri, Mar 2, 2012 at 23:06, Stefan wrote:
>>
>> Clean (from scratch) installation of Lion (10.7.3), followed by XCode
>> 4.3 (4E109), followed by Command Line Tools install via XCode
>> Preferences -> Dow
On Fri, Mar 2, 2012 at 23:06, Stefan wrote:
> Clean (from scratch) installation of Lion (10.7.3), followed by XCode
> 4.3 (4E109), followed by Command Line Tools install via XCode
> Preferences -> Downloads -> Components, followed by
> MacPorts-2.0.4-10.7-Lion.dmg ->
> Any suggestions?
If you haven't opened Xcode yet, you can accept the license for it in the
command line:
sudo xcodebuild -license
Xcode 4.3 requires a license agreement before you can make use it, even the
command line parts.
smime.p7s
Description: S/MIME cryptographic s
> Any suggestions?
Ah, I see it in the list now--my bad!
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
> Any suggestions?
Install Xcode.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Clean (from scratch) installation of Lion (10.7.3), followed by XCode
4.3 (4E109), followed by Command Line Tools install via XCode
Preferences -> Downloads -> Components, followed by
MacPorts-2.0.4-10.7-Lion.dmg -> pkg install, leads to:
$ sudo port upgrade
Warning: xcodebuild exists b
Well, despite the reports, I moved to xcode 4.3, installed the CLI bundle,
changed Xcode-select and the macports.conf developer-dir line and all works.
I just keep a minimal macports collection though.
F
--
Federico Calboli
f.calb...@gmail.com
On Feb 20, 2012, at 21:46, Peter B. West wrote:
> I have installed Xcode 4.3
https://trac.macports.org/wiki/ProblemHotlist#xcode43
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.
I have installed Xcode 4.3, and subsequently removed various pieces of old
Xcode functionality, including a directory from 3.3.1.
Just installed lynx.
Warning: xcodebuild exists but failed to execute
Warning: Xcode does not appear to be installed; most ports will likely fail to
build.
lynx
gt; > I just upgraded to Lion and XCode 4.3 and my macports installation is
> broken.
>
> https://trac.macports.org/wiki/ProblemHotlist#xcode43
>
>
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists
On Feb 19, 2012, at 00:07, Hisham A. wrote:
> I just upgraded to Lion and XCode 4.3 and my macports installation is broken.
https://trac.macports.org/wiki/ProblemHotlist#xcode43
___
macports-users mailing list
macports-users@lists.macosforge.
I just upgraded to Lion and XCode 4.3 and my macports installation is
broken. I followed the steps in the migration wiki to re-install macports
to no avail. I'm unable to install any ports. Here's an example of the
error I'm getting:
":info:configure checking for C compiler
like I need to agree to the license agreement. The only issue,
>>> though, is that I already have. I launch Xcode 4.3 (through Finder and
>>> `open /Applications/Xcode.app`) and it doesn't prompt me with anything. I
>>> even created a "Hello World!" cons
Xcode license agreements, please run
>> xcodebuild standalone from within a Terminal window to review and agree to
>> the Xcode license agreements.
>>
>>
>> This looks like I need to agree to the license agreement. The only issue,
>> though, is that I already have. I laun
l window to review and agree to
> the Xcode license agreements.
>
>
> This looks like I need to agree to the license agreement. The only issue,
> though, is that I already have. I launch Xcode 4.3 (through Finder and `open
> /Applications/Xcode.app`) and it doesn't pro
Though the path looks like a wrong macports.conf entry for developer_dir. With
an empty path for developer_dir the log said that there is no /usr/bin/clang
even though I could clearly see and execute it ;)
That's what lead me to look at the build folder.
Dom
Am 18.02.2012 um 07:32 schrieb Domin
Interestingly that's what the log said in my libpvx problem. And yes, there is
no clang at this location. Anyway on closer inspection, looking the config.err
in the build folder it revealed that not a missing clang was the problem but
that the SDKs weren't found.
IMO this only reveals a problem
On Feb 17, 2012, at 20:49, Arturo Rinaldi wrote:
> @ Ryan : here is my config.logcould you look at it and give your opinion
> ? thx in advance
Well it says:
./configure: line 2555:
/Applications/Xcode.app/Contents/Developer/usr/bin/clang: No such file or
directory
__
Thank you much for this report; this precisely the feedback we've been looking
for.
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.
err
shows:
https://trac.macports.org/ticket/33283
Thanks.
I realize you are first having to deal with all the fallout of xcode 4.3 but is
there anything planned yet? A full migration necessary because of all the other
ports that should need a bump first before bumping others (libtool, perl, etc
This fails and the
>>>> config.err shows:
>>>
>>> https://trac.macports.org/ticket/33283
>>>
>>
>> Thanks.
>>
>> I realize you are first having to deal with all the fallout of xcode 4.3 but
>> is there anything planned yet? A full mig
s.org/ticket/33283
>>
>
> Thanks.
>
> I realize you are first having to deal with all the fallout of xcode 4.3 but
> is there anything planned yet? A full migration necessary because of all the
> other ports that should need a bump first before bumping others (libtool,
>
> On Feb 17, 2012, at 15:13, Dominik Reichardt wrote:
>
>> My "port upgrade outdated" tries to build libvpx. This fails and the
>> config.err shows:
>
> https://trac.macports.org/ticket/33283
>
Thanks.
I realize you are first having to deal with al
On Feb 17, 2012, at 15:13, Dominik Reichardt wrote:
> My "port upgrade outdated" tries to build libvpx. This fails and the
> config.err shows:
https://trac.macports.org/ticket/33283
___
macports-users mailing list
macports-users@lists.macosforge.org
>
>
> Am 17.02.2012 um 17:55 schrieb Arturo Rinaldi :
>
>> Nella citazione in data Fri Feb 17 17:40:46 2012, Dominik Reichardt ha
>> scritto:
>>> I think the macports.conf instructions are partly wrong.
>>> Changing
>>>
>>> #developer_dir /Developer
>>> To
>>>
>>> developer_dir
>>> doe
On Feb 17, 2012, at 11:55 AM, Stefan Scheidt wrote:
> $ sudo port upgrade outdated
> ...
> ---> Computing dependencies for subversion-perlbindings
> ---> Fetching archive for subversion-perlbindings
> ---> Attempting to fetch
> subversion-perlbindings-1.7.3_0.darwin_11.x86_64.tgz from
> http:/
Am 17.02.2012 um 17:55 schrieb Arturo Rinaldi :
> Nella citazione in data Fri Feb 17 17:40:46 2012, Dominik Reichardt ha
> scritto:
>> I think the macports.conf instructions are partly wrong.
>> Changing
>>
>> #developer_dir /Developer
>> To
>>
>> developer_dir
>> doesn't make much sens
Nella citazione in data Fri Feb 17 17:40:46 2012, Dominik Reichardt ha
scritto:
I think the macports.conf instructions are partly wrong.
Changing
#developer_dir /Developer
To
developer_dir
doesn't make much sense. I'd say
developer_dir /applications/xcode.app/contents/Developer
mak
ns:`sudo xcode-select -switch /Applications/Xcode.app`and changed macports.conf developer_dir setting.RegardsStefanAm 17. Feb 2012 um 15:28 schrieb Eric Cronin :On 17.02.2012 09:04, Stefan Scheidt wrote: > Hi, > > I'm using OS X 10.7.3 and MacPorts 2.0.3. > I just upgraded to Xcod
I think the macports.conf instructions are partly wrong.
Changing
#developer_dir /Developer
To
developer_dir
doesn't make much sense. I'd say
developer_dir /applications/xcode.app/contents/Developer
makes more sense but I could ve wrong
Dom
Am 17.02.2012 um 16:54 schrieb Arturo Rinaldi :
>
On Feb 16, 2012, at 19:12, Arturo Rinaldi wrote:
> i just updated to Xcode 4.3 and i have some issue with macports.
The log you attached says:
:info:configure configure: error: C compiler cannot create executables
:info:configure See `config.log' for more details.
This is one of
> also made before this
>
> sudo port clean all
Did you uninstall all packages before you tried building again?
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Nella citazione in data Fri Feb 17 15:46:49 2012, Jeremy Lavergne ha
scritto:
do you mean "command line tools" in the preferences pane as unix tools ? i
already did that !
I think he is referring to developer_dir in your macports.conf
i just followed the instructions at
https://trac.mac
> do you mean "command line tools" in the preferences pane as unix tools ? i
> already did that !
I think he is referring to developer_dir in your macports.conf
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge
and is
somewhere else in developer right now.
Probably needs to install unix dev tools from xcode preferences as well.
Dom
Am 17.02.2012 um 02:12 schrieb Arturo Rinaldi <mailto:arty.n...@gmail.com>>:
i just updated to Xcode 4.3 and i have some issue with macports. I
performed the
On 17.02.2012 09:04, Stefan Scheidt wrote:
Hi,
I'm using OS X 10.7.3 and MacPorts 2.0.3.
I just upgraded to Xcode 4.3 and now have problems doing a "sudo port
upgrade outdated".
Here's what I did:
(1) Install Xcode 4.3 via App Store
(2) Move /Developer to trash by Xcode 4
Hi,I'm using OS X 10.7.3 and MacPorts 2.0.3.I just upgraded to Xcode 4.3 and now have problems doing a "sudo port upgrade outdated".Here's what I did:(1) Install Xcode 4.3 via App Store(2) Move /Developer to trash by Xcode 4.3 after first start of Xcode 4.3(3) Download Command
Hi,
As many of you may have noticed, XCode 4.3 was released today. The
installation of XCode 4.3 is a bit different than previous releases and will
require some updates to the macports installation wiki.
1) For starters, XCode 4.3 is self contained in an app bundle. You no longer
need to go
Hi all,
Apparently apple released standalone unix dev tools + SDKs
Also xcode 4.3 gets rid of /developer and has everything inside of the app
(also slightly different sdks locations). Also got rid of the extra install
step when downloaded from the app store. Otoh you now need to start
tools from xcode preferences as well.
Dom
Am 17.02.2012 um 02:12 schrieb Arturo Rinaldi :
> i just updated to Xcode 4.3 and i have some issue with macports. I performed
> the following steps :
>
> + removal of Xcode 4.2.1 with the command
>
> sudo /Xcode4/Library/uninstall-d
46 matches
Mail list logo
