There are a few things to try if you wouldn't mind. Could you make sure that all the pre-requisites from the swift compilation readme are installed:

{{
sudo apt-get install git cmake ninja-build clang python uuid-dev libicu-dev icu-devtools libbsd-dev libedit-dev libxml2-dev libsqlite3-dev swig libpython-dev libncurses5-dev pkg-config
}}

Also, this part is really important:

{{
sudo apt-get install clang-3.6
sudo update-alternatives --install /usr/bin/clang clang /usr/bin/clang-3.6 100
sudo update-alternatives --install /usr/bin/clang++ clang++ /usr/bin/clang++-3.6 100
}}
Make sure that you can run clang++ from the command line.

I installed swift on a fresh install of Ubuntu 14.04 on a Tegra TK1 into /opt/apple, and it worked once I installed all those packages. The bit about clang++ tripped me up at first.

If these don't work for you, I'll need to get more information about your system to figure out what might be different.

Comment by PeteVine (JIRA)

I'd needed clang before so yes I've got clang installed and symlinked. (clang++ as well)

Some more info and strace:

swiftc -v hello.swift 
Swift version 2.2-dev (LLVM 3ebdbb2c7e, Clang f66c5bb67b, Swift f089509539)
Target: armv7-unknown-linux-gnueabihf
/home/odroid/swift/usr/bin/swift -frontend -c -primary-file hello.swift -target armv7-unknown-linux-gnueabihf -disable-objc-interop -color-diagnostics -module-name hello -o /tmp/hello-3bfb0e.o

SwiftShims is being created in :

/tmp/org.llvm.clang.odroid/ModuleCache/13ZB8KO/SwiftShims-GBDR64.pcm

My guess is some search paths were hardcoded in your build so it doesn't work here. I'm new to swift's command line and have no idea which options could be fixing this.

Have a look at the attached strace.
swift.trace

Is this a duplicate of SR-23?

Comment by PeteVine (JIRA)

Looks like the same problem but over there it's happening during the build process itself. That should provide a clue as runtime requirements are much simpler - probably pointing at clang again...

Someone else mentioned this issue using a raspi version 2. In an effort to reproduce the bug, I bought one and installed a fresh image of raspian. I documented my process here:

http://www.housedillon.com/?p=2293

I wasn't able to reproduce this bug.

Would you mind replying with your exact environment (device, distribution, clang version, method for getting swift, etc.)?

Comment by Félix Lapalme (JIRA)

I have that exact same bug and I downloaded the version from your website (I used the option 1).
Here's some info about my Pi:

pi@raspberrypi ~ $ uname -a
Linux raspberrypi 4.1.6-v7+ #​810 SMP PREEMPT Tue Aug 18 15:32:12 BST 2015 armv7l
 GNU/Linux
pi@raspberrypi ~ $ clang --version
Debian clang version 3.8.0-svn250696-1 (trunk) (based on LLVM 3.8.0)
Target: arm-unknown-linux-gnueabihf
Thread model: posix
InstalledDir: /usr/local/bin
pi@raspberrypi ~ $ lsb_release -da
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 7.0 (wheezy)
Release:        7.0
Codename:       wheezy
pi@raspberrypi ~ $

If you want to, I could give you remote access to my Pi.

What version of Raspbian is your Pi running ?

Comment by PeteVine (JIRA)

@@hpux735

If I were you I'd start by tracking down the exact condition in the source that triggers the error. Possibly clang's source.

Maybe it's simply a case of certain hardcoded paths which is why it works on some distributions.

petevine (JIRA User) Because I can't reproduce this bug, it is very low priority. I have a lot on my plate trying to get the support that is there into swift 2.2, then I have a bigger project with tienex on my plate. You're encouraged to investigate if you'd like.

Comment by PeteVine (JIRA)

I completely forgot about swift so those were just some parting remarks. Good luck!

Darren Mo made some excellent progress on what I suspect is a duplicate of this:

https://bugs.swift.org/browse/SR-23

I've had good luck with the Raspian Jessie Light distribution, if you would like to see if that helps.

https://www.raspberrypi.org/downloads/raspbian/

Comment by Umberto Raimondi (JIRA)

Old bug, Swift 3.x works correctly on armv6 and armv7 SBCs.