You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Nico Kadel-Garcia <nk...@comcast.net> on 2006/06/06 21:35:34 UTC
Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in issuetracker)
----- Original Message -----
From: "David Summers" <da...@summersoft.fay.ar.us>
To: "Toby Johnson" <to...@etjohnson.us>
Cc: "David James" <dj...@collab.net>; "Nico Kadel-Garcia"
<nk...@comcast.net>; "dev" <de...@subversion.tigris.org>
Sent: Tuesday, June 06, 2006 3:57 PM
Subject: Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in
issuetracker)
>
> On Tue, 6 Jun 2006, Toby Johnson wrote:
>
>> Marcus Rueckert wrote:
>>> On 2006-06-06 10:56:19 -0400, Toby Johnson wrote:
>>>
>>>> Issue 2. The "chrpath" call failed for me:
>>>>
>>>> --- 8< ----- snip ----- >8 ---
>>>> + chrpath -r /usr/lib64
>>>> /home/toby/rpms/tmp/subversion-1.5.0-19957/usr/lib64/httpd/modules/mod_authz_svn.so
>>>> /home/toby/rpms/tmp/subversion-1.5.0-19957/usr/lib64/httpd/modules/mod_authz_svn.so:
>>>> no rpath or runpath tag found.
>>>> error: Bad exit status from /home/toby/rpms/tmp/rpm-tmp.51994
>>>> (%install)
>>>>
>>>>
>>> running chrpath inside the build process sounds a bit scary.
>>>
>>>
>> That was my first reaction as well... if the library can't be found
>> during the build, that sounds like a config problem. I'm pretty sure that
>> the chrpath build-time dependency is a recent addition (in 1.3.1 I
>> think); David, do you remember why this was needed?
>>
>
> I've been trying for a year or so to figure out why people with NFS and
> NIS were having error/warning messages printed out in their
> /var/log/messages with a path showing MY build environment home directory
> and saying it couldn't find the libraries in that path.
>
> I finally figured out a few months ago that it was the -rpath during the
> build. I tried multiple ways of setting it during the build and couldn't
> get it to change. I found out about the chrpath command and it took me
> all of 5 minutes to try it out and fix the problem. If there is a better
> way, I'm all ears; I've spent a lot of time on the problem over the last
> year or so and this was the only way I could figure out to fix the
> problem.
Take a look at the Fedora Core 5 SRPM and .spec file for subversion-1.3.1.
It does some similar things, but not as part of the .spec file. Instead, the
rpath option is moved out of the "LINK" command, and into a "LINK_LIBS"
command, and that is called only when linking libraries, not when linking
programs. This makes good sense to me and seems to help eliminate the RPM
build whackiness, and can be backported to other versons of RedHat or
Fedora.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in issuetracker)
Posted by Marcus Rueckert <da...@web.de>.
On 2006-06-06 19:45:19 -0400, Nico Kadel-Garcia wrote:
> >On 2006-06-06 17:35:34 -0400, Nico Kadel-Garcia wrote:
> >>Take a look at the Fedora Core 5 SRPM and .spec file for
> >>subversion-1.3.1.
> >>It does some similar things, but not as part of the .spec file. Instead,
> >>the rpath option is moved out of the "LINK" command, and into a
> >>"LINK_LIBS"
> >>command, and that is called only when linking libraries, not when linking
> >>programs. This makes good sense to me and seems to help eliminate the RPM
> >>build whackiness, and can be backported to other versons of RedHat or
> >>Fedora.
> >
> >are you sure the rpath issue is still valid? it doesnt looks like that
> >to me. i tested with 1.3.2.
>
> How did you test it
reading the build log. i still saw a few -L$BUILD_DIR but no params in
the cmdline for setting the rpath.
and i double checked with maxb. he stated that svn used the la files for
linking since quite some time already instead "-L../.... -lsomelib"
hope that helps
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in issuetracker)
Posted by Nico Kadel-Garcia <nk...@comcast.net>.
----- Original Message -----
From: "Marcus Rueckert" <da...@web.de>
To: "Nico Kadel-Garcia" <nk...@comcast.net>
Cc: "Toby Johnson" <to...@etjohnson.us>; "David Summers"
<da...@summersoft.fay.ar.us>; "David James" <dj...@collab.net>; "dev"
<de...@subversion.tigris.org>
Sent: Tuesday, June 06, 2006 6:12 PM
Subject: Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in
issuetracker)
> On 2006-06-06 17:35:34 -0400, Nico Kadel-Garcia wrote:
>> Take a look at the Fedora Core 5 SRPM and .spec file for
>> subversion-1.3.1.
>> It does some similar things, but not as part of the .spec file. Instead,
>> the rpath option is moved out of the "LINK" command, and into a
>> "LINK_LIBS"
>> command, and that is called only when linking libraries, not when linking
>> programs. This makes good sense to me and seems to help eliminate the RPM
>> build whackiness, and can be backported to other versons of RedHat or
>> Fedora.
>
> are you sure the rpath issue is still valid? it doesnt looks like that
> to me. i tested with 1.3.2.
How did you test it
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in issuetracker)
Posted by Marcus Rueckert <da...@web.de>.
On 2006-06-06 17:35:34 -0400, Nico Kadel-Garcia wrote:
> Take a look at the Fedora Core 5 SRPM and .spec file for subversion-1.3.1.
> It does some similar things, but not as part of the .spec file. Instead,
> the rpath option is moved out of the "LINK" command, and into a "LINK_LIBS"
> command, and that is called only when linking libraries, not when linking
> programs. This makes good sense to me and seems to help eliminate the RPM
> build whackiness, and can be backported to other versons of RedHat or
> Fedora.
are you sure the rpath issue is still valid? it doesnt looks like that
to me. i tested with 1.3.2.
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Agggh! 64-bit bug still present in 1.3.2 (PATCH already in
issuetracker)
Posted by David Summers <da...@summersoft.fay.ar.us>.
Thanks for the pointer.
This has been incorporated into trunk as of r20041 and subsequently
nominated for backport to 1.3.x and 1.4.x.
- David
On Tue, 6 Jun 2006, Nico Kadel-Garcia wrote:
> ----- Original Message ----- From: "David Summers"
>>
>> On Tue, 6 Jun 2006, Toby Johnson wrote:
>>
>>> Marcus Rueckert wrote:
>>>> On 2006-06-06 10:56:19 -0400, Toby Johnson wrote:
>>>>
>>>>> Issue 2. The "chrpath" call failed for me:
>>>>>
>>>>> --- 8< ----- snip ----- >8 ---
>>>>> + chrpath -r /usr/lib64
>>>>> /home/toby/rpms/tmp/subversion-1.5.0-19957/usr/lib64/httpd/modules/mod_authz_svn.so
>>>>> /home/toby/rpms/tmp/subversion-1.5.0-19957/usr/lib64/httpd/modules/mod_authz_svn.so:
>>>>> no rpath or runpath tag found.
>>>>> error: Bad exit status from /home/toby/rpms/tmp/rpm-tmp.51994 (%install)
>>>>>
>>>>>
>>>> running chrpath inside the build process sounds a bit scary.
>>>>
>>>>
>>> That was my first reaction as well... if the library can't be found during
>>> the build, that sounds like a config problem. I'm pretty sure that the
>>> chrpath build-time dependency is a recent addition (in 1.3.1 I think);
>>> David, do you remember why this was needed?
>>>
>>
>> I've been trying for a year or so to figure out why people with NFS and NIS
>> were having error/warning messages printed out in their /var/log/messages
>> with a path showing MY build environment home directory and saying it
>> couldn't find the libraries in that path.
>>
>> I finally figured out a few months ago that it was the -rpath during the
>> build. I tried multiple ways of setting it during the build and couldn't
>> get it to change. I found out about the chrpath command and it took me all
>> of 5 minutes to try it out and fix the problem. If there is a better way,
>> I'm all ears; I've spent a lot of time on the problem over the last year or
>> so and this was the only way I could figure out to fix the problem.
>
> Take a look at the Fedora Core 5 SRPM and .spec file for subversion-1.3.1. It
> does some similar things, but not as part of the .spec file. Instead, the
> rpath option is moved out of the "LINK" command, and into a "LINK_LIBS"
> command, and that is called only when linking libraries, not when linking
> programs. This makes good sense to me and seems to help eliminate the RPM
> build whackiness, and can be backported to other versons of RedHat or Fedora.
>
>
--
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david@summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org