bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ***SPAM*** Re: trying to build gnumach.gz


From: Samuel Thibault
Subject: Re: ***SPAM*** Re: trying to build gnumach.gz
Date: Tue, 2 Aug 2011 00:15:03 +0200
User-agent: Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30)

Andrew Engelbrecht, le Mon 01 Aug 2011 18:07:13 -0400, a écrit :
> On Mon, 1 Aug 2011 23:56:03 +0200, Samuel Thibault wrote:
> >It should have been done at the end of ./configure (see the
> >configfrag.ac file): I'm getting
> >
> >config.status: linking i386/i386 to machine
> >config.status: linking i386/include/mach/i386 to mach/machine
> 
> Here's what I'm getting:
> 
> config.status: linking i386/i386 to machine
> config.status: linking ../gnumach/i386/include/mach/i386 to mach/machine
> config.status: linking ../gnumach/linux/src/include/asm-i386 to
> linux/src/include/asm
> config.status: linking ../gnumach/linux/dev/include/asm-i386 to
> linux/dev/include/asm
> 
> I'm guessing that the fact I'm building in a separate directory doesn't play
> nice with something.

Well, the Debian package does it too, but gets

config.status: linking ../i386/i386 to machine

It's odd that you get this output while the code is 

AC_CONFIG_LINKS([machine:$systype/$systype
                 mach/machine:$systype/include/mach/$systype])

i.e. $systype in both case. Could you perhaps check the content of the
configure script itself?

Samuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]