ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "npic1 (Nat Pic1) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "npic1 (Nat Pic1)" <ruby-core@ml.ruby-lang.org>
Subject: [ruby-core:113195] [Ruby master Bug#19592] Unable to statically link a single extension in 3.2.x and >3.1.4
Date: Wed, 12 Apr 2023 13:48:08 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-19592.20230412134807.47060@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-19592.20230412134807.47060@ruby-lang.org

Issue #19592 has been reported by npic1 (Nat Pic1).

----------------------------------------
Bug #19592: Unable to statically link a single extension in 3.2.x and >3.1.4
https://bugs.ruby-lang.org/issues/19592

* Author: npic1 (Nat Pic1)
* Status: Open
* Priority: Normal
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN
----------------------------------------
Hi,
I need to statically link a single extension (not all of them) by adding it to ext/Setup.
This worked until version 3.1.4 and 3.2.x. 

It appears that this change broke it: 
[https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/790cf4b6d0475614afb127b416e87cfa39044d67](https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/790cf4b6d0475614afb127b416e87cfa39044d67)
[https://github.com/ruby/ruby/pull/6756](https://github.com/ruby/ruby/pull/6756).

I have attached a script to reproduce the issue.

When running the script, `ldd` fails with:
```
ext/extinit.o: in function `Init_ext':
extinit.c:(.text+0x10): undefined reference to `ruby_init_ext'
```



---Files--------------------------------
ruby_static_test.sh (1.57 KB)


-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/

       reply	other threads:[~2023-04-12 13:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 13:48 npic1 (Nat Pic1) via ruby-core [this message]
2023-04-14  7:37 ` [ruby-core:113247] [Ruby master Bug#19592] Unable to statically link a single extension in 3.2.x and >=3.1.4 npic1 (Nat Pic1) via ruby-core
2024-04-07  5:41 ` [ruby-core:117450] " nagachika (Tomoyuki Chikanaga) via ruby-core

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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

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

  git send-email \
    --in-reply-to=redmine.issue-19592.20230412134807.47060@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=ruby-core@ml.ruby-lang.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).