Re: compiler warning

[Clemens Lang]

On Mon, Oct 28, 2019 at 08:28:37PM -0700, Al Varnell via macports-users wrote:
> Maybe I’m missing something obvious here, but why isn’t the list configured 
> IAW RFC 2369 instead?

Quoting from the headers of your mail: 

| List-Id: MacPorts general user support and discussion
| 
| List-Unsubscribe: ,
| 
| List-Archive: 
| List-Post: 
| List-Help: 
| List-Subscribe: ,
| 

I believe that fulfils RFC 2369. Nowadays few mail clients have a
reply-to-list feature, though.

-- 
Clemens

Re: Mailing list configuration (was: Re: compiler warning)

[Ryan Schmidt]

On Oct 28, 2019, at 22:28, Al Varnell wrote:

> Maybe I’m missing something obvious here, but why isn’t the list configured 
> IAW RFC 2369 instead?

What specifically are you proposing we change?

Re: compiler warning

[Al Varnell via macports-users]

Maybe I’m missing something obvious here, but why isn’t the list configured IAW 
RFC 2369 instead?

Sent from my iPad

-Al-

> On Oct 28, 2019, at 19:44, Ryan Schmidt  wrote:
> 
> 
> 
>> On Oct 12, 2019, at 21:50, Al Varnell wrote:
>> 
>> I feel certain that could be configured to be the default setting for this 
>> list. It is the only one of over a dozen that I subscribe to where it’s not.
>> 
>> Could that be checked into?
> 
> No. Munging the Reply-To header would contravene the relevant RFC.
> 
> http://marc.merlins.org/netrants/reply-to-still-harmful.html
> 
> 
> And please use our new list addresses at lists.macports.org, rather than the 
> old addresses at the old hostname which were deprecated at the end of 2016. 
> Although mail to the old addresses forwards to the new ones, users using 
> restrictive mail servers like Yahoo! cannot receive those forwards.
> 

Re: compiler warning

[Ryan Schmidt]

On Oct 12, 2019, at 12:14, Andrew Hartung wrote:

> On Oct 12, 2019, at 10:10 AM, Ryan Schmidt wrote:

>> Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should 
>> either upgrade to Xcode 11 to match your clang version (I don't recommend 
>> this due to the many problems we've seen with SDK paths) or you should 
>> downgrade your Clang version (that is to say, your command line tools 
>> version) to match your Xcode version.
> 
> How do I do that?

You can download old versions of Xcode and the command line tools from:

http://developer.apple.com/download/more/

Re: compiler warning

[Ryan Schmidt]

On Oct 12, 2019, at 21:50, Al Varnell wrote:

> I feel certain that could be configured to be the default setting for this 
> list. It is the only one of over a dozen that I subscribe to where it’s not.
> 
> Could that be checked into?

No. Munging the Reply-To header would contravene the relevant RFC.

http://marc.merlins.org/netrants/reply-to-still-harmful.html


And please use our new list addresses at lists.macports.org, rather than the 
old addresses at the old hostname which were deprecated at the end of 2016. 
Although mail to the old addresses forwards to the new ones, users using 
restrictive mail servers like Yahoo! cannot receive those forwards.

Re: compiler warning

[Al Varnell via macports-users]

I feel certain that could be configured to be the default setting for this 
list. It is the only one of over a dozen that I subscribe to where it’s not.

Could that be checked into?

Sent from my iPad

-Al-

> On Oct 12, 2019, at 08:10, Ryan Schmidt  wrote:
> 
> Remember to Reply All so the conversation stays on the list.

Re: compiler warning

[Andrew Hartung via macports-users]

> On Oct 12, 2019, at 4:48 PM, Ryan Schmidt  wrote:
> 
> 
> 
> On Oct 12, 2019, at 12:30, Andrew Hartung wrote:
> 
>> I found the problem. Somehow xcode got updated to 11 automatically two days 
>> ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in 
>> the app store to turn off automatic upgrades. Downgrading now, sorry to 
>> waste everyones time.
> 
> Did downgrading to Xcode 10 make the warning disappear?
> 


The warnings disappeared when I ran xcodebuild -license with xcode 11 still 
installed.



> You shouldn't have seen those warnings for those ports with either Xcode 10 
> or 11, so there may still be something we have to fix.
> 

Re: compiler warning

[Ryan Schmidt]

On Oct 12, 2019, at 12:30, Andrew Hartung wrote:

> I found the problem. Somehow xcode got updated to 11 automatically two days 
> ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in 
> the app store to turn off automatic upgrades. Downgrading now, sorry to waste 
> everyones time.

Did downgrading to Xcode 10 make the warning disappear?

You shouldn't have seen those warnings for those ports with either Xcode 10 or 
11, so there may still be something we have to fix.

Re: compiler warning

[Andrew Hartung via macports-users]

I found the problem. Somehow xcode got updated to 11 automatically two days 
ago. I just upgraded to Mojave a couple of weeks ago and missed a setting in 
the app store to turn off automatic upgrades. Downgrading now, sorry to waste 
everyones time.

> On Oct 12, 2019, at 10:10 AM, Ryan Schmidt  wrote:
> 
> 
> On Oct 11, 2019, at 23:11, Andrew Hartung wrote:
> 
>> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote:
> 
>>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
>>> 
 
 Warning: All compilers are either blacklisted or unavailable; defaulting 
 to first fallback option
>>> 
>>> llvm, clang, and lldb are all part of the same software package.
>>> 
>>> Different ports impose different restrictions on the versions of compilers 
>>> they can be built with. According to the llvm-9.0 portfile, llvm-9.0 and 
>>> clang-9.0 blacklist clang < 602 while lldb-9.0 blacklists clang < 700.
>>> 
>>> The message you received means that, after applying the blacklist, no 
>>> suitable compiler remains. That should not be the case with Xcode 10; you 
>>> should have clang 1000 or newer, which should be fine. What version of 
>>> clang do you actually have? Run
>>> 
>>> /usr/bin/clang --version
>>> 
>>> to find out. If it's less than 1000, try (re)installing the command line 
>>> tools.
>>> 
>>> If that's not it, the compiler blacklist versions portgroup was recently 
>>> changed. Maybe in doing so we introduced a bug.
>>> 
>> 
>> ~ $ /usr/bin/clang --version
>> Apple clang version 11.0.0 (clang-1100.0.33.8)
>> Target: x86_64-apple-darwin18.7.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should either 
> upgrade to Xcode 11 to match your clang version (I don't recommend this due 
> to the many problems we've seen with SDK paths) or you should downgrade your 
> Clang version (that is to say, your command line tools version) to match your 
> Xcode version.
> 
> 
>> I had not changed/updated anything related to xcode since I had last 
>> accepted the xcode license, so maybe there has been a bug introduced.
> 
> Possibly. I am not able to investigate this right now. Maybe somebody else 
> can.

Re: compiler warning

[Andrew Hartung via macports-users]

> On Oct 12, 2019, at 10:10 AM, Ryan Schmidt  wrote:
> 
> On Oct 11, 2019, at 23:11, Andrew Hartung wrote:
> 
>> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote:
> 
>>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
>>> 
 
 Warning: All compilers are either blacklisted or unavailable; defaulting 
 to first fallback option
>>> 
>>> llvm, clang, and lldb are all part of the same software package.
>>> 
>>> Different ports impose different restrictions on the versions of compilers 
>>> they can be built with. According to the llvm-9.0 portfile, llvm-9.0 and 
>>> clang-9.0 blacklist clang < 602 while lldb-9.0 blacklists clang < 700.
>>> 
>>> The message you received means that, after applying the blacklist, no 
>>> suitable compiler remains. That should not be the case with Xcode 10; you 
>>> should have clang 1000 or newer, which should be fine. What version of 
>>> clang do you actually have? Run
>>> 
>>> /usr/bin/clang --version
>>> 
>>> to find out. If it's less than 1000, try (re)installing the command line 
>>> tools.
>>> 
>>> If that's not it, the compiler blacklist versions portgroup was recently 
>>> changed. Maybe in doing so we introduced a bug.
>>> 
>> 
>> ~ $ /usr/bin/clang --version
>> Apple clang version 11.0.0 (clang-1100.0.33.8)
>> Target: x86_64-apple-darwin18.7.0
>> Thread model: posix
>> InstalledDir: 
>> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 
> Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should either 
> upgrade to Xcode 11 to match your clang version (I don't recommend this due 
> to the many problems we've seen with SDK paths) or you should downgrade your 
> Clang version (that is to say, your command line tools version) to match your 
> Xcode version.
> 


How do I do that?



> 
>> I had not changed/updated anything related to xcode since I had last 
>> accepted the xcode license, so maybe there has been a bug introduced.
> 
> Possibly. I am not able to investigate this right now. Maybe somebody else 
> can.

Re: compiler warning

[Ryan Schmidt]

Remember to Reply All so the conversation stays on the list.


On Oct 11, 2019, at 23:11, Andrew Hartung wrote:

> On Oct 11, 2019, at 9:39 PM, Ryan Schmidt wrote:

>> On Oct 10, 2019, at 22:58, Andrew Hartung wrote:
>> 
>>> 
>>> Warning: All compilers are either blacklisted or unavailable; defaulting to 
>>> first fallback option
>> 
>> llvm, clang, and lldb are all part of the same software package.
>> 
>> Different ports impose different restrictions on the versions of compilers 
>> they can be built with. According to the llvm-9.0 portfile, llvm-9.0 and 
>> clang-9.0 blacklist clang < 602 while lldb-9.0 blacklists clang < 700.
>> 
>> The message you received means that, after applying the blacklist, no 
>> suitable compiler remains. That should not be the case with Xcode 10; you 
>> should have clang 1000 or newer, which should be fine. What version of clang 
>> do you actually have? Run
>> 
>> /usr/bin/clang --version
>> 
>> to find out. If it's less than 1000, try (re)installing the command line 
>> tools.
>> 
>> If that's not it, the compiler blacklist versions portgroup was recently 
>> changed. Maybe in doing so we introduced a bug.
>> 
> 
> ~ $ /usr/bin/clang --version
> Apple clang version 11.0.0 (clang-1100.0.33.8)
> Target: x86_64-apple-darwin18.7.0
> Thread model: posix
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin

Clang 11 goes with Xcode 11 but you said you have Xcode 10. You should either 
upgrade to Xcode 11 to match your clang version (I don't recommend this due to 
the many problems we've seen with SDK paths) or you should downgrade your Clang 
version (that is to say, your command line tools version) to match your Xcode 
version.


> I had not changed/updated anything related to xcode since I had last accepted 
> the xcode license, so maybe there has been a bug introduced.

Possibly. I am not able to investigate this right now. Maybe somebody else can.

Re: compiler warning

[Ryan Schmidt]

On Oct 10, 2019, at 22:58, Andrew Hartung wrote:

> What does this mean?
> 
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> 
> 10.14.6 with xcode 10.
> 
> Showed up after the latest port update I ran after here:
> 
> Adding subport libomp-devel
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Adding port lang/llvm-9.0
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Adding subport clang-9.0
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> Adding subport lldb-9.0
> 
> 
> and here:
> 
> Warning: All compilers are either blacklisted or unavailable; defaulting to 
> first fallback option
> --->  Computing dependencies for llvm-9.0.

llvm, clang, and lldb are all part of the same software package.

Different ports impose different restrictions on the versions of compilers they 
can be built with. According to the llvm-9.0 portfile, llvm-9.0 and clang-9.0 
blacklist clang < 602 while lldb-9.0 blacklists clang < 700.

The message you received means that, after applying the blacklist, no suitable 
compiler remains. That should not be the case with Xcode 10; you should have 
clang 1000 or newer, which should be fine. What version of clang do you 
actually have? Run

/usr/bin/clang --version

to find out. If it's less than 1000, try (re)installing the command line tools.

If that's not it, the compiler blacklist versions portgroup was recently 
changed. Maybe in doing so we introduced a bug.