[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [solaris] "as" foul...

From: Gabor Greif <ggreif_at_lucent.com>
Date: 2002-05-11 12:43:53 CEST

Albert Chin wrote:
> On Fri, May 10, 2002 at 07:28:52PM +0200, Gabor Greif wrote:
> > I attempted a build on sparc-solaris 2.7 today starting with the 0.12 tarball (subversion-r1868).
> >
> > When assembling apr/atomic/solaris_sparc/apr_atomic_sparc.S using
> >
> > as -K pic -P -D_ASM -D__STDC__=0 -xarch=v8plus -o apr_atomic_sparc.lo apr_atomic_sparc.S
> >
> > I get
> >
> > Assembler messages:
> > Warning: Unrecognized option following -K
> > as: unrecognized option `-_ASM'
> What about "-Kpic" or "-KPIC"? From 'as --help':
> -K warn when differences altered for long displacements
> -KPIC generate PIC

Well, the line came from the makefile, literally. In the meantime I can think of a possible cause. I started out with gnu as from binutils 2.8.1 and on the very same error I upgraded to binutils
2.11.2. I still got the error and in my desperation I wrote the mail. Then I rerun ./configure and this time it passed this point, "make" finished without errors. "make install" still fails on the
toplevel targets {install-headers install-lib install-config} with this:

/tmp/subversion-r1868/neon/install-sh -c -d /tmp/subversion-r1868/include/neon
mksh: Fatal error: Cannot load command `/tmp/subversion-r1868/neon/install-sh': Bad file number
Current working directory /tmp/subversion-r1868/neon
*** Error code 1
make: Fatal error: Command failed for target `install-headers'
Current working directory /tmp/subversion-r1868/neon
*** Error code 1
make: Fatal error: Command failed for target `external-install'

An attempt to run install-sh by hand:
/tmp/subversion-r1868/neon/install-sh -c -d /tmp/subversion-r1868/include/neon

Fails with:
/tmp/subversion-r1868/neon/install-sh: Permission denied.

No wonder, the permissions are "-rw-r--r--"

chmod u+x /tmp/subversion-r1868/neon/install-sh

Now at least it executes.

"make install" works too in this regard. (See end of message for `install-info' problems, maybe configure should check for "makeinfo"?)

Either this way or commenting out those targets, I at least get a running svn binary.

Then I seem to have trouble coming thru the proxy (yes, I set up the proxy file):
bin/svn co http://svn.collab.net/repos/svn/trunk -d /tmp/svn

svn_error: #21091 : <RA layer request failed>
  OPTIONS request failed on /repos/svn/trunk

svn_error: #21091 : <RA layer request failed>
  OPTIONS of /repos/svn/trunk: could not connect to server

I wonder why "OPTIONS" is not mentioned in the FAQ...

> BTW, why are you using GNU as on Solaris 7? We've never had a problem
> with Solaris as on 7 and above.

Well, it shouldn't matter anyway, modulo bugs they should emit the same binary.

Thanks a lot, I hope my feedback helps to improve the installation process on sparc ;-)


> --
> albert chin (china@thewrittenword.com)

echo cannot run makeinfo -I `dirname doc/user/svn_for_cvs_users/svn_for_cvs_users.texi` -o doc/user/svn_for_cvs_users/svn_for_cvs_users.info doc/user/svn_for_cvs_users/svn_for_cvs_users.texi
cannot run makeinfo -I doc/user/svn_for_cvs_users -o doc/user/svn_for_cvs_users/svn_for_cvs_users.info doc/user/svn_for_cvs_users/svn_for_cvs_users.texi
/tmp/subversion-r1868/ac-helpers/install-sh -c -d /tmp/subversion-r1868/info
/tmp/subversion-r1868/ac-helpers/install-sh -c -m 644 ./doc/user/manual/svn-manual.info /tmp/subversion-r1868/info/svn-manual.info
/tmp/subversion-r1868/ac-helpers/install-sh -c -m 644 doc/user/svn_for_cvs_users/svn_for_cvs_users.info /tmp/subversion-r1868/info/svn_for_cvs_users.info
install: doc/user/svn_for_cvs_users/svn_for_cvs_users.info does not exist
*** Error code 1
make: Fatal error: Command failed for target `install-info'

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 11 12:45:01 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.