Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line
app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
ld: library not found for -lswiftDispatch for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
-- E
···
On Jul 31, 2016, at 4:58 AM, Jens Persson via swift-dev <swift-dev@swift.org> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
I forgot to mention, the issue is only for the pkg without symbols:
swift-DEVELOPMENT-SNAPSHOT-2016-07-29-a-osx.pkg
The other one, ie this:
swift-DEVELOPMENT-SNAPSHOT-2016-07-29-a-osx-symbols.pkg
works but lacks UnsafeRawPointer (which is included in the one without
symbols).
Shouldn't UnsafeRawPointer be in both? And why does the one without symbols
have the linker error?
(btw, the error only shows when importing something, eg Foundation.)
/Jens
···
On Sun, Jul 31, 2016 at 12:58 PM, Jens Persson <jens@bitcycle.com> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line
app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
/Jens
--
bitCycle AB | Smedjegatan 12 | 742 32 Östhammar | Sweden
I get the same as Erica Sadun (for the pkg without symbols that is (the
other one seems to work but doesn't have UnsafeRawPointer as previously
mentioned)).
I've filed https://bugs.swift.org/browse/SR-2232
/Jens
···
On Sun, Jul 31, 2016 at 7:21 PM, Erica Sadun <erica@ericasadun.com> wrote:
For me:
ld: library not found for -lswiftDispatch for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
-- E
On Jul 31, 2016, at 4:58 AM, Jens Persson via swift-dev < > swift-dev@swift.org> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line
app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
> Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
>
> In Xcode 8 beta 3, selecting that toolchain, creating a new command line app, and trying to compile it results in:
> ld: library not found for -lswiftDispatch for architecture x86_64
>
> /Jens
>
>
>
>
_______________________________________________
swift-dev mailing list
swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
I checked the two earlier snapshots (25 and 28 july) and they too have this
bug :(
I fear that the next development snapshot, which I'm waiting for, will be
unusable too, or lack the UnsafeRawPointer API.
···
On Sun, Jul 31, 2016 at 9:45 PM, Jens Persson <jens@bitcycle.com> wrote:
I get the same as Erica Sadun (for the pkg without symbols that is (the
other one seems to work but doesn't have UnsafeRawPointer as previously
mentioned)).
I've filed https://bugs.swift.org/browse/SR-2232
/Jens
On Sun, Jul 31, 2016 at 7:21 PM, Erica Sadun <erica@ericasadun.com> wrote:
For me:
ld: library not found for -lswiftDispatch for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
-- E
On Jul 31, 2016, at 4:58 AM, Jens Persson via swift-dev < >> swift-dev@swift.org> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line
app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
On Aug 1, 2016, at 6:49 AM, Jens Persson via swift-dev <swift-dev@swift.org> wrote:
I checked the two earlier snapshots (25 and 28 july) and they too have this bug :(
I fear that the next development snapshot, which I'm waiting for, will be unusable too, or lack the UnsafeRawPointer API.
On Sun, Jul 31, 2016 at 9:45 PM, Jens Persson <jens@bitcycle.com <mailto:jens@bitcycle.com>> wrote:
I get the same as Erica Sadun (for the pkg without symbols that is (the other one seems to work but doesn't have UnsafeRawPointer as previously mentioned)).
I've filed [SR-2232] Broken Development Snapshot 2016-07-29-a · Issue #44839 · apple/swift · GitHub
/Jens
On Sun, Jul 31, 2016 at 7:21 PM, Erica Sadun <erica@ericasadun.com <mailto:erica@ericasadun.com>> wrote:
For me:
ld: library not found for -lswiftDispatch for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
-- E
On Jul 31, 2016, at 4:58 AM, Jens Persson via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
I've also tried the latest nightly (2 aug *), and I can verify that it's
broken in the same way as the latest dev snapshots.
(* https://swiftnightly.com,
swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain)
Note that the following suffices to demonstrate the issue (a command line
app):
import Foundation
print("Hello, world!") // This line is not needed to produce the linker
error.
Commenting out 'import Foundation' will make it compile.
(I also tried creating a single view iOS app and the standard template prj
won't compile with the nightly toolchain. Perhaps it's the same with the
latest dev snapshots, haven't tried.)
I'm a bit surprised that so few seem to have noticed that at least the
three latest dev snapshots (without symbols) are broken (ans the ones
without symbols don't include UnsafeRawPointer).
I'd like to try out the new UnsafeRawPointer API, and it's currently not
possible (beta 4 doesn't include it, and all the snapshots that include it
are broken/unusable as described above).
/Jens
···
On Wed, Aug 3, 2016 at 6:01 PM, Jordan Rose via swift-dev < swift-dev@swift.org> wrote:
On Aug 3, 2016, at 07:59, Erica Sadun via swift-dev <swift-dev@swift.org> > wrote:
On Aug 1, 2016, at 5:11 PM, Joe Groff via swift-dev <swift-dev@swift.org> > wrote:
On Jul 31, 2016, at 5:12 AM, Charles Lane via swift-dev < > swift-dev@swift.org> wrote:
I get a segmentation fault 11 at compile time with the 07/29 toolchain &
Xcode 8 beta 3. Can anyone point me in right direction to fix this?
On Sun, Jul 31, 2016 at 7:21 PM, Erica Sadun <erica@ericasadun.com> w
rote:
For me:
ld: library not found for -lswiftDispatch for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see
invocation)
-- E
On Jul 31, 2016, at 4:58 AM, Jens Persson via swift-dev < >>> swift-dev@swift.org> wrote:
Is it only me or is anyone else unable to use snapshot 2016-07-29-a?
In Xcode 8 beta 3, selecting that toolchain, creating a new command line
app, and trying to compile it results in:
ld: library not found for -lswiftDispatch for architecture x86_64
The only thing that’s known-broken is command-line tools (because they are linked statically). Everything else is working, or at least the normal levels of snapshot-buggy.
Jordan
···
On Aug 3, 2016, at 11:23, Jens Persson <jens@bitcycle.com> wrote:
I've also tried the latest nightly (2 aug *), and I can verify that it's broken in the same way as the latest dev snapshots.
(* https://swiftnightly.com <https://swiftnightly.com/>, swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain)
Note that the following suffices to demonstrate the issue (a command line app):
import Foundation
print("Hello, world!") // This line is not needed to produce the linker error.
Commenting out 'import Foundation' will make it compile.
(I also tried creating a single view iOS app and the standard template prj won't compile with the nightly toolchain. Perhaps it's the same with the latest dev snapshots, haven't tried.)
I'm a bit surprised that so few seem to have noticed that at least the three latest dev snapshots (without symbols) are broken (ans the ones without symbols don't include UnsafeRawPointer).
I'd like to try out the new UnsafeRawPointer API, and it's currently not possible (beta 4 doesn't include it, and all the snapshots that include it are broken/unusable as described above).
(Correction: (AND the ones WITH symbols don't include UnsafeRawPointer))
···
On Wed, Aug 3, 2016 at 8:23 PM, Jens Persson <jens@bitcycle.com> wrote:
I've also tried the latest nightly (2 aug *), and I can verify that it's
broken in the same way as the latest dev snapshots.
(* https://swiftnightly.com,
swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain)
Note that the following suffices to demonstrate the issue (a command line
app):
import Foundation
print("Hello, world!") // This line is not needed to produce the linker
error.
Commenting out 'import Foundation' will make it compile.
(I also tried creating a single view iOS app and the standard template prj
won't compile with the nightly toolchain. Perhaps it's the same with the
latest dev snapshots, haven't tried.)
I'm a bit surprised that so few seem to have noticed that at least the
three latest dev snapshots (without symbols) are broken (ans the ones
without symbols don't include UnsafeRawPointer).
I'd like to try out the new UnsafeRawPointer API, and it's currently not
possible (beta 4 doesn't include it, and all the snapshots that include it
are broken/unusable as described above).
/Jens
On Wed, Aug 3, 2016 at 6:01 PM, Jordan Rose via swift-dev < > swift-dev@swift.org> wrote:
On Aug 3, 2016, at 07:59, Erica Sadun via swift-dev <swift-dev@swift.org> >> wrote:
On Aug 1, 2016, at 5:11 PM, Joe Groff via swift-dev <swift-dev@swift.org> >> wrote:
On Jul 31, 2016, at 5:12 AM, Charles Lane via swift-dev < >> swift-dev@swift.org> wrote:
I get a segmentation fault 11 at compile time with the 07/29 toolchain &
Xcode 8 beta 3. Can anyone point me in right direction to fix this?
The symbols aren’t complete toolchains; they’re an overlay for debugging the other package.
Jordan
···
On Aug 3, 2016, at 11:25, Jens Persson <jens@bitcycle.com> wrote:
(Correction: (AND the ones WITH symbols don't include UnsafeRawPointer))
On Wed, Aug 3, 2016 at 8:23 PM, Jens Persson <jens@bitcycle.com <mailto:jens@bitcycle.com>> wrote:
I've also tried the latest nightly (2 aug *), and I can verify that it's broken in the same way as the latest dev snapshots.
(* https://swiftnightly.com <https://swiftnightly.com/>, swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain)
Note that the following suffices to demonstrate the issue (a command line app):
import Foundation
print("Hello, world!") // This line is not needed to produce the linker error.
Commenting out 'import Foundation' will make it compile.
(I also tried creating a single view iOS app and the standard template prj won't compile with the nightly toolchain. Perhaps it's the same with the latest dev snapshots, haven't tried.)
I'm a bit surprised that so few seem to have noticed that at least the three latest dev snapshots (without symbols) are broken (ans the ones without symbols don't include UnsafeRawPointer).
I'd like to try out the new UnsafeRawPointer API, and it's currently not possible (beta 4 doesn't include it, and all the snapshots that include it are broken/unusable as described above).
/Jens
On Wed, Aug 3, 2016 at 6:01 PM, Jordan Rose via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
On Aug 3, 2016, at 07:59, Erica Sadun via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
On Aug 1, 2016, at 5:11 PM, Joe Groff via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
On Jul 31, 2016, at 5:12 AM, Charles Lane via swift-dev <swift-dev@swift.org <mailto:swift-dev@swift.org>> wrote:
I get a segmentation fault 11 at compile time with the 07/29 toolchain & Xcode 8 beta 3. Can anyone point me in right direction to fix this?
The symbols aren’t complete toolchains; they’re an overlay for debugging
the other package.
Ah, thanks! I thought so at first, but then I uninstalled the -symbols-less
pkg and as the one with -symbols still seemed to work I got the idea that
it was a complete package : P Well, that explains why the UnsafeRawPointer
didn't seem to be in there then ... Sorry for the confusion.
I tried creating a Cocoa app now and it works. Thanks again for clearing
things up!
/Jens
···
On Wed, Aug 3, 2016 at 8:25 PM, Jordan Rose <jordan_rose@apple.com> wrote:
Jordan
On Aug 3, 2016, at 11:25, Jens Persson <jens@bitcycle.com> wrote:
(Correction: (AND the ones WITH symbols don't include UnsafeRawPointer))
On Wed, Aug 3, 2016 at 8:23 PM, Jens Persson <jens@bitcycle.com> wrote:
I've also tried the latest nightly (2 aug *), and I can verify that it's
broken in the same way as the latest dev snapshots.
(* https://swiftnightly.com,
swift-DEVELOPMENT-SNAPSHOT-2016-08-02-a.xctoolchain)
Note that the following suffices to demonstrate the issue (a command line
app):
import Foundation
print("Hello, world!") // This line is not needed to produce the linker
error.
Commenting out 'import Foundation' will make it compile.
(I also tried creating a single view iOS app and the standard template
prj won't compile with the nightly toolchain. Perhaps it's the same with
the latest dev snapshots, haven't tried.)
I'm a bit surprised that so few seem to have noticed that at least the
three latest dev snapshots (without symbols) are broken (ans the ones
without symbols don't include UnsafeRawPointer).
I'd like to try out the new UnsafeRawPointer API, and it's currently not
possible (beta 4 doesn't include it, and all the snapshots that include it
are broken/unusable as described above).
/Jens
On Wed, Aug 3, 2016 at 6:01 PM, Jordan Rose via swift-dev < >> swift-dev@swift.org> wrote:
On Aug 3, 2016, at 07:59, Erica Sadun via swift-dev <swift-dev@swift.org> >>> wrote:
On Aug 1, 2016, at 5:11 PM, Joe Groff via swift-dev <swift-dev@swift.org> >>> wrote:
On Jul 31, 2016, at 5:12 AM, Charles Lane via swift-dev < >>> swift-dev@swift.org> wrote:
I get a segmentation fault 11 at compile time with the 07/29 toolchain &
Xcode 8 beta 3. Can anyone point me in right direction to fix this?