Date: Tue, 6 Apr 2010 13:41:17 +0200 From: Christian Weisgerber <naddy@freebsd.org> To: Peter Jeremy <peterjeremy@acm.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: Trailing slashes on file names Message-ID: <20100406114117.GA9339@lorvorc.mips.inka.de> In-Reply-To: <20100406061213.GB46137@server.vk2pj.dyndns.org> References: <hpd6qm$2hbg$1@lorvorc.mips.inka.de> <20100406061213.GB46137@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Jeremy: > Do you have access to the config.log output? No, I have only been looking at the pointyhat logs, since I don't have access to a FreeBSD/sparc64 machine. Is there one available to committers? There is no mention on http://www.freebsd.org/internal/machines.html > That may provide more insight into what is going wrong. I have > in the past seen configure get very confused about how to compile > test programs and blunder on regardless, reporting nonsense. The configure script doesn't get confused in general. If you diff its output between amd64/i386 and sparc64, you see that it specifically differs about whether a number of system calls accept a trailing slash to a file name: chown, lstat, unlink, open, stat. Hundreds of other tests are fine. Anybody with access to a sparc64 can check what make configure for ports/archivers/gcpio reports for their system. I am concerned that linimon@ may have sprinkled BROKEN all over the ports tree based on a bogus build run. -- Christian "naddy" Weisgerber naddy@mips.inka.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100406114117.GA9339>