unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Marius Vollmer <mvo@zagadka.ping.de>,
	Bo Forslund <bo.forslund@abc.se>,
	guile-devel@gnu.org
Subject: Re: some rpm building questions
Date: Fri, 04 Oct 2002 10:48:47 -0500	[thread overview]
Message-ID: <8765wiryqo.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <20021004130821.GB20754@www> (rm@fabula.de's message of "Fri, 4 Oct 2002 15:08:21 +0200")

rm@fabula.de writes:

> Are you shure about this? If i understand it right it changes the behavior
> of libltdl, or? There might be apps (admittedly, broken) that depend on
> exactly this behaviour. 

We will be providing libguile-ltdl, and libguile will link against
it.  We will provide no headers for any of the libguile-ltdl
functionality, but dynamic-link and friends will be using it.

This has already been done, though I haven't finished committing the
second half of the work that mvo started, and so far it fixes the
problems listed below (most reported upstream in November of last year
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=120169&repeatmerged=yes).

We will also probably be adding support for /etc/ld.so.conf and
/usr/local/lib/ on the platforms where we already know it makes sense.

2002-10-04  Rob Browning  <rlb@defaultvalue.org>

	* guile-ltdl.c: Remove custom realloc. (#define rpl_realloc
	realloc).  You can't define realloc like this unless you also
	define malloc.  This is a quick hack for now; we may want
	something cleaner later.
	(memcpy): coerce ptrs to (char *) before copying characters
	through them -- I can't recall for sure, but I believe this was
	causing an overrun error at times.
	(realloc): commented out -- as mentioned above, you can't define
	your own malloc unless you know enough about the malloc in use to
	be able to tell how big the src ptr is.  The disabled code
	incorrectly used the *destination* ptr to decide how much to copy.
	This sometimes results in out-of-bound accesses which cause
	segfaults.
	(tryall_dlopen_module): check to be sure (dirname_len > 0) before
	testing first character against '/'.
	(try_dlopen): check for feof(file) in read loop -- otherwise
	infloop?
	(scm_lt_dlopenext): remove unused variable file_found.

2002-10-04  Marius Vollmer  <mvo@zagadka.ping.de>

	* guile-ltdl.c: Renamed all exported functions and variables to have a
	"scm_lt_" prefix.
	(try_dlopen): Set newhandle to null when try_all_dlopen failed.
	(scm_lt_dlopenext): Reverse test of "file_not_found()".
	Previously, we would stop searching when the file wasn't found
	yet, while we should continue in that case.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-10-04 15:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 22:06 some rpm building questions Bo Forslund
2002-10-04  2:20 ` Bo Forslund
2002-10-04 11:56   ` Han-Wen Nienhuys
2002-10-04 12:30   ` Marius Vollmer
2002-10-04 13:08     ` rm
2002-10-04 15:48       ` Rob Browning [this message]
2002-10-08 21:27       ` Marius Vollmer
2002-10-04 16:04 ` Rob Browning

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8765wiryqo.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=bo.forslund@abc.se \
    --cc=guile-devel@gnu.org \
    --cc=mvo@zagadka.ping.de \
    /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).