efined.
> If you go this path, it should be used when compiling on windows
> (not when the target is windows).
>
> - avih
>
> On Sunday, May 12, 2024 at 02:36:25 AM GMT+3, Nicolas Sauzede <
> nicolas.sauz...@gmail.com> wrote:
>
>
> Hi,
>
> I cre
Hi,
I created a very simple mob branch to color warnings/errors output, just
like GCC and Clang.
$ git fetch origin
refs/mob/mob_nsauzede/colored_warning_error:colored_warning_error
$ git checkout colored_warning_error
I tested it successfully on Linux (Arch) and Windows (MSYS2, 64
Hello,
This is my first post to the uClibc mailing-list.
I have a question related to weak API symbols of the uClibc.
I have noticed that, when linking a static binary against the uClibc,
that certain symbols,
such as 'abort', are not defined as weak symbol.
The end result is that this kind
, 2013 at 04:13:10PM +0100, Nicolas Sauzede wrote:
Hello,
This is my first post to the uClibc mailing-list.
I have a question related to weak API symbols of the uClibc.
I have noticed that, when linking a static binary against the
uClibc, that certain symbols,
such as 'abort', are not defined
Ci-joint la version corrigée par Stéphane..
Quelle étape faut-il franchir ensuite pour envoyer le ddtp (après ultimes
relectures bien sûr) ?
Qui s'en occupe/comment/quand ?
hsetroot.ddtp
Description: Binary data
Sorry this patch is ridiculous, but it fixes a minor display
typo in qemu-0.9.0 and qemu-snapshot-2007-02-08_05
(I don't have CVS access handy here)
NS
---
diff -r a294d9db2cd9 configure
--- a/configure Thu Feb 08 14:55:07 2007 +0100
+++ b/configure Thu Feb
ate if you can send me your written device so I can see
if it can help me!
Thanks
Ale
2006/8/22, Nicolas SAUZEDE:
Hi
Alessandro,
Concerning your cosimulation problem, I may help a little bit,
because when you first posted on the qemu dev list about your sysc
project,
it motivated m
target etc...
Anyway I appreciate if you can send me your written device
so I can see if
it can help me!
Thanks
Ale
2006/8/22, Nicolas SAUZEDE-NONST [EMAIL PROTECTED]:
Hi Alessandro,
Concerning your cosimulation problem, I may help a little bit,
because when you first posted
to recognize
it as a pci-card.
Can somebody help me?
3) Interrupt implementation: I need only to implement
..._update_irq right?
It seems no problem, but I want to be secure about it.
2006/8/22, Nicolas SAUZEDE-NONST [EMAIL PROTECTED]:
Hi Alessandro,
Concerning your cosimulation problem
One stupid question regarding inclusion of bcm43xx in upcoming 2.6.17 :for my 4306 to work (well configured with WEP key, etc..), after every boot, I have to issue as root :iwlist scan eth1dhclient eth1
because the WEP authentication was not totally finished with my APIIRC, there is a patch
10 matches
Mail list logo
