When I looked into the mono/runtime dir, I found a bunch
of windows .dll files.
Just because the files are called .dll doesn't mean they are
Windows libraries. I believe Mono uses the .dll and .exe
extensions just to make compatibility with binaries using those
names for references
-build.sh
not working right, though.
Cheers,
/ h+
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jon Watte
Sent: Sunday, July 04, 2004 9:26 AM
To: Brandon Knitter; 'mono-list'
Subject: RE: [Mono-list] Bootstrapping
I read through the docs for the CVS compile, as well as looked at the Mono
Runtime source code disrtibution and the MCS source code distribution. What I
found was that the mcs package requires the mono package to be compiled and
installed. When I looked into the mono/runtime dir, I found a bunch
The DLLs are not DLLs in the sense of binary shared libraries for Windows. The
files in mono/runtime are CLI/.NET assemblies (libraries, in this case).
The mono.tar.gz file contains prebuilt mcs.exe and DLLs. Once you have the
prebuild versions installed, you can download mcs.tar.gz and build
fdOn Tue, 2004-03-23 at 12:34, Noa Resare wrote:
A solution to this problem would be to have the ability to bootstrap the
mono environment from a verifiable source. I immediately come to think
about Portable.NET, since the cscc compiler is written in c and the
system bootstraps from a
Noa Resare wrote:
Trying to compile mono's mscorlib.dll however is a completely different
experience. Exceptions from
Mono.CSharp.RootContext.BootCorlib_PopulateCoreTypes decendands all over
the place.
How about running the newly compiled mcs.exe against PNET's corlib to
compile Mono's?
Stuart.
Instead of going outside of the project, why don't we just ask to have
the distribution files include a PGP signed MD5Hash? This is pretty
much standard practice for many projects.
rob
Noa Resare wrote:
Hello friends
I had a look at mono again yesterday for about a year away from it, and
tis 2004-03-23 klockan 19.22 skrev Ben Maurer:
I doubt there is one person in the world who can say that he has
traced the creation of his computer environment from square one
Valid point. However, it's all about risk/feasability. Just because I
can't verfiy evertything back to the big bang
On Tue, 2004-03-23 at 14:24, Noa Resare wrote:
In short, the verification of mcs is probably the least of your
problems. There are much bigger things you would really need to verify,
and mcs is easy in comparison.
I disagree. Yes, mcs is easy to verify, but it is also a very powerful
tis 2004-03-23 klockan 20.37 skrev Ben Maurer:
Not really. If you can get a backdoor into the C compiler, you can make
any kernel routine do anything. So, rather than just your app accepting
a backdoor password, i have a nice little rootkit.
Of course having a trojan in the system c compiler
On Tue, 2004-03-23 at 10:22, Ben Maurer wrote:
fdOn Tue, 2004-03-23 at 12:34, Noa Resare wrote:
A solution to this problem would be to have the ability to bootstrap the
mono environment from a verifiable source. I immediately come to think
about Portable.NET, since the cscc compiler is
11 matches
Mail list logo
