Adam Lackorzynski adam at os.inf.tu-dresden.de writes:
Yes, please stick with 4.8 for now.
Adam
Thanks Adam! I will try that then.
___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.de
Hi all,
I am trying to compile l4re run time from the snapshot (l4re-snapshot-
2014053111) using GCC 4.9 on an x86-64 machine with multilib. The
compilation fails with not being able to find cstdio header file. I followed
the instructions in http://os.inf.tu-dresden.de/L4Re/build.html.
I note
Hi,
On Tue Jun 03, 2014 at 10:02:42 +, Ramya Masti wrote:
I am trying to compile l4re run time from the snapshot (l4re-snapshot-
2014053111) using GCC 4.9 on an x86-64 machine with multilib. The
compilation fails with not being able to find cstdio header file. I followed
the
hi!
i have some doubt about the buliding of l4re.who decides the order of the l4re
pkg complie?if i want to make pkg drivers earliear than pkg input,hao can i do?
does the /pkg/XXX/Control mean anything? and in the obj directory, there are
.pc files like libdrivers-input.pc etc.what do they
Hi,
On 16.04.2013, at 14:40, gaober wrote:
i have some doubt about the buliding of l4re.who decides the order of the
l4re pkg complie?if i want to make pkg drivers earliear than pkg input,hao
can i do?
does the /pkg/XXX/Control mean anything? and in the obj directory, there are
.pc files
Hi,
I guess the problem is not the compilation but the used host library:
/usr/lib/gcc/i686-redhat-linux/4.4.4/libgcc_eh.a(unwind-dw2.o): In function
`.L107': (.text+0xb79): undefined reference to `__stack_chk_fail_local'
Seems Fedora builds GCC with stack protection enabled. For this
reason
Christian said:
Seems Fedora builds GCC with stack protection enabled. For this
reason (and some others), we switched to our custom build GCC with
Genode.
Ah, I see, thanks for the info. I might switch this dev box to Debian -
this isn't the only developer-unfriendly issue I've ran into due to
Hi,
On Fri Oct 29, 2010 at 12:09:52 -0700, Thomas DuBuisson wrote:
I've never had success with Fiasco but decided to give it another go
so I could run some benchmarks. In short, I had one success and two
failures. Any help would be appreciated.
1) I can build Fiasco for x86 on the host
On Sun Oct 31, 2010 at 14:48:51 -0700, Thomas DuBuisson wrote:
I'm mainly using the codesourcery ones nowadays (4.4). Nevertheless,
does it help if you remove the abi=apcs-gnu line in src/Makeconf.arm?
That causes it to fail just as early with a different message. I'll
try with 4.4 and
2) Failure to build Fiasco ARM
This early failure seems to be a simple problem with gcc changing the
arguments - can anyone tell me the version of the official arm
compiler in use? I'm running arm-linux-gcc 3.4.4.
make[1]: Entering directory `/home/tommd/dev/L4/L4Re/build_arm'
All,
I've never had success with Fiasco but decided to give it another go
so I could run some benchmarks. In short, I had one success and two
failures. Any help would be appreciated.
1) I can build Fiasco for x86 on the host (32 bit x86 system). Yay
2) Can't build Fiasco for ARM on an x86 host
11 matches
Mail list logo
