unix build fails on MacOSX - error: unknown directive about micropython HOT 9 CLOSED

OSX is only supported on the osx branch.
If you first do

git checkout osx

it should work.

willy

On 03 Jan 2014, at 17:35 , focsic [email protected] wrote:

sekrier-mac:unix sekrier$ make
mkdir -p build
gcc -I. -I../py -Wall -Werror -ansi -std=gnu99 -Os -DUSE_READLINE -c -o build/main.o main.c
gcc -I. -I../py -Wall -Werror -ansi -std=gnu99 -Os -DUSE_READLINE -c -o build/nlrx86.o ../py/nlrx86.S
gcc -I. -I../py -Wall -Werror -ansi -std=gnu99 -Os -DUSE_READLINE -c -o build/nlrx64.o ../py/nlrx64.S
../py/nlrx64.S:9:5: error: unknown directive
.type nlr_push, @function
^
../py/nlrx64.S:25:5: error: unknown directive
.size nlr_push, .-nlr_push
^
../py/nlrx64.S:29:5: error: unknown directive
.type nlr_pop, @function
^
../py/nlrx64.S:35:5: error: unknown directive
.size nlr_pop, .-nlr_pop
^
../py/nlrx64.S:39:5: error: unknown directive
.type nlr_jump, @function
^
../py/nlrx64.S:58:5: error: unknown directive
.size nlr_jump, .-nlr_jump
^
../py/nlrx64.S:60:5: error: unknown directive
.local nlr_top
^
make: *** [build/nlrx64.o] Error 1

sekrier-mac:build sekrier$ gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/include/c++/4.2.1
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix

—
Reply to this email directly or view it on GitHub.

from micropython.

Question about this: I grabbed the osx branch and successfully compiled the stm port on my mac, and proceeded to install it on hardware that I developed that happens to use the STM32F405 chip. (This happy coincidence is what got me excited about the micropython project in the first place.)

Unfortunately, there does not appear to have been any action on the osx branch in the two weeks since it was forked. I am new to git, (and much more of a hardware developer rather than software,) so I'm not really sure if there is an easy way to pull the changes on the main branch to the osx branch so that I can continue to follow and test the ongoing development. Does anyone have any pointers, and is this a straightforward thing to do?

from micropython.

On the command line on the root of the code,

git pull master

should do the trick.

from micropython.

I also moved asm files to be preprocessed first, so one should be able to add #ifdef's to have Apple-hacked Clang happy in the main branch.

from micropython.

@piranna - thanks, I hoped it would be something simple like that. (Will try it this evening after the kids are in bed...)

from micropython.

You are welcome :-) Maybe you'll need to do something more especially if
there are conflicts that git can't be able to fix itself (I don't think so,
it's just a commit in advance), but anyway, there are a lot of git manuals
on internet and this is just content of second day of class 101, so don't
worry about it :-)

2014/1/3 blmorris [email protected]

@piranna https://github.com/piranna - thanks, I hoped it would be
something simple like that. (Will try it this evening after the kids are in
bed...)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/48#issuecomment-31554930
.

"Si quieres viajar alrededor del mundo y ser invitado a hablar en un monton
de sitios diferentes, simplemente escribe un sistema operativo Unix."
– Linus Tordvals, creador del sistema operativo Linux

from micropython.

I made a pull request with the remaining tweaks needed to build on plain OSX: #73

from micropython.

A clarification for those doing their development on a mac: the tweaks in the osx branch are only necessary for those trying to compile and run the unix port on OSX. For those compiling and testing the stm port (probably very few at this point until Damien delivers the Micro Python boards) the stm port within the main branch compiles perfectly well under osx using the compiler toolchain from https://launchpad.net/gcc-arm-embedded
There is a prebuilt mac-osx binary for the toolchain that is one version out of date (4.7) but worked perfectly for me.
Sorry for the confusion.

from micropython.

#73 fixes the issue with unix/ building on Mac.

from micropython.