caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Philip <feucht@uni-koblenz.de>
To: caml-list@inria.fr
Cc: Adrien Nader <adrien@notk.org>
Subject: Re: [Caml-list] Compile 4.01 on debian
Date: Sat, 14 Sep 2013 18:35:34 +0200	[thread overview]
Message-ID: <20130914183534.3d1911af@asus> (raw)
In-Reply-To: <20130914162653.GA2524@notk.org>


[-- Attachment #1.1: Type: text/plain, Size: 581 bytes --]

On Sat, 14 Sep 2013 18:26:53 +0200
Adrien Nader <adrien@notk.org> wrote:

> Hi,
> 
> On Sat, Sep 14, 2013, Philip wrote:
> > Hi list,
> > just pulled ocaml from git and made:
> 
> Did you pull from the trunk branch? If so you didn't get 4.01 but the
> development version which is in a much more incertain state.
> 
> That said, I'm running on trunk plus a few patches and I didn't get an
> error. Can you attach the output of ./configure?
> 
> Thanks,
> Adrien Nader
> 

Yes, of course:
did 'git checkout 4.01.0' and configure <output attached>

Thanks,
P

[-- Attachment #1.2: messages.txt --]
[-- Type: text/plain, Size: 3763 bytes --]

Configuring for a x86_64-unknown-linux-gnu ...
gcc found
The C compiler is ANSI-compliant.
Checking the sizes of integers and pointers...
Wow! A 64 bit architecture!
This is a little-endian architecture.
Doubles can be word-aligned.
64-bit integers can be word-aligned.
Native division and modulus have round-towards-zero semantics,
will use them.
ranlib found
#! appears to work in shell scripts
POSIX signal handling found.
expm1(), log1p(), hypot(), copysign() found.
getrusage() found.
times() found.
termcap functions found (with libraries '-lcurses')
You have BSD sockets.
socklen_t is defined in <sys/socket.h>
inet_aton() found.
IPv6 is supported.
unistd.h found.
off_t is defined in <sys/types.h>
dirent.h found.
rewinddir() found.
lockf() found.
mkfifo() found.
getcwd() found.
getwd() found.
getpriority() found.
utime() found.
utimes() found.
dup2() found.
fchmod() found.
truncate() found.
sys/select.h found.
select() found.
symlink() found.
waitpid() found.
wait4() found.
getgroups() found.
setgroups() found.
initgroups() found.
POSIX termios found.
Asynchronous I/O are supported.
setitimer() found.
gethostname() found.
uname() found.
gettimeofday() found.
mktime() found.
setsid() found.
putenv() found.
setlocale() and <locale.h> found.
dlopen() found in -ldl.
Dynamic loading of shared libraries is supported.
mmap() found.
pwrite() found
gethostbyname_r() found (with 6 arguments).
gethostbyaddr_r() found (with 8 arguments).
Replay debugger supported.
System stack overflow can be detected.
POSIX threads library supported.
Options for linking with POSIX threads: -lpthread
sigwait() found
Bytecode threads library supported.
X11 works
Options for compiling for X11: 
Options for linking with X11: -L/usr/lib/x86_64-linux-gnu -lX11
Configuring LablTk...
tcl.h and/or tk.h not found.
Configuration failed, LablTk will not be built.
BFD library not found, 'objinfo' will be unable to display info on .cmxs files
Assembler supports CFI

** Configuration summary **

Directories where OCaml will be installed:
        binaries.................. /usr/local/bin
        standard library.......... /usr/local/lib/ocaml
        manual pages.............. /usr/local/man (with extension .1)
Configuration for the bytecode compiler:
        C compiler used........... gcc
        options for compiling..... -fno-defer-pop -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT
        options for linking.......  -Wl,-E  -lm  -ldl -lcurses -lpthread
        shared libraries are supported
        options for compiling..... -fPIC -fno-defer-pop -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT
        command for building...... gcc -shared -o lib.so -Wl,-rpath,/a/path objs
Configuration for the native-code compiler:
        hardware architecture..... amd64
        OS variant................ linux
        C compiler used........... gcc
        options for compiling..... -Wall -D_FILE_OFFSET_BITS=64 -D_REENTRANT
        options for linking.......   -lm
        assembler ................ as
        preprocessed assembler ... gcc -c
        assembler supports CFI ... yes
        with frame pointers....... no
        native dynlink ........... true
        profiling with gprof ..... supported
Source-level replay debugger: supported
Additional libraries supported:
        unix str num dynlink bigarray systhreads threads graph
Configuration for the "num" library:
        target architecture ...... amd64 (asm level 1)
Configuration for the "graph" library:
        options for compiling .... 
        options for linking ...... -L/usr/lib/x86_64-linux-gnu -lX11
The "labltk" library: not supported

** OCaml configuration completed successfully **


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2013-09-14 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-14 15:59 Philip
2013-09-14 16:23 ` Kakadu
2013-09-14 16:26 ` Adrien Nader
2013-09-14 16:35   ` Philip [this message]
2013-09-14 16:33 ` Xavier Leroy
2013-09-14 16:39   ` Philip
2013-09-14 18:06   ` Wojciech Meyer

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=20130914183534.3d1911af@asus \
    --to=feucht@uni-koblenz.de \
    --cc=adrien@notk.org \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).