From: Doru Carastan <doru.carastan@mvista.com>
To: cygwin@cygwin.com
Subject: gcc-3.2: gcc driver doesn't pick up crt0.a from /usr/lib
Date: Tue, 30 Sep 2003 02:06:00 -0000 [thread overview]
Message-ID: <3F78DC42.1050303@mvista.com> (raw)
Hello,
I am facing a gcc-3.2 configuration problem and I would like to ask your
opinion about it. I have built an i686-pc-cygwin gcc compiler on Linux
using a gcc-3.2 i686-pc-linux-gnu to i686-pc-cygwin cross compiler I
have built and installed in $HOME/cygwin.
r=$HOME/cygwin
i=$HOME/install
# Build, host, target
b=`$r/src/$binutils/config.guess`
h=i686-pc-cygwin
t=i686-pc-cygwin
#
mkdir -p "$r/src/build/$gcc" && \
cd "$r/src/build/$gcc" && \
"$r/src/$gcc/configure" --build=$b --host=$h --target=$t \
--prefix=/usr --includedir=/nonexistent/include \
--enable-languages=c,c++ \
--enable-threads=posix \
--with-system-zlib \
--enable-nls \
--without-included-gettext \
--disable-version-specific-runtime-libs \
--enable-shared \
--enable-haifa \
--enable-interpreter && \
make all && \
make install prefix="$i/$gcc/usr" && \
cd "$i/$gcc" && tar -cf "$r/$gcc.tar" *
At build time I have $HOME/i686-pc-cygwin/lib stuffed with the
i686-pc-cygwin lib files including crt0.o. It builds fine, but when I
install it on Cygwin it can't find crt0.o. /usr/lib.crt0.o is available
but gcc it doesn't even look in /usr/lib:
$ gcc -print-search-dirs
install: /usr/lib/gcc-lib/i686-pc-cygwin/3.2/
programs:
=/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/:/usr/lib/gcc/i686-pc-cygwin/3.2/:/usr/lib/gcc/i686-pc-cygwin/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/
libraries:
=/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/lib/
The stock Cygwin gcc and also the native Linux one have a libraries line
like:
install: /usr/lib/gcc-lib/i686-pc-cygwin/3.2/
programs:
=/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/:/usr/lib/gcc/i686-pc-cygwin/3.2/:/usr/lib/gcc/i686-pc-cygwin/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/bin/
libraries:
=/usr/lib/gcc-lib/i686-pc-cygwin/3.2/:/usr/lib/gcc/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/lib/i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../../i686-pc-cygwin/lib/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../i686-pc-cygwin/3.2/:/usr/lib/gcc-lib/i686-pc-cygwin/3.2/../../../:/lib/i686-pc-cygwin/3.2/:/lib/:/usr/lib/i686-pc-cygwin/3.2/:/usr/lib/
Any ideas?
Thank you,
--
Doru Carastan
*\\\///* WinHost Contractor
||\\//|| 408-992-4497
|||\/||| doru.carastan@mvista.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2003-09-30 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 2:06 Doru Carastan [this message]
2003-09-30 17:51 Doru Carastan
2003-09-30 18:44 ` Christopher Faylor
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=3F78DC42.1050303@mvista.com \
--to=doru.carastan@mvista.com \
--cc=cygwin@cygwin.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).