Quickemu Quickly create and run optimised Windows, macOS and Linux desktop virtual machines. I may need to crosscompile Eiffel applications for MacOs
View On WordPress
seen from Maldives

seen from South Africa
seen from Türkiye
seen from China
seen from China
seen from Maldives
seen from United States
seen from Maldives

seen from Italy

seen from United Kingdom
seen from Canada

seen from United States

seen from United States
seen from United States

seen from United States
seen from China

seen from T1
seen from United States
seen from Italy
seen from T1
Quickemu Quickly create and run optimised Windows, macOS and Linux desktop virtual machines. I may need to crosscompile Eiffel applications for MacOs
View On WordPress
Go on Raspberry Pi: simple cross-compiling
#Go on Raspberry Pi: simple cross-compiling #golang #raspberrypi
Go – or Golang if you prefer – is a powerful programming language, applicable to virtually any platform, from single-board computers (SBCs) such as the Raspberry Pi to supercomputer clusters.
I tend to work at the lower end of that scale. And I was motivated to check out Go because it has a reputation for being fast – unlike, say, Python – while not requiring the hairy-chested self-flagellation…
View On WordPress
An overview and example of the technical steps to cross-compile Qt applications on Linux using the Yocto Project software development kit (SDK).
cross-compiling BusyBox is a piece of cake
cross-compiling BusyBox is a piece of cake
http://www.busybox.net/FAQ.html
http://landley.net/aboriginal/downloads/binaries
The FAQ told me where to get a ready-made cross-compiler. Within the untarred busybox sources I ran make menuconfig; make; make CONFIG_PREFIX=target_root_dir, then I ftp-ed the statically linked busybox to my target system, and halas!, it works.
Alright, menuconfig needs to know the prefix of the gcc etc., like…
View On WordPress
How to: Error "gnu/stubs-32.h: No such file or directory" while compiling Nachos source code
How to: Error "gnu/stubs-32.h: No such file or directory" while compiling Nachos source code
Error "gnu/stubs-32.h: No such file or directory" while compiling Nachos source code
I am trying to install Nachos on my laptop and I have Ubuntu 11.04 on the laptop.
The code is in C and so to build it I assume I will need cross compiler. This is where my problem is. I downloaded the source code of the MIPS cross compiler using the command
wget http://mll.csie.ntu.edu.tw/course/os_f08/assignme…
View On WordPress
C++11 is all the rage these days. It’s got a ton of new features language- and compiler-wise that are aimed towards fixing the many problems that have constantly plagued C++ over the years. It’s not a perfect language, not by a long shot, it’s ridiculously verbose when following best practices and it’s, well, C++. I’m sure I’ll get flamed.
Clanged now
Anyway, I've done doing the craziest port of recent times - at the same time GCC to Clang and from waf 1.5 to 1.6.
Quite a bit of quirks to work around.
waf has changed a lot internally, and from occasional backtraces I still see that I'm using compatibility mode somewhere. Oh well, one day when I'm bored...
Clang is also full of quirks. First, I had to build a cross-gcc for it anyway, because otherwise it totally refuses to link or assemble anything. Second, the freestanding standard C headers are not quite finished it seems - stdint.h for example spits out about 20-30 warnings about redefined macros, so I had to disable -Werror for now just to get it to compile. Third, the generated code, obviously, doesn't run. I got only first couple functions of kickstart bootloader to work in bochs, after that it just GPFs. Now if it keeps raining tomorrow like today, I'll certainly will go and look what happens there, otherwise it might have to wait until next weekend (actually, in two weeks).
I've finished my CS373 homework 5 at Udacity - more about that in the next post.
Clangestine
Finally, Clang people have enabled C++11 lambda support in clang and I'm busy hurrying my buildsystem into clang support for everything. I'm tired of endlessly autoconfiguring and building crossgcc for a bunch of different targets. Adding a target with some include paths set up for my OS into the clang frontend seems like a much simpler idea.