caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: "Corey O'Connor" <coreyoconnor@gmail.com>
Cc: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Re: Problems linking in an object file produced with "ocamlopt -c -output-obj"
Date: 17 May 2005 16:52:24 +1000	[thread overview]
Message-ID: <1116312743.32536.286.camel@pelican.wigram> (raw)
In-Reply-To: <c12912350505162314389f00ad@mail.gmail.com>

On Tue, 2005-05-17 at 16:14, Corey O'Connor wrote:
> > _caml_atom_table
> > _caml_static_data_end
> > _caml_static_data_start
> > _caml_code_area_end
> > _caml_code_area_start
> 
> Umm.. Well. I changed asmrun/startup.c from:
> char * caml_static_data_start, * caml_static_data_end;
> char * caml_code_area_start, * caml_code_area_end;
> 
> To:
> char * caml_static_data_start, * caml_static_data_end = NULL;
> char * caml_code_area_start, * caml_code_area_end = NULL;
> 
> And *poof*, the errors went away. 
> 
> This is under Mac OS X 10.4 for what it's worth. Maybe something
> changed with GCC 4.0 effecting the export of extern variables with no
> initializers?

See ISO C99, 6.9.2./1

Variables with external linkage must be defined exactly
once (if they're used) or at most once (if they're not).

The above fragments do not constitute an external
definition, an initialiser is required for that.

The Ocaml sources are incorrect, you patch fixes them.
This should go in the bug tracker. 

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net




  reply	other threads:[~2005-05-17  6:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16 18:31 Corey O'Connor
2005-05-17  6:14 ` Corey O'Connor
2005-05-17  6:52   ` skaller [this message]
2005-05-18  8:02     ` [Caml-list] " Marcin 'Qrczak' Kowalczyk

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=1116312743.32536.286.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@inria.fr \
    --cc=coreyoconnor@gmail.com \
    /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).