ERROR: While parsing option --apple_platform_type=ios: Not a valid Apple platform type: 'ios' (should be ıos, watchos, tvos, macos or catalyst) #17541
Comments
|
@sgowroji This is indeed a bug in Bazel itself. Note how the error message says that I believe that this can be fixed by using |
|
Yes I truly believe the issue displayed because of case sensitivity. |
Java's `String#to{Lower,Upper}Case()` is locale-dependent, which can
lead to unexpected results in locales with special case mappings in the
ASCII range (e.g. in a Turkish locale, a capital ASCII `I` lowercases to
a non-ASCII variant of `i`).
This is prevented by specifying a local without such case mappings. This
commit uses `Locale.ROOT` as the canonical choice with the same case
mapping behavior as other common locales such as `Locale.ENGLISH` or
`Locale.US`.
Follow-up changes could use Guava's `Ascii.to{Lower,Upper}Case` instead,
but whether this is safe may depend on the context, which makes this
replacement unsuitable to perform across the repo.
Fixes bazelbuild#17541
|
I submitted a fix: #17687 Bazel didn't really work at all with a Turkish locale (e.g. it fails when it encounters a |
This ensures consistent behavior of string operations even if the individual operations do not set a locale. Without this change, Bazel can't operate in e.g. a Turkish locale, where it fails with error messages such as: In rule 'test', size 'medium' is not a valid size. This is because Turkish case mapping rules make it so that a capital ASCII 'I' lowercases to a non-ASCII variant of 'i'. Fixes bazelbuild#17541 Closes bazelbuild#17702. PiperOrigin-RevId: 515339563 Change-Id: I8417d0befd76ba6d140588be5f7e50529af3f6c7
This ensures consistent behavior of string operations even if the individual operations do not set a locale. Without this change, Bazel can't operate in e.g. a Turkish locale, where it fails with error messages such as: In rule 'test', size 'medium' is not a valid size. This is because Turkish case mapping rules make it so that a capital ASCII 'I' lowercases to a non-ASCII variant of 'i'. Fixes #17541 Closes #17702. PiperOrigin-RevId: 515339563 Change-Id: I8417d0befd76ba6d140588be5f7e50529af3f6c7 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
This ensures consistent behavior of string operations even if the individual operations do not set a locale. Without this change, Bazel can't operate in e.g. a Turkish locale, where it fails with error messages such as: In rule 'test', size 'medium' is not a valid size. This is because Turkish case mapping rules make it so that a capital ASCII 'I' lowercases to a non-ASCII variant of 'i'. Fixes bazelbuild#17541 Closes bazelbuild#17702. PiperOrigin-RevId: 515339563 Change-Id: I8417d0befd76ba6d140588be5f7e50529af3f6c7
and others
Description of the bug:
I am following tensorflow installation locally from here. I run configure then run this code:
bazel build --config=ios_fat -c opt --cxxopt=--std=c++17 \ //tensorflow/lite/ios:TensorFlowLiteC_frameworkWhat's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
following the link provided after cloning tensorflow from github.
Which operating system are you running Bazel on?
macos monterey (intel)
What is the output of
bazel info release?5.3.0
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD?Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: