| Summary: | ASTERISK-28293: New Build ast_expr2fz.o Will Not Link | ||
| Reporter: | Michel R. Vaillancourt (jkl5group) | Labels: | |
| Date Opened: | 2019-02-15 13:30:51.000-0600 | Date Closed: | 2020-01-14 11:13:45.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Addons/General |
| Versions: | 13.24.1 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | CentOS7 | Attachments: | |
| Description: | # make clean
# ./configure --libdir=/usr/lib64 --with-pjproject-bundled CFLAGS=-fPIC LDFLAGS=-fPIC ... configure: Package configured for: configure: OS type : linux-gnu configure: Host CPU : x86_64 configure: build-cpu:vendor:os: x86_64 : pc : linux-gnu : configure: host-cpu:vendor:os: x86_64 : pc : linux-gnu : # make all ... [LD] check_expr.o ast_expr2.o ast_expr2f.o strcompat.o threadstorage.o clicompat.o -> check_expr [CC] ast_expr2f.c -> ast_expr2fz.o [CC] ast_expr2.c -> ast_expr2z.o [LD] ast_expr2fz.o ast_expr2z.o -> check_expr2 /usr/bin/ld: ast_expr2fz.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: ast_expr2z.o: relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status make[1]: *** [check_expr2] Error 1 make: *** [utils] Error 2 | ||
| Comments: | By: Asterisk Team (asteriskteam) 2019-02-15 13:30:52.579-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: George Joseph (gjoseph) 2019-02-19 09:13:51.932-0600 Can't seem to reproduce this on my CentOS7 system, with or without the force of -fPIC. What versions of gcc, glibc and binutils are you running? By: Michel R. Vaillancourt (jkl5group) 2019-02-20 08:07:13.852-0600 gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) glibc-2.17 binutils-2.27 By: Joshua C. Colp (jcolp) 2019-02-25 09:31:56.547-0600 Is this a new source checkout, or are you using an existing one? Does "make distclean" alter things? Are you reusing an existing configuration? By: Michel R. Vaillancourt (jkl5group) 2019-03-08 07:10:58.805-0600 New source checkout. Was reusing a "known-good" DEP file from prior installs. "Make Distclean" did not correct the problem. 13.25.0 also produces this behavior. By: Michel R. Vaillancourt (jkl5group) 2019-03-08 07:11:36.544-0600 ((sorry for delay in reply, was out sick for a few days)) By: Michel R. Vaillancourt (jkl5group) 2019-03-08 07:57:29.882-0600 wiped the install directory, fresh DL of v16.2.1, 'make distclean' ... everything works fine. Going to stick with v16 since it is LTS. By: Benjamin Keith Ford (bford) 2019-03-12 14:05:28.355-0500 That's great that 16 is working for you, but very strange that 13 is not. If we are going to dig into this further, we would require further assistance from you, if you're willing, like trying to reproduce this on another machine with same environment if possible. By: Asterisk Team (asteriskteam) 2019-03-27 12:00:01.682-0500 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines | ||