I've made a pull request, https://github.com/apple/swift/pull/435, that
attempts to fix this problem. I'm not entirely sure why clang is not
seeing the flags they are clearly in the argument list.
On Sat, Dec 5, 2015, at 05:15 PM, Dmitri Gribenko wrote:
> On Sat, Dec 5, 2015 at 6:28 AM, Ryan Lovel
I've been playing around with a Swift wrapper for the FFmpeg C libraries
(e.g., libavutil, libavcodec, libavformat, etc...). While providing some
extensions to some of the core C structures I've run into something that
doesn't feel quite right to me.
Before I provide a discussion here is a Gist [0
On Wed, Dec 16, 2015, at 03:12 AM, Dave Abrahams via swift-dev wrote:
>
> > On Dec 15, 2015, at 11:51 PM, Kevin Ballard wrote:
> >
> > On Tue, Dec 15, 2015, at 11:25 PM, Dave Abrahams wrote:
> >>
> >>> On Dec 15, 2015, at 6:46 PM, Kevin Ballard wrote:
> >>>
> >>> On Tue, Dec 15, 2015, at 06:3
On Mon, Jan 4, 2016, at 03:40 PM, Tom Gall via swift-dev wrote:
> Building with: ./swift/utils/build-script -R -t --foundation
>
> on Linux (gentoo amd64) fails with
>
> + /usr/bin/cmake --build
> /home/tgall/swift/build/Ninja-ReleaseAssert/swift-linux-x86_64 -- -j4
> SwiftUnitTests
>
> [6/29] G
consistently read filenames and such with the way
the OS is presenting them.
https://docs.python.org/2/library/sys.html#sys.getfilesystemencoding
On Mon, Jan 4, 2016, at 05:12 PM, Ryan Lovelett via swift-dev wrote:
> On Mon, Jan 4, 2016, at 03:40 PM, Tom Gall via swift-dev wrote:
> > Buil
ME="en_US"
> LC_COLLATE="en_US"
> LC_MONETARY="en_US"
> LC_MESSAGES="en_US"
> LC_PAPER="en_US"
> LC_NAME="en_US"
> LC_ADDRESS="en_US"
> LC_TELEPHONE="en_US"
> LC_MEASUREMENT="en_US"
;
> >> tgall@mars ~/swift $ locale
> >>
> >> LANG=en_US
> >> LC_CTYPE=C
> >> LC_NUMERIC="en_US"
> >> LC_TIME="en_US"
> >> LC_COLLATE="en_US"
> >> LC_MONETARY="en_US"
> >> LC_M
What is the "correct" way to remove a Swift Dev snapshot from OS X? It
comes with a nice installer package it install is there an equivalent
for removal?
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
I'm beginning to try to port some of my existing C code over to Swift
(you have no idea how excited that makes me). Unfortunately, I've hit a
stumbling block.
When interacting with some of the system/hardware interfaces in Linux it
sometimes (often?) becomes necessary to interact with I/O Control
Response inline:
On Tue, Jan 5, 2016, at 03:12 PM, Xi Ge wrote:
>
> > On Jan 5, 2016, at 11:54 AM, Ryan Lovelett via swift-dev
> > wrote:
> >
> > I'm beginning to try to port some of my existing C code over to Swift
> > (you have no idea how excited tha
o see invocation)
:0: error: build had 1 command failures error: exit(1):
["/usr/bin/swift-build-
tool", "-f", "/home/ryan/Source/castable-
live/.build/debug/CastableLive.o/llbuild.yaml"]
On Tue, Jan 5, 2016, at 04:57 PM, Kate Stone wrote:
>> On Jan 5, 2016, at 12:
nto
> /Library/Developer/Toolchains/ with /Library/Developer/Toolchains/swift-
> latest.xctoolchain pointing to the most recently installed
> snapshot. — Johan
>
> On Tue, Jan 5, 2016 at 5:40 PM, Ryan Lovelett via swift-dev d...@swift.org> wrote:
>> What is the "correct&quo
I file one?
> >
> > Thanks again for the quick response.
> >
> > On Mon, Feb 29, 2016, at 10:55 PM, Dmitri Gribenko wrote:
> >> On Mon, Feb 29, 2016 at 7:51 PM, Ryan Lovelett via swift-dev
> >> wrote:
> >> > I have a daily build of Swift that I make
On Mon, Mar 14, 2016, at 06:42 PM, Dmitri Gribenko wrote:
> On Mon, Mar 14, 2016 at 3:38 PM, Ryan Lovelett
> wrote:
> > On Tue, Mar 1, 2016, at 12:16 AM, Dmitri Gribenko wrote:
> >> IIRC there is no issue in the bug tracker, please feel free to file one!
> >>
> >> Also, if you are familiar with bi
On Mon, Mar 14, 2016, at 06:44 PM, Greg Parker wrote:
>
> > On Mar 14, 2016, at 3:38 PM, Ryan Lovelett via swift-dev
> > wrote:
> >
> >> On Tue, Mar 1, 2016, at 12:16 AM, Dmitri Gribenko wrote:
> >>
> >> IIRC there is no issue in the bug tracke
On Mon, Mar 14, 2016, at 06:42 PM, Dmitri Gribenko wrote:
> On Mon, Mar 14, 2016 at 3:38 PM, Ryan Lovelett
> wrote:
> > On Tue, Mar 1, 2016, at 12:16 AM, Dmitri Gribenko wrote:
> >> IIRC there is no issue in the bug tracker, please feel free to file one!
> >>
> >> Also, if you are familiar with bi
> Thank you for the hard work! It is definitely a good idea to create a
> bug, I am not aware of one existing on bugs.swift.org.
Great, I've reported this as: https://bugs.swift.org/browse/SR-1023.
___
swift-dev mailing list
swift-dev@swift.org
https://
On Tue, Mar 22, 2016, at 01:26 PM, William Dillon wrote:
>
>>
>> Phew. Well I finally got everything ready to where I could bisect
>> binutils. I won't bore with the details of what it took to actually be
>> able to bisect binutils (unless someone actually wants to know).
>
> I would be interest
I've hit a road block in my resolution of SR-1023 [1].
I have a "working" patch in so far as I can now apply my patches to
master and resume compiling. I think my patch for the CMake changes is
largely acceptable (based on feedback of the associated PR [2]).
However, my patch for the driver has n
On Thu, Apr 14, 2016, at 09:17 AM, Joseph Bell via swift-dev wrote:
> Howdy,
>
> I've mentioned this once before and didn't get any feedback; I thought
> I'd give it one more shot.
>
> Has anyone out there tried building, from scratch, the Swift 3.0
> package on Ubuntu? The compile, link, packagin
b/oss-swift-package-linux-ubuntu-14_04/993/consoleText
>>
>> lit.py: lit.cfg:101: note: 'pexpect' module unavailable, skipping
>> related tests
>>
>> Perhaps pexpect should be added to the CI server so these tests can
>> begin failing properly.
>>
n the mechanics of what happens
when I type "import Glibc" into the REPL/lldb?
On Thu, Apr 14, 2016, at 05:47 PM, Dmitri Gribenko wrote:
> +Brian
>
> On Thu, Apr 14, 2016 at 2:46 PM, Ryan Lovelett via swift-dev
> wrote:
> > I've played around with `git bisect` and I
Progress. Hat tip to William Dillon (@hpux735 on Twitter) for pointing
something out; `strace`
Ran `strace` on the REPL while trying to import Glibc. Noticed that it
was looking for a file: /usr/lib/lldb/clang/linux/x86_64/glibc.modulemap
which does not exist. However,
/usr/lib/lldb/clang/linux/x8
Facepalm.
On Fri, Apr 15, 2016, at 11:11 PM, Ryan Lovelett wrote:
> Progress. Hat tip to William Dillon (@hpux735 on Twitter) for pointing
> something out; `strace`
>
> Ran `strace` on the REPL while trying to import Glibc. Noticed that it
> was looking for a file: /usr/lib/lldb/clang/linux/x86_6
On Tue, Apr 19, 2016, at 11:00 AM, Joseph Bell wrote:
> Hi all,
>
> Has anyone looked further at getting the REPL working again on the
> master branch builds? Or for that matter installed pexpect on the CI
> server to properly fail the build?
@Joe,
Out of curiosity, did the work-around I propo
I've been using CLion lately for C++ development on Linux. It uses CMake
for its integrated builds as does Swift. This seems, at least at first
glance, to make it possible to use CLion as an IDE on Linux to develop
the Swift toolchain.
I was just wondering if anyone has attempted to be able to use
restore functionality to lldb/repl.
> >
> > Unfortunately too many things have changed in the build system since
> > that commit for a revert to make sense anymore
> >
> > Can anyone provide documentation/explain the mechanics of what happens
> > when I type
On Wed, Apr 20, 2016, at 08:17 PM, Greg Parker via swift-dev wrote:
>
> > On Apr 20, 2016, at 5:14 PM, no-re...@swift.org wrote:
> >
> > New issue found!
> >
> > [FAILURE] oss-swift-package-linux-ubuntu-14_04 [#1072]
> >
> > Build URL:
> > https://ci.swift.org/job/oss-swift-package-linux-ubun
On Fri, Apr 22, 2016, at 12:28 AM, Daniel Dunbar via swift-dev wrote:
> Hi all,
>
> I would like to propose that we include `FileCheck` in the downloadable
> toolchains.
>
> The downloadable toolchains are quite useful for people who are wanting
> to work on Swift projects that use FileCheck (llb
On Sun, Apr 24, 2016, at 05:44 PM, Joseph Bell via swift-dev wrote:
> Well, I thought the REPL issues had all been put to rest, but now I am
> seeing this on Ubuntu 14.04 (15.10 I do not see it):
>
> ➜ package-swift-3.0 git:(swift-3.0) ✗ ./install/usr/bin/swift
> ==18928==ASan runtime does not com
On Thu, Apr 21, 2016, at 01:12 PM, Todd Fiala via swift-lldb-dev wrote:
> Hi all,
> I wanted to propose how we can go about handling newer Ubuntu releases
> in a systematic way. This covers how we handle Ubuntu on our CI, but
> also reflects where we'll be focusing effort at any given point. The
> ../swift/utils/build-script -d \
> --install-prefix="/usr" \
> --install-symroot="${cc_files}/out/symroot" \
> -- \
> --cross-compile-tools-deployment-targets=linux-armv7 \
> --cross-compile-sysroot="${sysroot}" \
> --cross-compile-toolchain-bin="${toolchain}"
> --stdlib-deployment-targets="mac
Big help! Thank you Rintaro.
___
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev
On Sat, May 14, 2016, at 12:17 PM, William Dillon via swift-dev wrote:
> I'm in favor. The current disparate use of linkers overly complicates
> the build scripts, and given that BFD seems to be a liability, I think it
> makes sense to transition. In the interest of full disclosure, I don't
> ful
I think I've discovered a few bugs/inconsistencies with generic protocol
conformance. I'm mostly concerned with if these have been seen/reported
before. I'm pretty sure they are all bugs but I could be wrong (I've
been wrong before, it _will_ happen again 😀).
All of the (possible?) bugs can be see
Ugh. Can you un-send an email. I was wrong. See it happened AGAIN. 😂
On Mon, May 23, 2016, at 12:16 PM, Ryan Lovelett via swift-dev wrote:
> I think I've discovered a few bugs/inconsistencies with generic protocol
> conformance. I'm mostly concerned with if these have been seen/r
On Wed, Jun 8, 2016, at 09:33 AM, Alex Blewitt via swift-dev wrote:
> There is an increasing number of languages and IDEs supporting VS Code’s
> language agnostic server protocol.
>
> https://github.com/Microsoft/vscode-languageserver-protocol/wiki/Protocol-Implementations
While it is unclear fro
On Mon, Jun 13, 2016, at 11:33 PM, Dmitri Gribenko via swift-dev wrote:
> On Sat, Jun 11, 2016 at 8:12 AM, 김종수 via swift-dev
> wrote:
> > I am testing Swift in "Windows Subsystem for Linux" which is a new feature
> > of Windows 10 Anniversary Update scheduled in this year. WSL is Ubuntu LTS
> > 14
The `soucekitd.framework` that comes bundled with Xcode does not include
the headers, specifically `sourcekitd.h` [1]. On the other hand, the
toolchains that get downloaded from Swift.org do come with the headers.
Is there any particular reason for this?
The reason why I ask is that libraries that
I am proposing that https://github.com/apple/swift/pull/4177 be reviewed
for acceptance in Swift 3.0.
(Not really sure what the format of this e-mail should be, subject or
body. Sorry if this is wrong.)
Thank you!
___
swift-dev mailing list
swift-dev@sw
> The header is not currently bundled with Xcode because it is not
> considered a supported stable API.
> The toolchain snapshots from swift.org do not make any promises about
> stable APIs so we include it with those.
Thank you for the response. It seems that you do a lot of the
management/develo
I just noticed that if you do `utils/update-checkout --clone` it pulls
down `compiler-rt`. I have been building Swift from source on Linux for
awhile now. I've never once checked out compiler-rt. Which makes me
wonder if that repository is even in use.
Here is the question: what is the compiler-rt
Is it known/expected that Swift will not build with Clang 3.9.0? My
personal build-bot recently updated its upstream dependency from Clang
3.8.1 to Clang 3.9.0 and since then it will not build the
swift-3.0.1-RELEASE. It seems that others have noticed this
(https://gist.github.com/eyeplum/94627aac7
I've found what I believe is a bug. Though I'm unclear if the bug is in
Swift 3.1 or Swift 3.2/4.0. All I can say for sure is the behavior is
quite drastically different between the two.
For the code below (and attached):
import Cocoa
var data = Data(bytes: [0x50, 0x4B, 0x01, 0x02, 0x41,
>> On Aug 24, 2017, at 11:05 AM, Michael Gottesman via swift-dev >> d...@swift.org> wrote:>>>
>>>
>>>> On Aug 24, 2017, at 10:47 AM, Ryan Lovelett via swift-dev >>> d...@swift.org> wrote:>>>>
>>>> I've found
>>
>>>> On Aug 24, 2017, at 11:07 AM, Philippe Hausler
>>>> wrote:>>>>
>>>> Is there a radar or bugs.swift.org ticket filed on this?
>>>>
>>>> I presume because of the import this is a Darwin thing and not a
>>>> linux thing
46 matches
Mail list logo
