This is the mail archive of the
cygwin-developers
mailing list for the Cygwin project.
Re: Latest 64 bit test stuff on sourceware
On Feb 21 12:56, Andy Koppe wrote:
> On 21 February 2013 10:58, Corinna Vinschen wrote:
> > The toolchain I created on Linux is not using --with-sysroot. All
> > target files are installed into $(exec_prefix)/$(target_alias) and
> > expected there by the compiler.
>
> I see. Is it generally reasonable to assume that if `$(CC)
> -print-sysroot` comes back empty, the library directory can be found
> at ../$(target)/lib relative to the target-gcc's location?
Erm... I guess you have to ask a toolchain guy there :-}
> > For testing I moved away
> > /ext/redhat/x86_64-pc-cygwin/x86_64-pc-cygwin/lib/w32api/libkernel32.a
> > and I got
> >
> > $ x86_64-pc-cygwin-gcc -g test.c
> > /ext/redhat/x86_64-pc-cygwin/bin/../lib/gcc/x86_64-pc-cygwin/4.8.0/../../../../x86_64-pc-cygwin/bin/ld: cannot find -lkernel32
> > collect2: error: ld returned 1 exit status
> >
> > If I move libkernel32.a back, linking works.
>
> Hmm. I tried putting the toolchain into the same location you have it
> in, but that didn't make a difference. -v output at the end of this
> mail. A couple of things I noticed there:
> - It says 'ignoring nonexistent directory "../../include/w32api"'
> - The collect2 command line contains the main lib directory
> ('L/ext/redhat/x86_64-pc-cygwin/bin/../lib/gcc/x86_64-pc-cygwin/4.8.0/../../../../x86_64-pc-cygwin/lib/../lib',
> aka /ext/redhat/x86_64-pc-cygwin/x86_64-pc-cygwin/lib), but not its
> w32api subdirectory.
Oh, hmm. Maybe the toolchain is *not* what I'm using. I just remember
that we had a problem with the default library path last week or so.
There's a chance I tweaked my toolchain locally but didn't upload the
changes. I'm just going to upload a new
binary-toolchain-x86_64-pc-linux-x-x86_64-pc-cygwin-20130221.tar.xz
Hopefully that problem heals itself by using that toolchain.
> Btw, I'm using openSuse 12.2.
Shouldn't matter at all.
> >> Is there a better approach for dealing with that, other than requiring
> >> the library directory to be passed into the makefile?
> >
> > Where is the non w32api libuuid.a coming from? I don't have such a
> > file.
>
> On Cygwin proper it comes from the libuuid-devel package. Previously I
> got around this by explicitly linking in /usr/lib/w32api/libuuid.a,
> but obviously that's no good for cross-compiling. I'd like to address
> this "properly" rather than rely on lib/libuuid.a not appearing in
> cross build setups.
What about `$(CC) -print-file-name=w32api/libuuid.a'?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat