From: reskumar@in.ibm.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95331] [Ruby master Bug#16179] ruby binaries generate "already initialized constant" warnings on AIX 6.1
Date: Tue, 15 Oct 2019 12:17:40 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-82040.20191015121739.694d414de0cd9da2@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16179.20190925023303@ruby-lang.org
Issue #16179 has been updated by Reshma (Reshma Kumar).
64bit
-----
./configure \
--host=powerpc-ibm-aix6.1.0.0 --target=powerpc-ibm-aix6.1.0.0 --build=powerpc-ibm-aix6.1.0.0 \
--prefix=/opt/freeware \
--libdir=/opt/freeware/lib64 \
--libexecdir=/opt/freeware/lib64 \
--disable-rpath \
--enable-pthread \
--enable-shared \
--disable-static
32bit
-----
./configure \
--host=powerpc-ibm-aix6.1.0.0 --target=powerpc-ibm-aix6.1.0.0 --build=powerpc-ibm-aix6.1.0.0 \
--prefix=/opt/freeware \
--libdir=/opt/freeware/lib \
--libexecdir=/opt/freeware/lib \
--disable-rpath \
--enable-pthread \
--enable-shared \
--disable-static
----------------------------------------
Bug #16179: ruby binaries generate "already initialized constant" warnings on AIX 6.1
https://bugs.ruby-lang.org/issues/16179#change-82040
* Author: Reshma (Reshma Kumar)
* Status: Feedback
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: 2.6.3
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
We are building ruby 2.6.3(both 32 and 64bit) on AIX 6.1.
The build options used for 64bit build are:-
```
export LDFLAGS="-L/opt/freeware/lib64 -L/opt/freeware/lib -Wl,-blibpath:/opt/freeware/lib64:/usr/lib:/lib"
```
and for 32bit build are:-
```
export LDFLAGS="-L/opt/freeware/lib -Wl,-blibpath:/opt/freeware/lib:/usr/lib:/lib -Wl,-bmaxdata:0x80000000"
```
After successful build and installation of the package, 64bit and 32bit libraries are installed in /opt/freeware/lib64 and /opt/freeware/lib respectively. There are ruby scripts which are shipped in both /opt/freeware/lib and /opt/freeware/lib64.
Execution of irb(both 64bit and 32bit) generates warnings as mentioned below.
```
# irb
/opt/freeware/lib/ruby/2.6.0/uri/common.rb:17: warning: already initialized constant URI::REGEXP
/opt/freeware/lib64/ruby/2.6.0/uri/common.rb:17: warning: previous definition of REGEXP was here
/opt/freeware/lib/ruby/2.6.0/uri/common.rb:18: warning: already initialized constant URI::Parser
/opt/freeware/lib64/ruby/2.6.0/uri/common.rb:18: warning: previous definition of Parser was here
```
Any ideas why this could be happening?
---Files--------------------------------
ruby_output.log.docx (13.2 KB)
--
https://bugs.ruby-lang.org/
next prev parent reply other threads:[~2019-10-15 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16179.20190925023303@ruby-lang.org>
2019-09-25 2:33 ` [ruby-core:95072] [Ruby master Bug#16179] ruby binaries generate "already initialized constant" warnings reskumar
2019-09-25 7:14 ` [ruby-core:95078] " nobu
2019-09-26 6:59 ` [ruby-core:95097] " reskumar
2019-10-15 0:16 ` [ruby-core:95321] [Ruby master Bug#16179] ruby binaries generate "already initialized constant" warnings on AIX 6.1 merch-redmine
2019-10-15 12:17 ` reskumar [this message]
2019-10-15 14:47 ` [ruby-core:95335] " merch-redmine
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.journal-82040.20191015121739.694d414de0cd9da2@ruby-lang.org \
--to=ruby-core@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).