public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glibc at sailorcire dot homelinux.com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug build/13893] New: cross compile issue with prefix: ld.so.conf not found
Date: Thu, 22 Mar 2012 22:54:00 -0000	[thread overview]
Message-ID: <bug-13893-131@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13893

             Bug #: 13893
           Summary: cross compile issue with prefix: ld.so.conf not found
           Product: glibc
           Version: 2.14
            Status: NEW
          Severity: minor
          Priority: P2
         Component: build
        AssignedTo: unassigned@sourceware.org
        ReportedBy: glibc@sailorcire.homelinux.com
                CC: carlos@systemhalted.org
    Classification: Unclassified


host/build/target: 
i696/2.14.1/arm

uname -a (modified hostname):
Linux computer.site.tld 2.6.37.6-0.11-desktop #1 SMP PREEMPT 2011-12-19
23:39:38 +0100 i686 i686 i386 GNU/Linux

configure options:
configure --target=arm-linux --prefix=/usr/local/arm-linux --enable-add-on

gcc -v:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i586-suse-linux/4.5/lto-wrapper
Target: i586-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.5
--enable-ssp --disable-libssp --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib --with-system-zlib
--enable-__cxa_atexit --enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --program-suffix=-4.5
--enable-linux-futex --without-system-libunwind --enable-gold
--with-plugin-ld=/usr/bin/gold --with-arch-32=i586 --with-tune=generic
--build=i586-suse-linux
Thread model: posix
gcc version 4.5.1 20101208 [gcc-4_5-branch revision 167585] (SUSE Linux) 

ld -v:
GNU ld (GNU Binutils; openSUSE 11.4) 2.21

How to replicate:

After configure I then run make, which works fine. When it gets to the make
install I see this error:

Can't open configuration file /usr/local/arm-linux/etc/ld.so.conf: No such file
or directory make[1]: Leaving directory


I was able to fix this by doing the following:

mkdir -p /usr/local/arm-linux/etc
touch /usr/local/arm-linux/etc/ld.so.conf

Then running configure, make, make install.

As a suggestion, in the configure script, if the prefix is passed in that a
check is performed for a ld.so.conf; if there is not then touch it.

If there is anything else I can provide, let me know.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2012-03-22 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 22:54 glibc at sailorcire dot homelinux.com [this message]
2012-03-22 23:21 ` [Bug build/13893] " glibc at sailorcire dot homelinux.com
2012-05-08 19:08 ` aj at suse dot de
2012-05-09  4:12 ` aj at suse dot de
2014-06-26 13:44 ` fweimer at redhat dot com

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

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

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

  git send-email \
    --in-reply-to=bug-13893-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).