unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alexis Purslane <alexispurslane@pm.me>
Cc: emacs-devel@gnu.org
Subject: Re: Trying to build scratch/igc: cannot find MPS library
Date: Sun, 29 Dec 2024 18:06:16 +0200	[thread overview]
Message-ID: <86y0zypj7r.fsf@gnu.org> (raw)
In-Reply-To: <87bjwujy6k.fsf@pm.me> (emacs-devel@gnu.org)

> Date: Sun, 29 Dec 2024 15:39:54 +0000
> From:  Alexis Purslane via "Emacs development discussions." <emacs-devel@gnu.org>
> 
>     I'm trying to build the scratch/igc branch of Emacs in order to see if I
>     can help bug hunt, and I'm running into a problem. I apologize if
>     this turns out to be a dumb mistake, I don't often build things from
>     source.
> 
>     I'm following README-IGC's instructions to build the debug version
>     of MPS from source to the letter, except I've decided to place
>     mps-artifacts in the mps directory, and the mps directory inside my
>     emacs source directory, in order to avoid cluttering up my home
>     directory. So the commands I'm running are:
> 
>         $ # starting in the emacs directory, /home/alexispurslane/Development/scratch/emacs/
>         $ git clone https://github.com/Ravenbrook/mps.git
>         $ cd mps/code
>         $ gcc -O0 -g -DCONFIG_VAR_COOL -c mps.c -o mps-debug.o
>         $ ar rvs libmps-debug.a mps-debug.o
>         $ cp libmps-debug.a ../mps-artifacts
>         $ cd ../..
>         $ ./configure CPPFLAGS=-I/home/alexispurslane/Development/scratch/emacs/mps/mps-artifacts LDFLAGS=-I/home/alexispurslane/Development/scratch/emacs/mps/mps-artifacts --with-cairo --with-dbus --with-gif --with-gpm=no --with-harfbuzz --with-jpeg --with-modules --with-native-compilation=aot --with-png --with-rsvg --with-sqlite3 --with-tiff --with-tree-sitter --with-webp --with-x-toolkit=gtk3 --with-xinput2 --with-xpm --with-mps=debug --enable-checking=igc_debug
> 
>     When I try to do this, configure reports this error:
> 
>         checking for mps.h... yes
>         checking for mps_arena_create in -lmps... no
>         configure: error: The MPS library libmps is missing
> 
>     This seems odd to me not only because I'm providing it with a
>     directory that has what it's looking for, but that it appears the
>     CPPFLAGS(?) are working, since it can find mps.h, but not the
>     LDFLAGS.

Your LDFLAGS are incorrect: the option letter is -L, not -I.


>     P.S. There's a type in the README-IGC debug build instructions: it
>     says `mpc.c' instead of `mps.c' in the GCC command.

Thanks, fixed.



      reply	other threads:[~2024-12-29 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-29 15:39 Trying to build scratch/igc: cannot find MPS library Alexis Purslane via Emacs development discussions.
2024-12-29 16:06 ` Eli Zaretskii [this message]

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/emacs/

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

  git send-email \
    --in-reply-to=86y0zypj7r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=alexispurslane@pm.me \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).