Hi Pascal,
On 2024-01-24 12:53, Pascal Scholz wrote:
1) Is there a technical reason for L4Re still using the Linuxthreads
implementation and not some kind of NPTL port or other
implementations?
The libpthread implementation used in L4Re is based on the linuxthreads
(formerly named
Hi Haohui,
the svn repository is not up to date. To get the latest source code
please download the snapshot[0], which includes the latest version of
L4Linux (5.15).
Best regards,
- Marcus
[0] https://l4re.org/download/snapshots/
On 2022-03-04 07:43, Haohui Mai wrote:
Greetings!
I've
Hi Yang,
85 is the SPI (Shared Peripheral Interrupt) number of the Ethernet
device, but the Res.irq command takes the interrupt ID as an argument.
However interrupts IDs are structured in:
16 SGIs (Software Generated Interrupt, interrupt ID 0-15)
16 PPIs (Private Peripheral Interrupt,
Hi Nancy,
Trolltech has not been the owner of Qt since more than 7 years. You
should look into support from "The Qt Company", which can be reached
under qt.io. The folks there may be the best place to start when you
want to look at what to port the framework and what needs to be adapted.
Hi Harini,
On 2015-02-11 07:49, Harini Balachandran wrote:
We mounted the ramdisk and copied the binary to l4linux ramdisk but
while executing on l4linux,
/# cd tmp
/tmp#./hello
/bin/sh: ./hello : not found
I assume the `hello` binary is really there. One common other problem
that leads
Hi,
On 2015-02-05 05:57, Gayathri Nagarajan wrote:
Upon the boot of l4linux iso image using QEMU, I got the following:
vmlinuz | RAMDISK: ext2 filesystem found at block 0
vmlinuz | RAMDISK: Loading 3072KiB [1 disk] into ram disk... done.
vmlinuz | EXT4-fs (ram0): couldn't mount as ext3 due to
Hi,
On 2015-02-04 14:39, Gayathri Nagarajan wrote:
Upon the boot of l4linux iso image using QEMU, I got the following:
vmlinuz | RAMDISK: ext2 filesystem found at block 0
vmlinuz | RAMDISK: Loading 3072KiB [1 disk] into ram disk... done.
vmlinuz | EXT4-fs (ram0): couldn't mount as ext3 due to
Hi Karl,
the haecer library can be found here:
tudos.org/~mhaehnel/haecer.tar.gz
it requires another lib called libdebug that provides MSR access for the
userland. This is purely a means of benchmarking and measurements as it
severely breaks security of the system because MSR accesses are
Hi Cem,
On 2014-09-18 10:00, cem akpolat wrote:
Dear all,
I was searching how to debug the fiasco kernel through JDB. The
following link gives a good approach how to it through minicom.
http://os.inf.tu-dresden.de/l4env/doc/html/dev-overview/ [1]
However, even if I see the messages on the
.
Best regards
- Marcus
best,
ramya
p.s. my board requires that I run an older version of the kernel - so
the pain.
From: l4-hackers [l4-hackers-boun...@os.inf.tu-dresden.de] on behalf
of Marcus Hähnel [mhaeh...@os.inf.tu-dresden.de]
Sent: 16 September
Hi Yunchuan,
Taeung made a nice guide on how to get everything to work with the
i.MX6.
Please have a look at these threads:
https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006463.html
https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006298.html
- Marcus
On 2014-08-04 09:47,
On 2014-07-29 15:09, Jorge Ventura wrote:
ImportError: No module named tempita
make: *** [arch/api/invocation.h] Error 1
What is this module tempita? What package is that?
The relevant debian package is python-tempita.
- Marcus
___
l4-hackers
On 2014-05-29 18:22, Yuxin Ren wrote:
On Tue, May 27, 2014 at 11:44 PM, Marcus Hähnel
mhaeh...@os.inf.tu-dresden.de wrote:
On 2014-05-28 03:59, Yuxin Ren wrote:
Thank you very much.
But how can I know which file is compiled?
What do you mean with 'how can I know'?
Do you mean how you can
On 2014-05-28 03:59, Yuxin Ren wrote:
Thank you very much.
But how can I know which file is compiled?
This is decided during build time based on your configuration. The
vuild system decides which file to build based on the
CONFIG_VIRT_OBJ_SPACE setting. See src/Modules.generic.
- Marcus
On 2014-05-22 16:02, Valentin Hauner wrote:
On 05/22/2014 03:41 PM, Marcus Hähnel wrote:
Sorry. Forgot to reply to the previous mail. Is this for a 64-bit or
32-bit system?
No problem.
It's a 32-bit system, I'm compiling into ./bin/x86_586.
You need a terminal to do input. fbterminal is one
. Is this for a 64-bit or
32-bit system?
- Marcus
Best regards,
Valentin
On 05/20/2014 11:11 AM, Valentin Hauner wrote:
On 05/19/2014 08:00 PM, Marcus Hähnel wrote:
Do 'svn up libc_be_stdin' in the pkg/ directory. Then build the new
package and you can link against it.
Thanks
https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006453.html
https://os.inf.tu-dresden.de/pipermail/l4-hackers/2014/006454.html
- Marcus
On 2014-05-19 10:18, Valentin Hauner wrote:
Hi!
I'm having some trouble with doing simple I/O actions in the clntsrv
example
Hi,
On 2014-05-19 18:16, Valentin Hauner wrote:
Adding libstdc++ to REQUIRES_LIBS works like a charm, but adding
libc_be_file_stdin gives me the following error:
Library dependencies missing: libc_be_file_stdin in directory
'/home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv';
Hi ba_f,
BTW before that missing lib error, i get a lot of multiple
definition
of
Could you show some examples of those errors please?
Adam
./tpm_integrity.o: In function `TPM_Extend':
/home/ba_f/vTPM/server/src/tpm_integrity.c:39: multiple definition of
`tpm_log'
Hi Valentin,
On 2014-05-17 13:00, Valentin Hauner wrote:
I did not change the Makefile, so g++ is used for compiling (and not
gcc). I've added
CXX_FLAGS = -lstdc++
but that doesn't help.
The standard way for the l4re build system to link against certain
libraries ist to put them in the
Hi Jack,
On 2014-04-06 11:24, Jack Andrews wrote:
Hi,
Sorry if this is not the right forum.
you've come to the right place.
I'm following
https://os.inf.tu-dresden.de/fiasco/build.html [1]
and i could build fiasco just fine.
I made a couple of guesses about how to build L4Re because I
Hi Emanuel,
it looks like you have some very basic misunderstandings of the build
system. Looking at what the script you used seems to have done I
recommend starting from scratch, because I suspect you abused the build
directory to a point where it is no longer worth saving.
You main
Hi Daniel,
Have you done a
make oldconfig
in the src/l4 directory? This has fixed similar problems for me in the
past. The configuration is specific to the files that come with the
compiler and needs to be notified of a compiler change.
- Marcus
On 2013-10-12 18:33, Daniel Müller wrote:
Hi Vijay,
you can find an introduction to running L4Re/Fiasco.OC and programs for
the system here
https://os.inf.tu-dresden.de/fiasco/build.html
and here
https://os.inf.tu-dresden.de/L4Re/doc/l4re_getting_started.html
For writing your own programs you can get some pointers in the existing
I tried to add a few .cpp files to Makefile but it seems that L4Re
build
systems ignores this extension.
Not exactly. The build system considers .cpp as preprocessed C files.
Please use .cc as extension for C++ code.
Then how do I port libs like Qt to L4Re? Qt uses .cpp extension for
C++
25 matches
Mail list logo
