From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Ryan Raymond <rjraymond@oakland.edu>
Cc: Guile User <guile-user@gnu.org>, guile-devel@gnu.org
Subject: Re: Changes to Guile not effecting built binary
Date: Thu, 21 Mar 2024 17:45:49 +0100 [thread overview]
Message-ID: <871q831qha.fsf@web.de> (raw)
In-Reply-To: <CAGvJ-HRJUYadPUbf-OubE-rm5vG=0Lr+hH5dQrXpHL=x2uejCg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Ryan Raymond <rjraymond@oakland.edu> writes:
> For example, I modified "parse-http-method" and completely removed all error throwing capabilities but I am still getting an error thrown from
> within that function.
> (bad-request "Invalid method: ~a" (substring str start end))
>
> I am assuming that the modules are not being rebuilt. My workflow is as follows:
> 1. Modify the source code
> 2. ./configure
> 3. make
> 4. make install
>
> Can anyone point out a mistake I might be making?
A shot into the blue would be that some dependencies aren’t marked
correctly in the Makefile so some file is not being rebuilt and includes
the old version of the function via a macro.
Does it also happen when you add a `make clean` step?
Does it happen when you directly run meta/guile instead of installing?
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
next prev parent reply other threads:[~2024-03-21 16:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 15:34 Changes to Guile not effecting built binary Ryan Raymond
2024-03-21 16:45 ` Dr. Arne Babenhauserheide [this message]
2024-03-21 17:17 ` Ryan Raymond
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=871q831qha.fsf@web.de \
--to=arne_bab@web.de \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=rjraymond@oakland.edu \
/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).