unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: Damien Mattei <damien.mattei@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: compilation error on Apple M1
Date: Sun, 25 Dec 2022 23:40:56 -0800	[thread overview]
Message-ID: <CA+XASoUaQc99xR91o-O3UEe0TyWf_i49UjqLi9v_Z9NEg30E+Q@mail.gmail.com> (raw)
In-Reply-To: <CADEOadeDxcRx3Z4rPkqgr9BVoe3S_M0OJX3_szwODzi2ndTKBg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2550 bytes --]

Hi Damien,

This looks like a linking issue probably related to how things are
installed in your system, not with Guile itself. And the issue seems to be
with libiconv. Usually that comes with macOS itself and is located in
/usr/lib/libiconv.2.dylib.

Building Guile on M1 is definitely possible and works. I would suggest
using Homebrew which already has all Guile dependencies figured out.
Actually, I just recently added the Apple Silicon chip fix that Colin
mentions to Homebrew as well (
https://github.com/Homebrew/homebrew-core/pull/118698), because even if you
solve the issue you are currently getting you are going to run into the
next one (which is that you need to disable JIT which makes Guile very slow
unless you apply that fix).

Also, if you use Guile from Homebrew you will benefit from Guile Homebrew
which has all these packages ready to be used:
https://github.com/aconchillo/homebrew-guile/tree/master/Formula

Some people dislike Homebrew very much and refuse to install it, so I
totally understand if that's the case.

Best,

Aleix

On Sun, Dec 25, 2022 at 3:33 PM Damien Mattei <damien.mattei@gmail.com>
wrote:

> hello,
>
> on Apple M1 i have this error:
>
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include/sys/cdefs.h:215:48:
> note: expanded from macro '__deprecated_msg'
>         #define __deprecated_msg(_msg)
> __attribute__((__deprecated__(_msg)))
>                                                       ^
> 1 warning generated.
>   CC       libguile_3.0_la-net_db.lo
>   CC       libguile_3.0_la-socket.lo
>   CC       libguile_3.0_la-regex-posix.lo
>   CCLD     libguile-3.0.la
> Undefined symbols for architecture arm64:
>   "_iconv", referenced from:
>       _mem_cd_iconveh_internal in libgnu.a(striconveh.o)
>      (maybe you meant: _str_iconveh, _mem_iconveh ,
> _scm_port_acquire_iconv_descriptors , _iconveh_open , _iconveh_close ,
> _mem_cd_iconveh , _str_cd_iconveh , _scm_port_release_iconv_descriptors )
>   "_iconv_close", referenced from:
>       _iconveh_open in libgnu.a(striconveh.o)
>       _iconveh_close in libgnu.a(striconveh.o)
>   "_iconv_open", referenced from:
>       _iconveh_open in libgnu.a(striconveh.o)
> ld: symbol(s) not found for architecture arm64
> clang: error: linker command failed with exit code 1 (use -v to see
> invocation)
> make[3]: *** [libguile-3.0.la] Error 1
> make[2]: *** [all] Error 2
> make[1]: *** [all-recursive] Error 1
> make: *** [all] Error 2
>
> any idea about this arm64?
>
> regards,
> Damien
>

[-- Attachment #2: Type: text/html, Size: 4860 bytes --]

  parent reply	other threads:[~2022-12-26  7:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 23:32 compilation error on Apple M1 Damien Mattei
2022-12-25 23:58 ` Damien Mattei
2022-12-26  5:45   ` Colin Woodbury
2022-12-26  7:40 ` Aleix Conchillo Flaqué [this message]
2022-12-26 11:13   ` Damien Mattei
  -- strict thread matches above, loose matches on Subject: below --
2022-12-26 13:19 dsmich
     [not found] <2a517d79541e8c54b889639b3290b0eefd7dc22b@webmail>
2022-12-26 23:35 ` Damien Mattei

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=CA+XASoUaQc99xR91o-O3UEe0TyWf_i49UjqLi9v_Z9NEg30E+Q@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=damien.mattei@gmail.com \
    --cc=guile-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.
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).