From: Sven <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Pixel <pixel@mandrakesoft.com>, caml-list@inria.fr
Subject: Re: [Caml-list] -thread and ocamlc vs ocamlc.opt
Date: Wed, 16 Jan 2002 17:46:02 +0100 [thread overview]
Message-ID: <20020116174602.A8424@dpt-info.u-strasbg.fr> (raw)
In-Reply-To: <20020116174351.A15459@pauillac.inria.fr>; from xavier.leroy@inria.fr on Wed, Jan 16, 2002 at 05:43:51PM +0100
On Wed, Jan 16, 2002 at 05:43:51PM +0100, Xavier Leroy wrote:
> > Is there really much people using the .opt compilers ? Does it really make
> > sense to have them packaged ?
>
> They speed up compilations by a factor of 2 or 3. Some of my
> colleagues use them for this reason, but that's because they have
> 3-year old workstations :-) With more recent hardware, I've never been
> bothered by the compilation speed of the non-.opt compilers, and thus
> don't use them except for testing purposes.
>
> > I myself was considering splitting them of into a separate debian package,
> > since they are big, and most probably not used that much.
>
> That sounds reasonable to me.
>
> > I could also simply disable the building of them, but am afraid someone will
> > need them in the future.
>
> Well, there are always users that cling to their 90 Mhz Pentium :-)
Ok, i will split them away in the next iteration of my packages, this will
save 3MB of installed stuff for people not using it. It will also make
downloading the ocaml package smaller :)))
Friendly,
Sven Luther
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-01-16 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-13 21:39 Pixel
2002-01-16 16:03 ` Xavier Leroy
2002-01-16 16:29 ` Sven
2002-01-16 16:38 ` Patrick M Doane
2002-01-16 16:43 ` Xavier Leroy
2002-01-16 16:46 ` Sven [this message]
2002-01-16 16:53 ` Pixel
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=20020116174602.A8424@dpt-info.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=pixel@mandrakesoft.com \
--cc=xavier.leroy@inria.fr \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox