Re: Command Line Tools warning

[Chris Jones]

Try starting Xcode, and make sure in the preferences section for updates 
everything is up to date. Also accept any licenses etc.


On 30/10/15 05:30, Mark Brethen wrote:

I don’t plan on installing El Capitain for a while. Macports website says 6.1 
or later for Yosemite. I have 6.2.

xcode-select -print-path
/Applications/Xcode.app/Contents/Developer

So that’s not it.

I’m stumped.


On Oct 30, 2015, at 12:09 AM, Stephen J. Butler  
wrote:

I think 6.2 is too old for El Capitain (and maybe even for Yosemite). You need 
to upgrade to 7 or 7.1 for El Capitain.

On Thu, Oct 29, 2015 at 11:58 PM, Mark Brethen  wrote:
I upgrading to Yosemite and followed the macports migration document. Now, 
though the 'port install' command succeeds, I get the following warning 
whenever I install a port:

Warning: The Xcode Command Line Tools don't appear to be installed; most ports 
will likely fail to build.

I have Xcode 6.2 and installed the Command Line Tools using 'xcode-select 
—install’

Have overlooked something?


Mark




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users





Mark




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: gcc49 vs gcc48

[Chris Jones]

On 30/10/15 01:18, Brandon Allbery wrote:


On Thu, Oct 29, 2015 at 9:15 PM, David Strubbe > wrote:

The problem that was being mentioned here is that gcc48 doesn't
build. That should not imply that ports already built with gcc48
have any problem. So there is no need to recompile anything. Just
when building new ports use a different version not gcc48.


But there are ports (and I believe one of them was at the start of this
thread) that bake specific compilers into themselves, and therefore have
compiler-specific variants.

That said, the fix for this is to look for any +gcc48 on ports to be
installed and replace it with +gcc49. (Ports that had +gcc48 as default
variant *should* use a different compiler already; if not, file a bug.)


or better yet, use +gcc5, to use the most recent stable gcc release.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Eneko Gotzon Ares]

On 30 Oct 2015, at 21:13, Dave Horsfall  wrote:
> 
> I'm waiting for 10.11.1

Already released some days ago.

--
Eneko Gotzon Ares
enekogot...@gmail.com

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[woods . w]

Version 10.11.1 (15B42) is out BTW.

> On Oct 30, 2015, at 3:13 PM, Dave Horsfall  wrote:
> 
> On Fri, 30 Oct 2015, Mathieu Deaudelin-Lemay wrote:
> 
>> Just for the record, if you are planning on staying on OS X 10.10 
>> (Yosemite), do not upgrade to Xcode 7 as it does not include the SDK for 
>> that OS (only 10.11).
> 
> Now I find out...  I'm waiting for 10.11.1 on principle (never use a 
> version *.0 of anything unless you want to be a beta tester) and Xcode 
> upgraded itself to 7.0,
> 
>> This shouldn't be a problem much of the time, but there are some ports 
>> that will fail to build (e.g. wireshark), as they'll be looking for a 
>> SDK matching your system version and will fail to find it.
> 
> And I occasionally use Wireshark...
> 
> -- 
> Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Ryan Schmidt]

>> On Fri, 30 Oct 2015, Mathieu Deaudelin-Lemay wrote:
>> 
>>> Just for the record, if you are planning on staying on OS X 10.10 
>>> (Yosemite), do not upgrade to Xcode 7 as it does not include the SDK for 
>>> that OS (only 10.11).
>> 
>>> This shouldn't be a problem much of the time, but there are some ports 
>>> that will fail to build (e.g. wireshark), as they'll be looking for a 
>>> SDK matching your system version and will fail to find it.

Wireshark might be an exception, but I tried many ports with Xcode 7 on 
Yosemite and did not see any problems. 
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Brandon Allbery]

On Fri, Oct 30, 2015 at 6:40 PM, Ryan Schmidt 
wrote:

> >>> This shouldn't be a problem much of the time, but there are some ports
> >>> that will fail to build (e.g. wireshark), as they'll be looking for a
> >>> SDK matching your system version and will fail to find it.
>
> Wireshark might be an exception, but I tried many ports with Xcode 7 on
> Yosemite and did not see any problems.


I believe wireshark is a specific exception because it actively hunts for
an SDK instead of using the default.

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Bill Christensen]

Ah, that explains why wireshark updates have failed.  Thanks.  One more
mystery solved!

On Fri, Oct 30, 2015 at 8:59 AM, Mathieu Deaudelin-Lemay <
macpo...@mdeaudelin.net> wrote:

> > or should I go ahead and install 7.1?
>
> Just for the record, if you are planning on staying on OS X 10.10
> (Yosemite), do not upgrade to Xcode 7 as it does not include the SDK for
> that OS (only 10.11).
>
> This shouldn't be a problem much of the time, but there are some ports
> that will fail to build (e.g. wireshark), as they'll be looking for a SDK
> matching your system version and will fail to find it.
>
>
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Dave Horsfall]

On Fri, 30 Oct 2015, Eneko Gotzon Ares wrote:

> > I'm waiting for 10.11.1
> 
> Already released some days ago.


On Fri, 30 Oct 2015, wood...@gmail.com wrote:

> Version 10.11.1 (15B42) is out BTW.

Thanks, all; I'll give it a bash when I have a free day :-)

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Marius Schamschula]

Yes,

This problem can be defeated by adding

—disable-osx-deploy-target

to the configure arguments. Even then, wireshark is broken because of its 
dependency on lua 5.2.

On Oct 30, 2015, at 7:02 PM, Brandon Allbery  wrote:

> On Fri, Oct 30, 2015 at 6:40 PM, Ryan Schmidt  wrote:
> >>> This shouldn't be a problem much of the time, but there are some ports
> >>> that will fail to build (e.g. wireshark), as they'll be looking for a
> >>> SDK matching your system version and will fail to find it.
> 
> Wireshark might be an exception, but I tried many ports with Xcode 7 on 
> Yosemite and did not see any problems.
> 
> I believe wireshark is a specific exception because it actively hunts for an 
> SDK instead of using the default.
> 
> 

Marius
--
Marius Schamschula




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: error upgrading gcc48 port

[Chris Jones]

On 30/10/15 12:26, Fabrizio Salvatore wrote:

I see that there are two ports related to gcc48, one of which is active:

--->  The following versions of gcc48 are currently installed:
--->  gcc48 @4.8.2_2
--->  gcc48 @4.8.3_3 (active)

How do I remove both and make gcc49 the default one?


specify the version when uninstalling

> sudo port uninstall gcc48@4.8.2_2

etc.

( gcc49 is a different port to gcc48 anyway, and can be installed along 
side, as can the gcc5 port which is the recommended default version now 
anyway )




Thanks for your help!

Fab



On 29 October 2015 at 22:41, Eneko Gotzon > wrote:


On Thu, Oct 29, 2015 at 10:43 PM, Fabrizio Salvatore
> wrote:

Is there any instruction anywhere on how to do that?


Port uninstall .


--
Eneko Gotzon Ares
enekogot...@gmail.com 




--
+++
Dr Fabrizio Salvatore|e-mail: p.f.salvat...@sussex.ac.uk

Department of Physics and Astronomy, University of Sussex,
Brighton, Sussex, BN1 9QH, United Kingdom
Tel.:  +44 (0)1273 67 8749; Fax: +44 (0)1273 67 8068
http://epp.phys.susx.ac.uk/epp/FabrizioSalvatore
facebook.com/p.fabrizio.salvatore

+++

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: error upgrading gcc48 port

[Mojca Miklavec]

On Fri, Oct 30, 2015 at 1:49 PM, Chris Jones wrote:
> On 30/10/15 12:26, Fabrizio Salvatore wrote:
>>
>> I see that there are two ports related to gcc48, one of which is active:
>>
>> --->  The following versions of gcc48 are currently installed:
>> --->  gcc48 @4.8.2_2
>> --->  gcc48 @4.8.3_3 (active)
>>
>> How do I remove both and make gcc49 the default one?
>
> specify the version when uninstalling
>
>> sudo port uninstall gcc48@4.8.2_2

Is there also something like
sudo port uninstall gcc48@all
?

Also, what happened to the GSOC project where user would simply select
which port to uninstall in an interactive way?

Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: error upgrading gcc48 port

[Fabrizio Salvatore]

I see that there are two ports related to gcc48, one of which is active:

--->  The following versions of gcc48 are currently installed:
--->  gcc48 @4.8.2_2
--->  gcc48 @4.8.3_3 (active)

How do I remove both and make gcc49 the default one?

Thanks for your help!

Fab



On 29 October 2015 at 22:41, Eneko Gotzon  wrote:

>
> On Thu, Oct 29, 2015 at 10:43 PM, Fabrizio Salvatore <
> p.fabrizio.salvat...@googlemail.com> wrote:
>
>> Is there any instruction anywhere on how to do that?
>
>
> Port uninstall .
>
>
> --
> Eneko Gotzon Ares
> enekogot...@gmail.com
>



-- 
+++
Dr Fabrizio Salvatore|e-mail: p.f.salvat...@sussex.ac.uk
Department of Physics and Astronomy, University of Sussex,
Brighton, Sussex, BN1 9QH, United Kingdom
Tel.:  +44 (0)1273 67 8749; Fax: +44 (0)1273 67 8068
http://epp.phys.susx.ac.uk/epp/FabrizioSalvatore

facebook.com/p.fabrizio.salvatore
+++
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Mark Brethen]

I'm going to reinstall 6 and see if it fixes the warning message.

Sent from my iPhone

> On Oct 30, 2015, at 8:59 AM, Mathieu Deaudelin-Lemay 
>  wrote:
> 
> > or should I go ahead and install 7.1?
> 
> Just for the record, if you are planning on staying on OS X 10.10 (Yosemite), 
> do not upgrade to Xcode 7 as it does not include the SDK for that OS (only 
> 10.11).
> 
> This shouldn't be a problem much of the time, but there are some ports that 
> will fail to build (e.g. wireshark), as they'll be looking for a SDK matching 
> your system version and will fail to find it.
> 
> > Subject: Re: Command Line Tools warning
> > To: mark.bret...@nasa.gov
> > From: jon...@hep.phy.cam.ac.uk
> > Date: Fri, 30 Oct 2015 13:26:40 +
> > CC: macports-users@lists.macosforge.org
> > 
> > 
> > 
> > On 30/10/15 13:21, Brethen, Mark Douglas. (MSFC-ES22)[ESSSA] wrote:
> > > Did that.
> > >
> > > Is it possible to reinstall 6.2,
> > 
> > https://developer.apple.com/downloads/
> > 
> > you probably want to reinstall command line tools and Xcode...
> > 
> > or should I go ahead and install 7.1?
> > >
> > >> On Oct 30, 2015, at 2:31 AM, Chris Jones  
> > >> wrote:
> > >>
> > >>
> > >> Try starting Xcode, and make sure in the preferences section for updates 
> > >> everything is up to date. Also accept any licenses etc.
> > >>
> > >> On 30/10/15 05:30, Mark Brethen wrote:
> > >>> I don’t plan on installing El Capitain for a while. Macports website 
> > >>> says 6.1 or later for Yosemite. I have 6.2.
> > >>>
> > >>> xcode-select -print-path
> > >>> /Applications/Xcode.app/Contents/Developer
> > >>>
> > >>> So that’s not it.
> > >>>
> > >>> I’m stumped.
> > >>>
> >  On Oct 30, 2015, at 12:09 AM, Stephen J. Butler 
> >   wrote:
> > 
> >  I think 6.2 is too old for El Capitain (and maybe even for Yosemite). 
> >  You need to upgrade to 7 or 7.1 for El Capitain.
> > 
> >  On Thu, Oct 29, 2015 at 11:58 PM, Mark Brethen 
> >   wrote:
> >  I upgrading to Yosemite and followed the macports migration document. 
> >  Now, though the 'port install' command succeeds, I get the following 
> >  warning whenever I install a port:
> > 
> >  Warning: The Xcode Command Line Tools don't appear to be installed; 
> >  most ports will likely fail to build.
> > 
> >  I have Xcode 6.2 and installed the Command Line Tools using 
> >  'xcode-select —install’
> > 
> >  Have overlooked something?
> > 
> > 
> >  Mark
> > 
> > 
> > 
> > 
> >  ___
> >  macports-users mailing list
> >  macports-users@lists.macosforge.org
> >  https://lists.macosforge.org/mailman/listinfo/macports-users
> > 
> > >>>
> > >>>
> > >>>
> > >>> Mark
> > >>>
> > >>>
> > >>>
> > >>>
> > >>> ___
> > >>> macports-users mailing list
> > >>> macports-users@lists.macosforge.org
> > >>> https://lists.macosforge.org/mailman/listinfo/macports-users
> > >>>
> > >> ___
> > >> macports-users mailing list
> > >> macports-users@lists.macosforge.org
> > >> https://lists.macosforge.org/mailman/listinfo/macports-users
> > >
> > > Thanks,
> > >
> > > Mark
> > >
> > > Mark D. Brethen
> > > Stress Analyst
> > > DSI - Jacobs
> > > Marshall Space Flight Center
> > > Bldg 4203, Cube 4321
> > > Work: (256) 961-2147
> > > Email: mark.bret...@nasa.gov
> > > Web: http://www.davisdsi.com/
> > >
> > >
> > >
> > >
> > ___
> > macports-users mailing list
> > macports-users@lists.macosforge.org
> > https://lists.macosforge.org/mailman/listinfo/macports-users
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

RE: Command Line Tools warning

[Mathieu Deaudelin-Lemay]

> or should I go ahead and install 7.1?

Just for the record, if you are planning on staying on OS X 10.10 (Yosemite), 
do not upgrade to Xcode 7 as it does not include the SDK for that OS (only 
10.11).
This shouldn't be a problem much of the time, but there are some ports that 
will fail to build (e.g. wireshark), as they'll be looking for a SDK matching 
your system version and will fail to find it.
> Subject: Re: Command Line Tools warning
> To: mark.bret...@nasa.gov
> From: jon...@hep.phy.cam.ac.uk
> Date: Fri, 30 Oct 2015 13:26:40 +
> CC: macports-users@lists.macosforge.org
> 
> 
> 
> On 30/10/15 13:21, Brethen, Mark Douglas. (MSFC-ES22)[ESSSA] wrote:
> > Did that.
> >
> > Is it possible to reinstall 6.2,
> 
> https://developer.apple.com/downloads/
> 
> you probably want to reinstall command line tools and Xcode...
> 
>   or should I go ahead and install 7.1?
> >
> >> On Oct 30, 2015, at 2:31 AM, Chris Jones  wrote:
> >>
> >>
> >> Try starting Xcode, and make sure in the preferences section for updates 
> >> everything is up to date. Also accept any licenses etc.
> >>
> >> On 30/10/15 05:30, Mark Brethen wrote:
> >>> I don’t plan on installing El Capitain for a while. Macports website says 
> >>> 6.1 or later for Yosemite. I have 6.2.
> >>>
> >>> xcode-select -print-path
> >>> /Applications/Xcode.app/Contents/Developer
> >>>
> >>> So that’s not it.
> >>>
> >>> I’m stumped.
> >>>
>  On Oct 30, 2015, at 12:09 AM, Stephen J. Butler 
>   wrote:
> 
>  I think 6.2 is too old for El Capitain (and maybe even for Yosemite). 
>  You need to upgrade to 7 or 7.1 for El Capitain.
> 
>  On Thu, Oct 29, 2015 at 11:58 PM, Mark Brethen  
>  wrote:
>  I upgrading to Yosemite and followed the macports migration document. 
>  Now, though the 'port install' command succeeds, I get the following 
>  warning whenever I install a port:
> 
>  Warning: The Xcode Command Line Tools don't appear to be installed; most 
>  ports will likely fail to build.
> 
>  I have Xcode 6.2 and installed the Command Line Tools using 
>  'xcode-select —install’
> 
>  Have overlooked something?
> 
> 
>  Mark
> 
> 
> 
> 
>  ___
>  macports-users mailing list
>  macports-users@lists.macosforge.org
>  https://lists.macosforge.org/mailman/listinfo/macports-users
> 
> >>>
> >>>
> >>>
> >>> Mark
> >>>
> >>>
> >>>
> >>>
> >>> ___
> >>> macports-users mailing list
> >>> macports-users@lists.macosforge.org
> >>> https://lists.macosforge.org/mailman/listinfo/macports-users
> >>>
> >> ___
> >> macports-users mailing list
> >> macports-users@lists.macosforge.org
> >> https://lists.macosforge.org/mailman/listinfo/macports-users
> >
> > Thanks,
> >
> > Mark
> >
> > Mark D. Brethen
> > Stress Analyst
> > DSI - Jacobs
> > Marshall Space Flight Center
> > Bldg 4203, Cube 4321
> > Work: (256) 961-2147
> > Email: mark.bret...@nasa.gov
> > Web: http://www.davisdsi.com/
> >
> >
> >
> >
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users
  ___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning

[Chris Jones]

On 30/10/15 13:21, Brethen, Mark Douglas. (MSFC-ES22)[ESSSA] wrote:

Did that.

Is it possible to reinstall 6.2,


https://developer.apple.com/downloads/

you probably want to reinstall command line tools and Xcode...

 or should I go ahead and install 7.1?



On Oct 30, 2015, at 2:31 AM, Chris Jones  wrote:


Try starting Xcode, and make sure in the preferences section for updates 
everything is up to date. Also accept any licenses etc.

On 30/10/15 05:30, Mark Brethen wrote:

I don’t plan on installing El Capitain for a while. Macports website says 6.1 
or later for Yosemite. I have 6.2.

xcode-select -print-path
/Applications/Xcode.app/Contents/Developer

So that’s not it.

I’m stumped.


On Oct 30, 2015, at 12:09 AM, Stephen J. Butler  
wrote:

I think 6.2 is too old for El Capitain (and maybe even for Yosemite). You need 
to upgrade to 7 or 7.1 for El Capitain.

On Thu, Oct 29, 2015 at 11:58 PM, Mark Brethen  wrote:
I upgrading to Yosemite and followed the macports migration document. Now, 
though the 'port install' command succeeds, I get the following warning 
whenever I install a port:

Warning: The Xcode Command Line Tools don't appear to be installed; most ports 
will likely fail to build.

I have Xcode 6.2 and installed the Command Line Tools using 'xcode-select 
—install’

Have overlooked something?


Mark




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users





Mark




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


Thanks,

Mark

Mark D. Brethen
Stress Analyst
DSI - Jacobs
Marshall Space Flight Center
Bldg 4203, Cube 4321
Work: (256) 961-2147
Email: mark.bret...@nasa.gov
Web: http://www.davisdsi.com/





___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: Command Line Tools warning -- Fixed!

[Mark Brethen]

After installing Xcode 6.4, in preferences, under the “Locations” tab, it 
showed that the command line tools were installed. However, the warning message 
didn’t go away until I issued a separate 'sudo xcode-select —install’ in the 
terminal.


Mark




___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: error upgrading gcc48 port

[Rainer Müller]

On 2015-10-30 13:59, Mojca Miklavec wrote:
> On Fri, Oct 30, 2015 at 1:49 PM, Chris Jones wrote:
>> On 30/10/15 12:26, Fabrizio Salvatore wrote:
>>>
>>> I see that there are two ports related to gcc48, one of which is active:
>>>
>>> --->  The following versions of gcc48 are currently installed:
>>> --->  gcc48 @4.8.2_2
>>> --->  gcc48 @4.8.3_3 (active)
>>>
>>> How do I remove both and make gcc49 the default one?
>>
>> specify the version when uninstalling
>>
>>> sudo port uninstall gcc48@4.8.2_2
> 
> Is there also something like
> sudo port uninstall gcc48@all
> ?

You can achieve that with the intersection of ports with the name gcc48
and ports that are installed:

  sudo port uninstall gcc48 and installed

> Also, what happened to the GSOC project where user would simply select
> which port to uninstall in an interactive way?

The work was merged to trunk, but is not yet available in any released
version of MacPorts.

Rainer
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

RE: Command Line Tools warning

[Dave Horsfall]

On Fri, 30 Oct 2015, Mathieu Deaudelin-Lemay wrote:

> Just for the record, if you are planning on staying on OS X 10.10 
> (Yosemite), do not upgrade to Xcode 7 as it does not include the SDK for 
> that OS (only 10.11).

Now I find out...  I'm waiting for 10.11.1 on principle (never use a 
version *.0 of anything unless you want to be a beta tester) and Xcode 
upgraded itself to 7.0,

> This shouldn't be a problem much of the time, but there are some ports 
> that will fail to build (e.g. wireshark), as they'll be looking for a 
> SDK matching your system version and will fail to find it.

And I occasionally use Wireshark...

-- 
Dave Horsfall DTM (VK2KFU)  "Those who don't understand security will suffer."
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users