public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Gough <bjg@network-theory.co.uk>
To: Emmanuel Chomarat <Emmanuel.Chomarat@bigfoot.com>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: pb compile under borland c++
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <15219.1642.877179.846853@debian> (raw)
In-Reply-To: <17096239334.20010809231215@bigfoot.com>

Emmanuel Chomarat writes:
 > 
 > in interpolation subdir
 > akima.c
 > Error E2024 akima.c 244: Cannot modify a const object in function
 > Error E2024 akima.c 280: Cannot modify a const object in function
 > Error E2024 vegas.c 606: Cannot modify a const object in function random_point
 > Error E2024 gear1.c 92: Cannot modify a const object in function gear1_apply
 > 
 >     Not really hard to fix but hard to understand. why it's prevent warning,
 >     it cause errors :)

Thanks for the bug reports.  I have made the line into a macro
DISCARD_POINTER(p) which can be redefined in config.h.

 > I succeed to compile all module and to build libgsl.lib. but now when
 > i try to link i have this error:
 > Turbo Incremental Link 5.00 Copyright (c) 1997, 2000 Borland
 > Error: Unresolved external '_gsl_sf_lngamma' referenced from C:\LIBGSL.LIB|gamma
 > Error: Unresolved external '_gsl_sf_choose' referenced from C:\LIBGSL.LIB|binomial
 > Error: Unresolved external '_gsl_sf_lnfact' referenced from C:\LIBGSL.LIB|poisson

The functions the randist directory (libgslrandist.a) need to use some
functions from the specfunc directory, and cannot find them.  Perhaps
it is due to the order of linking the files?

  reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Emmanuel Chomarat
2001-12-19 13:20 ` Brian Gough [this message]
2001-12-19 13:20   ` Re[2]: " Emmanuel Chomarat
2001-12-19 13:20   ` Emmanuel Chomarat
2001-12-19 13:20     ` Brian Gough

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=15219.1642.877179.846853@debian \
    --to=bjg@network-theory.co.uk \
    --cc=Emmanuel.Chomarat@bigfoot.com \
    --cc=gsl-discuss@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).