Philip Martin wrote:
> Raman Gupta <email@example.com> writes:
>> I am building Subversion 1.4.0 on Solaris 2.6 SPARC... I am having a
>> problem related to the build using /usr/ccs/bin/ld instead of the GNU
>> ld in /usr/local/bin.
>> In the past, e.g. Subersion 1.3.x, specifying the PATH was sufficient
>> for the build to use the GNU toolset:
>> export PATH=/usr/local/bin:$PATH
>> However, with 1.4.0, I have found that configure persists on using
>> /usr/ccs/bin/ld instead of /usr/local/bin/ld despite the PATH ordering
>> (which eventually results in a build error).
>> Therefore, I also defined:
>> export LD=/usr/local/bin/ld
>> This above is sufficient for configure to find the GNU ld, but when
>> make is run, the build again attempts to use /usr/ccs/bin/ld (but at
>> least the error occurs right away instead of 5 minutes into the build!)
>> I finally got 1.4.0 to build by renaming /usr/ccs/bin/ld to
>> /usr/ccs/bin/ld.old, but IMHO, I shouldn't have to do this. Should I?
> When asking for help it's a good idea to show the exact configure
> command and error messages.
Actually, since I did get subversion to build (by moving
/usr/ccs/bin/ld) I wasn't asking for help so much as wondering why the
behavior was different between 1.3.x and 1.4.0. Anyway, here are my
export LIBS="-L/usr/local/lib/gcc/sparc-sun-solaris2.6/3.4.1 -lgcc"
$CONFIG_SHELL ./configure CONFIG_SHELL=$CONFIG_SHELL \
--without-apache --without-berkeley-db --with-python=/usr/local/bin/python \
--with-perl5=/usr/local/bin/perl --with-apr=/usr/local/apr/bin/apr-config \
> It's possible your gcc has been built to use /usr/ccs/bin/ld, what
> does the command 'gcc --print-prog-name ld' show?
# gcc --print-prog-name ld
Looks like that is the problem -- Hmm, maybe my 1.3.x builds used the
Solaris linker too, but the build succeeded with the Solaris linker, but
for some reason the 1.4.0 build requires the GNU linker.
> If your gcc has been built to use the Solaris linker then perhaps you
> can configure Subversion using --without-gnu-ld, but I have no idea
> whether this works. Alternatively you might be able to get GNU ld by
> using COMPILER_PATH=/usr/local/bin, or by adding '-B /usr/local/bin'
> to CFLAGS or LDFLAGS, but again I have no idea whether that works.
> You may need to rebuild gcc to use GNU ld.
Next time I'll try one or more of the above.
> Perhaps your shell init scripts are resetting PATH
I checked that, but that is not the problem.
Thanks for your help/suggestions.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Sep 12 18:48:21 2006