From: Ildar Mulyukov <ildar@users.sourceforge.net>
To: sisyphus@altlinux.ru
Cc: tibor@altlinux.ru
Subject: Re: [sisyphus] Кривая сборка mono
Date: Wed, 19 Nov 2003 23:48:06 +0300
Message-ID: <3FBBD706.9020503@users.sourceforge.net> (raw)
In-Reply-To: <3FB36D4C.4040606@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
Для информации
--
Ildar Mulyukov,
free SW designer/programmer
================================================
email: ildar@users.sourceforge.net
projects: http://os-development.sourceforge.net/
home: http://tuganger.narod.ru/
ALT Linux Sisyphus (20030721)
================================================
[-- Attachment #2: Вложенное сообщение --]
[-- Type: message/rfc822, Size: 2475 bytes --]
From: Miguel de Icaza <miguel@ximian.com>
To: Ildar Mulyukov <ildar@users.sourceforge.net>
Cc: mono-list@lists.ximian.com
Subject: Re: [Mono-list] Mono status: mono/tests
Date: Wed, 19 Nov 2003 12:27:32 -0500
Message-ID: <1069262851.5037.216.camel@erandi.boston.ximian.com>
Hello,
> But the problem here: I was unable to find an information, which tests
> should the mono+mcs pass and which lead to failure. Of course, when mono
> becomes 1.0, all of the tests [hopefully] will work just fine. But now -
> can anyone give this information to me?
The JIT (mono/mono/tests) and Compiler (mcs/tests) should all pass with
the proper targets.
In mcs/tests, use `make test-compiler-jit'.
In mono/mono/tests use `make test'
> mcs --unsafe -nowarn:0162 -out:pinvoke1.exe pinvoke1.cs
>
> ** (/usr/bin/mcs.exe:30678): WARNING **: cant resolve internal call to
> "Test::MyClone()" (tested without signature also)
That is ok, it is just a warning.
Miguel
prev parent reply other threads:[~2003-11-19 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-13 11:38 Ildar Mulyukov
2003-11-19 20:48 ` Ildar Mulyukov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FBBD706.9020503@users.sourceforge.net \
--to=ildar@users.sourceforge.net \
--cc=sisyphus@altlinux.ru \
--cc=tibor@altlinux.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
ALT Linux Sisyphus discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/sisyphus/0 sisyphus/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 sisyphus sisyphus/ http://lore.altlinux.org/sisyphus \
sisyphus@altlinux.ru sisyphus@altlinux.org sisyphus@lists.altlinux.org sisyphus@lists.altlinux.ru sisyphus@lists.altlinux.com sisyphus@linuxteam.iplabs.ru sisyphus@list.linux-os.ru
public-inbox-index sisyphus
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.sisyphus
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git