You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 243 Reporter: administrator Status: closed Resolution: fixed Priority: normal Severity: minor Category: ~DO NOT USE (was: OCaml general)
While re-installing ocaml 3.00, I accidentally came across a little bug in the
installation scripts : when the shell's variable "AS" isn't set, the native
assembler
(as) is correctly detected by configure.
But when performing something like export AS=foo, the detection seems to be
skipped and the native-compiling (make opt) goes wrong during mips.s
compilation.
This isn't a real problem because AS is initially empty. I discovered this
while
playing with a related strange behaviour : although specifying -cc gcc to
configure
works fine for the "make world" phase, during the "make opt" gcc isn't used.
Is this expected ? I'd love to be able to use GNU tools during all compilation
phases...
All of this isn't a bug, really, but may be confusing.
Thanks,
Olivier.
The text was updated successfully, but these errors were encountered:
While re-installing ocaml 3.00, I accidentally came across a little
bug in the installation scripts : when the shell's variable "AS"
isn't set, the native assembler (as) is correctly detected by
configure.
But when performing something like export AS=foo, the detection
seems to be skipped and the native-compiling (make opt) goes wrong
during mips.s compilation.
Certains programmes "make" ont la mauvaise habitude d'initialiser
les variables du Makefile à partir des variables de même nom de
l'environnement. Les Makefile de Caml utilisent $(AS) sans définir
cette variable pour faire référence à l'assembleur par défaut du
système...
Il y a peut-être une option de "make" pour désactiver cette
initialisation automatique; ou alors, utiliser GNU make?
This isn't a real problem because AS is initially empty. I
discovered this while playing with a related strange behaviour :
although specifying -cc gcc to configure works fine for the "make
world" phase, during the "make opt" gcc isn't used. Is this
expected ? I'd love to be able to use GNU tools during all
compilation phases...
Lorsqu'on ne spécifie pas "-cc", le script "configure" essaye de
déterminer les meilleurs compilateurs C à utiliser. Sur toutes les
architectures, gcc est le meilleur pour l'interprète de bytecode; mais
sur Mips et sur Alpha, le compilateur cc du système est meilleur pour
la bibliothèque d'exécution du compilateur natif ocamlopt.
Mais en effet ce choix de cc pour Mips et Alpha devrait être désactivé
si l'utilisateur a spécifié un compilo avec "-cc".
configure should not use cc for ocamlopt on the Alpha and Mips if the user
specified the C compiler to use with the -cc option. Feature implemented
2000-12-11 by Xavier.
Original bug ID: 243
Reporter: administrator
Status: closed
Resolution: fixed
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Full_Name: Olivier Parisy
Version: 3.00
OS: IRIX 6.5
Submission from: spiderman.labri.u-bordeaux.fr (147.210.8.140)
While re-installing ocaml 3.00, I accidentally came across a little bug in the
installation scripts : when the shell's variable "AS" isn't set, the native
assembler
(as) is correctly detected by configure.
But when performing something like export AS=foo, the detection seems to be
skipped and the native-compiling (make opt) goes wrong during mips.s
compilation.
This isn't a real problem because AS is initially empty. I discovered this
while
playing with a related strange behaviour : although specifying -cc gcc to
configure
works fine for the "make world" phase, during the "make opt" gcc isn't used.
Is this expected ? I'd love to be able to use GNU tools during all compilation
phases...
All of this isn't a bug, really, but may be confusing.
Thanks,
Olivier.
The text was updated successfully, but these errors were encountered: