similar to: [Bug 2030] New: build of 6.0p1 fails @ "/usr/bin/ld: unrecognized option '-Wl,-rpath,/usr/local/ssl/lib64"

Hello list, I'm trying to compile a php4 package for centos5 and I'm stumbling across some "oddity" with the symbolic links of at least one library. But it's not a php4 problem, so read on. The package 'js' gives the library /usr/lib64/libjs.so.1 but shouldn't there be a link from /usr/lib64/libjs.so to /usr/lib64/libjs.so.1? Otherwise my compiler call %

Also what exact distro and version are you having the problem on and what version of ld does it have? Mine is $ ld --version GNU ld version 2.29.1-23.fc28 -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.

On 8 June 2018 at 12:09, PGNet Dev <pgnet.dev at gmail.com> wrote: [...] > /usr/bin/ld -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect2.o mux.o -L. -Lopenbsd-compat/ -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -fstack-protector-strong -pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv > /usr/bin/ld: unrecognized option

hi On 6/7/18 4:03 PM, Darren Tucker wrote: > On 8 June 2018 at 07:09, PGNet Dev <pgnet.dev at gmail.com> wrote: >> Verifying a report I just got pinged about, building vanilla openssh 7.7p1 on linux configures ok, but fails build around 'retpoline' > [...] >> Should the retpoline flag be getting added? If so, what's needed to make LD happy with it? > >

On 6/7/18 8:37 PM, Darren Tucker wrote: > On 8 June 2018 at 12:21, Darren Tucker <dtucker at dtucker.net> wrote: >> On 8 June 2018 at 12:09, PGNet Dev <pgnet.dev at gmail.com> wrote: >> [...] >>> /usr/bin/ld -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect2.o mux.o -L. -Lopenbsd-compat/ -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack

One difference I notice is that in your failing example you are invoking /usr/bin/ld directly to link: /usr/bin/ld -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect2.o mux.o -L. -Lopenbsd-compat/ -Wl,-z,retpolineplt -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -fstack-protector-strong -pie -lssh -lopenbsd-compat -lutil -lz -lcrypt -lresolv whereas my example is

On 8 June 2018 at 10:52, PGNet Dev <pgnet.dev at gmail.com> wrote: [...] > So, there's a problem for OpenSSH build with spec'ing LD=/usr/bin/ld ? in this particular case, apparently yes. not generally, though. [...] > What's *intended* re: openssh? Support for LD=ld or only =gcc, or undef'd ? Well the intent is you should be able to set CC and LD to whatever you

On 8 June 2018 at 11:21, PGNet Dev <pgnet.dev at gmail.com> wrote: > fyi > > add'l -- and looks unrelated -- issue > /usr/include/pthread.h:251:12: note: previous declaration of ?pthread_join? was here > extern int pthread_join (pthread_t __th, void **__thread_return); What included pthread.h? That's explicitly not supported by sshd: $ grep THREAD

On Thu, Jun 07, 2018 at 06:14:42PM -0700, PGNet Dev wrote: > On 6/7/18 6:08 PM, Darren Tucker wrote: > > Well the intent is you should be able to set CC and LD to whatever you > > want as long as they work. In this case, the OSSH_CHECK_LDFLAG_LINK > > test invokes autoconf's AC_LINK_IFELSE with uses CC not LD. I'm not > > sure what to do about it yet though. I

Verifying a report I just got pinged about, building vanilla openssh 7.7p1 on linux configures ok, but fails build around 'retpoline' I've started looking through recent reports; haven't _yet_ found anything similar. While I continue, is any of the following familiar/expected? Either known bug/issue or env conflict? The current env includes supposedly retpoline-ready GCC 8.1.1,

Kasper, I haven?t checked in depth, so just to clarify: you *are* setting CXX11=g++ so it is doing what you asked it to. Since the settings are inherited upwards, this implies that you are setting both CXX14 and CXX17 to g++. So I?m not quite sure I understand your concern. Cheers, Simon > On Sep 3, 2019, at 9:02 PM, Kasper Daniel Hansen <kasperdanielhansen at gmail.com> wrote: >

I am trying to compile R under a new setup, and frankly, I have had a lot of problems, but I think the stuff below points to a possible bug in R's (custom) configure checks for C++11/14/17, but not for C++98. This is a report about R from the R-3-6 branch, with a svn checkout from today, revision r77135. In my case the compiler name is x86_64-conda_cos6-linux-gnu-g++, not g++. I denote this

Hi. My system image is built on amd64 using Gentoo catalyst, and my target is x86. This works really well. However, OpenSSH configure adds -Wl,-rpath -Wl,/usr/lib to LIBS during build, which then causes a problem when trying to run sftp. (sftp has been linked with libedit, and /usr/lib/libedit.so exists but is a linker script that points to /lib/libedit.so. This linker script confuses ld.so

Hello everyone... This is my FIRST time... I am using GCC 4.3.5 on AIX 5.3... I compiled with openssh but got the error messages. Here is: gcc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o mux.o roaming_common.o roaming_client.o -L. -Lopenbsd-compat/ -L/usr/local/ssl/lib -L/usr/local/lib -Wl,-blibpath:/usr/lib:/lib -lssh -lopenbsd-compat -lcrypto -lz

Previous version compiled successfully was 5.5p1. Now compiling 5.8p1 on the same machine "AIX 5.3 TL12 SP2" via GNU make with gcc 4.2.0 - got an error, can someone help with this? gcc -o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o sshconnect1.o sshconnect2.o mux.o roaming_common.o roaming_client.o -L. -Lopenbsd-compat/ -L/usr/local/lib -Wl,-blibpath:/usr/lib:/lib:

So results of testing ... Conditional caveats: 1) current snapshot will not build against native openssl on any system with openssl version <0.9.8f (i.e RHEL <=6.4) ... requiring alternate openssl installs . 2) openssl 1.0.1i on RHEL 4 and lower (gcc 2/3) only builds and tests cleanly static libssl.a and the current patched snapshot builds and tests to completion against it just fine

Hi, This is just a quick note that I receive effectively the same error when doing an amd64 build. A workaround is to install the binary package libxenstore3.0 but of course the source build should not require an external install of one of the packages that it builds. James

Source: xen Version: 4.3.0-1 Severity: serious Justification: FTBFS Hi New uploaded xen 4.3.0-1 FTBFS, see [1] for build log for i386. [1] https://buildd.debian.org/status/fetch.php?pkg=xen&arch=i386&ver=4.3.0-1&stamp=1378426577 Regards, Salvatore

Hello List, I'm trying to get libvirt to work on slackware64-current (slackware64-14.2 beta) and while it compiles just fine, it refuses to run because of an undefined symbol: 2016-03-01 20:09:26.822+0000: 27849: error : virDriverLoadModule:73 : failed to load module /usr/lib64/libvirt/connection-driver/libvirt_driver_storage.so /usr/lib64/../lib64/libfl.so.2: undefined symbol: yylex

For people reading this: I was installing bzip2 by hand. Two things to bear in mind (1) it only installs a shared library if you use a special Makefile (this is clearly stated in the installation docs) and (2) I had to symlink libbz2.so.1 to libbz2.so.1.0.6 (the included libbz2.so.1.0 was not being picked up). Best, Kasper On Fri, Mar 27, 2015 at 11:19 AM, Kasper Daniel Hansen <