Displaying 8 results from an estimated 8 matches for "hardcode_libdir_flag_spec".
2009 Aug 03
1
use gnulib, and begin to pass its "make syntax-check" tests
...wl='-Wl,'
- ;;
- sunos4*)
- wl='-Qoption ld '
- ;;
- sysv4 | sysv4.2uw2* | sysv4.3* | sysv5*)
- wl='-Wl,'
- ;;
- sysv4*MP*)
- ;;
- uts4*)
- ;;
- esac
-fi
-
-# Code taken from libtool.m4's AC_LIBTOOL_PROG_LD_SHLIBS.
-
-hardcode_libdir_flag_spec=
-hardcode_libdir_separator=
-hardcode_direct=no
-hardcode_minus_L=no
-
-case "$host_os" in
- cygwin* | mingw* | pw32*)
- # FIXME: the MSVC++ port hasn't been tested in a loooong time
- # When not using gcc, we currently assume that we are using
- # Microsoft Visual C++.
-...
2009 Nov 17
1
[LLVMdev] rpaths in llvm binaries
...do not have cmake installed - and when packaging for NetBSD (IIRC) you need to explicitly tell it that cmake is used, which I haven't done - so I'd have to answer "no".
I do see LIBS="$LIBS -L${llvm_cv_oppath} -Wl,-rpath,${llvm_cv_oppath}" in autoconf/configure.ac, and hardcode_libdir_flag_spec'${wl}-rpath ${wl}$libdir' and hardcode_libdir_flag_spec_ld='-rpath $libdir' in configure, though. Do these need to be there?
Tim
2015 May 17
1
fs_api_module_register
Marcus,
Thanks for the spec file.
I'm fairly new to creating RPM's and I just found out that the issue is
taking place during the 'make check' portion of the spec file. I'm not
sure what 'make check' does after having googled it, although, I think
it checks for run-time errors. Any hints?
Eric
On 5/16/2015 12:52 PM, Marcus Rueckert wrote:
> On 2015-05-16 11:52:55
2009 Nov 16
0
[LLVMdev] rpaths in llvm binaries
"Larson, Timothy E." <TELarson at west.com> writes:
> Hello LLVM devs,
>
> I am trying to package llvm for NetBSD. The package checker scripts
> are complaining about bad rpaths in the binaries. I see that they are
> relative to the build directory. I have no idea why that would be.
> Can you explain?
Are you using cmake for building LLVM?
If the answer is
2009 Nov 16
2
[LLVMdev] rpaths in llvm binaries
Hello LLVM devs,
I am trying to package llvm for NetBSD. The package checker scripts are complaining about bad rpaths in the binaries. I see that they are relative to the build directory. I have no idea why that would be. Can you explain?
If I build as myself, for testing (e.g.):
$ readelf -d ~/downloads/llvm-2.6/Release/bin/llvm-ar
Dynamic section at offset 0x15af28 contains 25 entries:
2016 Oct 21
0
v2.2.26 release candidate released
...t; Aki
I had an error (below) during make check as well on CentOS 5 (no issues
with 6 and 7) and commented the following 'sed' commands (Removing Rpath
from this page: https://fedoraproject.org/wiki/Packaging:Guidelines ) in
the spec file resulting in a successful build:
#sed -i 's|^hardcode_libdir_flag_spec=.*|hardcode_libdir_flag_spec=""|g'
libtool
#sed -i 's|^runpath_var=LD_RUN_PATH|runpath_var=DIE_RPATH_DIE|g' libtool
<make check error>
make[3]: Leaving directory
`/usr/src/redhat/BUILD/dovecot-2.2.26.rc1/src/lib-storage'
for bin in test-mail-search-args-imap test...
2016 Oct 21
3
v2.2.26 release candidate released
> On October 21, 2016 at 6:27 AM Tamsy <dovecot-list at mohtex.net> wrote:
>
>
> Timo Sirainen wrote on 20.10.2016 04:01:
> > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz
> > http://dovecot.org/releases/2.2/rc/dovecot-2.2.26.rc1.tar.gz.sig
> >
> > There are quite a lot of changes since v2.2.25. Please try out this RC so we can get a good
2005 May 11
5
Implementing R on IBM p690 cluster Jump
Dear All,
we're trying to implement R on the IBM p690 cluster "Jump" at the
research centre in J?lich, Germany (c.f.
http://www.fz-juelich.de/nic/Supercomputer/computer-e.html)
using the most recent version of R (2.1.0) and precisly following the
installation instructions.
After ./configure we get the final message:
----------------
R is now configured for powerpc-ibm-aix5.2.0.0