You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Steve Huston <sh...@riverace.com> on 2008/11/18 22:39:31 UTC
Linking problems on RHEL 4 starting between Friday and Monday
Hi,
I run a daily Qpid trunk build on RHEL 4 and sometime between Friday
Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158) something
changed which causes the following at link time:
/usr/bin/ld: `.L10258' referenced in section
`.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
`.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o
/usr/bin/ld: `.L10513' referenced in section
`.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
`.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o
/usr/bin/ld: `.L9874' referenced in section
`.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
`.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
qpid/broker/.libs/ConnectionHandler.o
The second message above repeats many times. The resulting lib appears
to run, but the voluminous warnings are a bit disconcerting. Does
anyone recall changing something in that area that may explain this?
Thanks,
-Steve
Re: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Alan Conway <ac...@redhat.com>.
On Mon, 2008-11-24 at 18:18 +0000, Gordon Sim wrote:
> Steve Huston wrote:
> > Just as mysteriously as it started, it's gone...
> >
> > RHEL 4 w/ boost 1.35 is now building clean.
>
> My guess is it was something with the spirit stuff that has now been
> removed from url parsing. I can't understand why the particular revision
> that seemed to trigger it would make a difference, but if its building
> ok now I won't worry too much about it! Thanks for the update.
boost::spirit was exorcised in r719410 if that helps.
Re: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Gordon Sim <gs...@redhat.com>.
Steve Huston wrote:
> Just as mysteriously as it started, it's gone...
>
> RHEL 4 w/ boost 1.35 is now building clean.
My guess is it was something with the spirit stuff that has now been
removed from url parsing. I can't understand why the particular revision
that seemed to trigger it would make a difference, but if its building
ok now I won't worry too much about it! Thanks for the update.
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Steve Huston <sh...@riverace.com>.
Just as mysteriously as it started, it's gone...
RHEL 4 w/ boost 1.35 is now building clean.
FYI...
-Steve
> Oh, well, I guess we need look no further. (farther?)
> Sorry, I missed that. When I was porting to RHEL4, boost was the
> source of 99.94% of the trouble. That's the difference.
>
>
>
> On Fri, 2008-11-21 at 13:55 -0500, Steve Huston wrote:
> > Hi Mick,
> >
> > I did see your later email re my finding Broker.cpp triggered the
> > problem.
> >
> > The most obvious diff btw our RHEL 4 systems is probably that I
have
> > boost 1.35 and I'm guessing you have 1.32 or so. Let me
> know if you'd
> > like to compare further.
> >
> > -Steve
> >
> > > -----Original Message-----
> > > From: michael goulish [mailto:mgoulish@redhat.com]
> > > Sent: Friday, November 21, 2008 1:41 PM
> > > To: qpid-dev@incubator.apache.org
> > > Subject: RE: Linking problems on RHEL 4 starting between
> > > Friday and Monday
> > >
> > >
> > > Steve --
> > >
> > > I build frequently on RHEL4, so I thought I would try this out.
> > > This morning I checked out clean trees for both 713904 and
> > > 718158, and I
> > > got normal builds on both.
> > >
> > > So -- I don't know how helpful that is -- but I think there
> > > must be some
> > > other change on your system that is the culprit. I don't
suppose
> > you
> > > have access to a different RHEL4 box that you could try it on?
> > >
> > > Or -- I'd be happy to compare notes between your RHEL4 system
> > > and mine,
> > > if you like.
> > >
> > > ------------------------------ Mick .
> > >
> > >
> > >
> > >
> > > On Wed, 2008-11-19 at 17:23 -0500, Steve Huston wrote:
> > > > Hi Gordon,
> > > >
> > > > Yes, it is puzzling... FYI, it fails the same way on a clean
svn
> > > > checkout.
> > > > Not sure what to make of it...
> > > >
> > > > -Steve
> > > >
> > > > > -----Original Message-----
> > > > > From: Gordon Sim [mailto:gsim@redhat.com]
> > > > > Sent: Wednesday, November 19, 2008 5:25 AM
> > > > > To: qpid-dev@incubator.apache.org
> > > > > Subject: Re: Linking problems on RHEL 4 starting between
> > > > > Friday and Monday
> > > > >
> > > > >
> > > > > Steve Huston wrote:
> > > > > > Hi,
> > > > > > I run a daily Qpid trunk build on RHEL 4 and
> sometime between
> > > > Friday
> > > > > > Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158)
> > > > something
> > > > > > changed which causes the following at link time:
> > > > > >
> > > > > > /usr/bin/ld: `.L10258' referenced in section
> > > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o: defined in
discarded
> > > > section
> > > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > > >
> > > > > > /usr/bin/ld: `.L10513' referenced in section
> > > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o: defined in
discarded
> > > > section
> > > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > > >
> > > > > > /usr/bin/ld: `.L9874' referenced in section
> > > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o: defined in
discarded
> > > > section
> > > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > > >
> > > > > >
> > > > > > The second message above repeats many times. The resulting
> > > > > lib appears
> > > > > > to run, but the voluminous warnings are a bit
> > > disconcerting. Does
> > > > > > anyone recall changing something in that area that
> may explain
> > > > this?
> > > > > >
> > > > > > Thanks,
> > > > > > -Steve
> > > > > >
> > > > > Odd; I can't see anything in the diff between those
> two revision
> > > > that
> > > > > looks like it might be the culprit.
> > > > >
> > > > > Last change to ConnectionHandler was r713739 (last Thursday,
> > > > > 13th). Url
> > > > > hasn't changed this month.
> > > > >
> > > > > Do you see the same errors on a clean build (or is this from
> > > > > a clean build)?
> > > > >
> > > >
> > >
> >
>
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by michael goulish <mg...@redhat.com>.
Oh, well, I guess we need look no further. (farther?)
Sorry, I missed that. When I was porting to RHEL4, boost was the
source of 99.94% of the trouble. That's the difference.
On Fri, 2008-11-21 at 13:55 -0500, Steve Huston wrote:
> Hi Mick,
>
> I did see your later email re my finding Broker.cpp triggered the
> problem.
>
> The most obvious diff btw our RHEL 4 systems is probably that I have
> boost 1.35 and I'm guessing you have 1.32 or so. Let me know if you'd
> like to compare further.
>
> -Steve
>
> > -----Original Message-----
> > From: michael goulish [mailto:mgoulish@redhat.com]
> > Sent: Friday, November 21, 2008 1:41 PM
> > To: qpid-dev@incubator.apache.org
> > Subject: RE: Linking problems on RHEL 4 starting between
> > Friday and Monday
> >
> >
> > Steve --
> >
> > I build frequently on RHEL4, so I thought I would try this out.
> > This morning I checked out clean trees for both 713904 and
> > 718158, and I
> > got normal builds on both.
> >
> > So -- I don't know how helpful that is -- but I think there
> > must be some
> > other change on your system that is the culprit. I don't suppose
> you
> > have access to a different RHEL4 box that you could try it on?
> >
> > Or -- I'd be happy to compare notes between your RHEL4 system
> > and mine,
> > if you like.
> >
> > ------------------------------ Mick .
> >
> >
> >
> >
> > On Wed, 2008-11-19 at 17:23 -0500, Steve Huston wrote:
> > > Hi Gordon,
> > >
> > > Yes, it is puzzling... FYI, it fails the same way on a clean svn
> > > checkout.
> > > Not sure what to make of it...
> > >
> > > -Steve
> > >
> > > > -----Original Message-----
> > > > From: Gordon Sim [mailto:gsim@redhat.com]
> > > > Sent: Wednesday, November 19, 2008 5:25 AM
> > > > To: qpid-dev@incubator.apache.org
> > > > Subject: Re: Linking problems on RHEL 4 starting between
> > > > Friday and Monday
> > > >
> > > >
> > > > Steve Huston wrote:
> > > > > Hi,
> > > > > I run a daily Qpid trunk build on RHEL 4 and sometime between
> > > Friday
> > > > > Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158)
> > > something
> > > > > changed which causes the following at link time:
> > > > >
> > > > > /usr/bin/ld: `.L10258' referenced in section
> > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > > section
> > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > >
> > > > > /usr/bin/ld: `.L10513' referenced in section
> > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > > section
> > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > >
> > > > > /usr/bin/ld: `.L9874' referenced in section
> > > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > > section
> > > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > > qpid/broker/.libs/ConnectionHandler.o
> > > > >
> > > > >
> > > > > The second message above repeats many times. The resulting
> > > > lib appears
> > > > > to run, but the voluminous warnings are a bit
> > disconcerting. Does
> > > > > anyone recall changing something in that area that may explain
> > > this?
> > > > >
> > > > > Thanks,
> > > > > -Steve
> > > > >
> > > > Odd; I can't see anything in the diff between those two revision
> > > that
> > > > looks like it might be the culprit.
> > > >
> > > > Last change to ConnectionHandler was r713739 (last Thursday,
> > > > 13th). Url
> > > > hasn't changed this month.
> > > >
> > > > Do you see the same errors on a clean build (or is this from
> > > > a clean build)?
> > > >
> > >
> >
>
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Steve Huston <sh...@riverace.com>.
Hi Mick,
I did see your later email re my finding Broker.cpp triggered the
problem.
The most obvious diff btw our RHEL 4 systems is probably that I have
boost 1.35 and I'm guessing you have 1.32 or so. Let me know if you'd
like to compare further.
-Steve
> -----Original Message-----
> From: michael goulish [mailto:mgoulish@redhat.com]
> Sent: Friday, November 21, 2008 1:41 PM
> To: qpid-dev@incubator.apache.org
> Subject: RE: Linking problems on RHEL 4 starting between
> Friday and Monday
>
>
> Steve --
>
> I build frequently on RHEL4, so I thought I would try this out.
> This morning I checked out clean trees for both 713904 and
> 718158, and I
> got normal builds on both.
>
> So -- I don't know how helpful that is -- but I think there
> must be some
> other change on your system that is the culprit. I don't suppose
you
> have access to a different RHEL4 box that you could try it on?
>
> Or -- I'd be happy to compare notes between your RHEL4 system
> and mine,
> if you like.
>
> ------------------------------ Mick .
>
>
>
>
> On Wed, 2008-11-19 at 17:23 -0500, Steve Huston wrote:
> > Hi Gordon,
> >
> > Yes, it is puzzling... FYI, it fails the same way on a clean svn
> > checkout.
> > Not sure what to make of it...
> >
> > -Steve
> >
> > > -----Original Message-----
> > > From: Gordon Sim [mailto:gsim@redhat.com]
> > > Sent: Wednesday, November 19, 2008 5:25 AM
> > > To: qpid-dev@incubator.apache.org
> > > Subject: Re: Linking problems on RHEL 4 starting between
> > > Friday and Monday
> > >
> > >
> > > Steve Huston wrote:
> > > > Hi,
> > > > I run a daily Qpid trunk build on RHEL 4 and sometime between
> > Friday
> > > > Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158)
> > something
> > > > changed which causes the following at link time:
> > > >
> > > > /usr/bin/ld: `.L10258' referenced in section
> > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > section
> > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o
> > > >
> > > > /usr/bin/ld: `.L10513' referenced in section
> > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > section
> > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o
> > > >
> > > > /usr/bin/ld: `.L9874' referenced in section
> > > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> > section
> > > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > > qpid/broker/.libs/ConnectionHandler.o
> > > >
> > > >
> > > > The second message above repeats many times. The resulting
> > > lib appears
> > > > to run, but the voluminous warnings are a bit
> disconcerting. Does
> > > > anyone recall changing something in that area that may explain
> > this?
> > > >
> > > > Thanks,
> > > > -Steve
> > > >
> > > Odd; I can't see anything in the diff between those two revision
> > that
> > > looks like it might be the culprit.
> > >
> > > Last change to ConnectionHandler was r713739 (last Thursday,
> > > 13th). Url
> > > hasn't changed this month.
> > >
> > > Do you see the same errors on a clean build (or is this from
> > > a clean build)?
> > >
> >
>
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by michael goulish <mg...@redhat.com>.
Steve --
I build frequently on RHEL4, so I thought I would try this out.
This morning I checked out clean trees for both 713904 and 718158, and I
got normal builds on both.
So -- I don't know how helpful that is -- but I think there must be some
other change on your system that is the culprit. I don't suppose you
have access to a different RHEL4 box that you could try it on?
Or -- I'd be happy to compare notes between your RHEL4 system and mine,
if you like.
------------------------------ Mick .
On Wed, 2008-11-19 at 17:23 -0500, Steve Huston wrote:
> Hi Gordon,
>
> Yes, it is puzzling... FYI, it fails the same way on a clean svn
> checkout.
> Not sure what to make of it...
>
> -Steve
>
> > -----Original Message-----
> > From: Gordon Sim [mailto:gsim@redhat.com]
> > Sent: Wednesday, November 19, 2008 5:25 AM
> > To: qpid-dev@incubator.apache.org
> > Subject: Re: Linking problems on RHEL 4 starting between
> > Friday and Monday
> >
> >
> > Steve Huston wrote:
> > > Hi,
> > > I run a daily Qpid trunk build on RHEL 4 and sometime between
> Friday
> > > Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158)
> something
> > > changed which causes the following at link time:
> > >
> > > /usr/bin/ld: `.L10258' referenced in section
> > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> section
> > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o
> > >
> > > /usr/bin/ld: `.L10513' referenced in section
> > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> section
> > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o
> > >
> > > /usr/bin/ld: `.L9874' referenced in section
> > > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
> section
> > > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > > qpid/broker/.libs/ConnectionHandler.o
> > >
> > >
> > > The second message above repeats many times. The resulting
> > lib appears
> > > to run, but the voluminous warnings are a bit disconcerting. Does
> > > anyone recall changing something in that area that may explain
> this?
> > >
> > > Thanks,
> > > -Steve
> > >
> > Odd; I can't see anything in the diff between those two revision
> that
> > looks like it might be the culprit.
> >
> > Last change to ConnectionHandler was r713739 (last Thursday,
> > 13th). Url
> > hasn't changed this month.
> >
> > Do you see the same errors on a clean build (or is this from
> > a clean build)?
> >
>
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by michael goulish <mg...@redhat.com>.
Sorry -- I didn't notice this post before I sent my reply -- I'll see if
I can repro this on my system.
On Fri, 2008-11-21 at 12:19 -0500, Steve Huston wrote:
> Hi Gordon,
>
> This is the change that triggered the link diagnostics. Why? I don't
> know... Will look into that next, but any ideas are welcome.
>
> -Steve
>
> [shuston@timmy broker]$ svn diff -r{2008-11-14} Broker.cpp
> Index: Broker.cpp
> ===================================================================
> --- Broker.cpp (revision 713916)
> +++ Broker.cpp (working copy)
> @@ -240,11 +240,10 @@
> queueCleaner.start(conf.queueCleanInterval *
> qpid::sys::TIME_SEC);
> }
>
> - //initialize known broker urls:
> - try {
> - knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
> getPort(TCP_TRANSPORT) ) );
> - } catch (const NoSuchTransportException& e) {
> - QPID_LOG(error, "Could not send client known broker urls for
> cluster: " << e.what());
> + //initialize known broker urls (TODO: add support for urls for
> other transports (SSL, RDMA)):
> + boost::shared_ptr<ProtocolFactory> factory =
> getProtocolFactory(TCP_TRANSPORT);
> + if (factory) {
> + knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
> factory->getPort() ) );
> }
> }
>
> > -----Original Message-----
> > From: Gordon Sim [mailto:gsim@redhat.com]
> > Sent: Thursday, November 20, 2008 9:35 AM
> > To: qpid-dev@incubator.apache.org
> > Subject: Re: Linking problems on RHEL 4 starting between
> > Friday and Monday
> >
> >
> > Steve Huston wrote:
> > > Hi Gordon,
> > >
> > > Yes, it is puzzling... FYI, it fails the same way on a clean svn
> > > checkout.
> > > Not sure what to make of it...
> >
> > Does reverting back to a revision from last week fix it? If
> > so trying to
> > narrow down the revision where it first appears might help.
> >
> > We have automated rhel4 builds also, but they are using the standard
>
> > boost version (1.32) which is quite old (and requires the
> > special patch
> > as checked in under boost-1.32-support. Haven't seen the
> > problem you are
> > describing.
> >
>
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Steve Huston <sh...@riverace.com>.
Hi Gordon,
This is the change that triggered the link diagnostics. Why? I don't
know... Will look into that next, but any ideas are welcome.
-Steve
[shuston@timmy broker]$ svn diff -r{2008-11-14} Broker.cpp
Index: Broker.cpp
===================================================================
--- Broker.cpp (revision 713916)
+++ Broker.cpp (working copy)
@@ -240,11 +240,10 @@
queueCleaner.start(conf.queueCleanInterval *
qpid::sys::TIME_SEC);
}
- //initialize known broker urls:
- try {
- knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
getPort(TCP_TRANSPORT) ) );
- } catch (const NoSuchTransportException& e) {
- QPID_LOG(error, "Could not send client known broker urls for
cluster: " << e.what());
+ //initialize known broker urls (TODO: add support for urls for
other transports (SSL, RDMA)):
+ boost::shared_ptr<ProtocolFactory> factory =
getProtocolFactory(TCP_TRANSPORT);
+ if (factory) {
+ knownBrokers.push_back ( qpid::Url::getIpAddressesUrl (
factory->getPort() ) );
}
}
> -----Original Message-----
> From: Gordon Sim [mailto:gsim@redhat.com]
> Sent: Thursday, November 20, 2008 9:35 AM
> To: qpid-dev@incubator.apache.org
> Subject: Re: Linking problems on RHEL 4 starting between
> Friday and Monday
>
>
> Steve Huston wrote:
> > Hi Gordon,
> >
> > Yes, it is puzzling... FYI, it fails the same way on a clean svn
> > checkout.
> > Not sure what to make of it...
>
> Does reverting back to a revision from last week fix it? If
> so trying to
> narrow down the revision where it first appears might help.
>
> We have automated rhel4 builds also, but they are using the standard
> boost version (1.32) which is quite old (and requires the
> special patch
> as checked in under boost-1.32-support. Haven't seen the
> problem you are
> describing.
>
Re: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Gordon Sim <gs...@redhat.com>.
Steve Huston wrote:
> Hi Gordon,
>
> Yes, it is puzzling... FYI, it fails the same way on a clean svn
> checkout.
> Not sure what to make of it...
Does reverting back to a revision from last week fix it? If so trying to
narrow down the revision where it first appears might help.
We have automated rhel4 builds also, but they are using the standard
boost version (1.32) which is quite old (and requires the special patch
as checked in under boost-1.32-support. Haven't seen the problem you are
describing.
RE: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Steve Huston <sh...@riverace.com>.
Hi Gordon,
Yes, it is puzzling... FYI, it fails the same way on a clean svn
checkout.
Not sure what to make of it...
-Steve
> -----Original Message-----
> From: Gordon Sim [mailto:gsim@redhat.com]
> Sent: Wednesday, November 19, 2008 5:25 AM
> To: qpid-dev@incubator.apache.org
> Subject: Re: Linking problems on RHEL 4 starting between
> Friday and Monday
>
>
> Steve Huston wrote:
> > Hi,
> > I run a daily Qpid trunk build on RHEL 4 and sometime between
Friday
> > Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158)
something
> > changed which causes the following at link time:
> >
> > /usr/bin/ld: `.L10258' referenced in section
> > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
section
> > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o
> >
> > /usr/bin/ld: `.L10513' referenced in section
> > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
section
> > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o
> >
> > /usr/bin/ld: `.L9874' referenced in section
> > `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o: defined in discarded
section
> > `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> > qpid/broker/.libs/ConnectionHandler.o
> >
> >
> > The second message above repeats many times. The resulting
> lib appears
> > to run, but the voluminous warnings are a bit disconcerting. Does
> > anyone recall changing something in that area that may explain
this?
> >
> > Thanks,
> > -Steve
> >
> Odd; I can't see anything in the diff between those two revision
that
> looks like it might be the culprit.
>
> Last change to ConnectionHandler was r713739 (last Thursday,
> 13th). Url
> hasn't changed this month.
>
> Do you see the same errors on a clean build (or is this from
> a clean build)?
>
Re: Linking problems on RHEL 4 starting between Friday and Monday
Posted by Gordon Sim <gs...@redhat.com>.
Steve Huston wrote:
> Hi,
> I run a daily Qpid trunk build on RHEL 4 and sometime between Friday
> Nov 14 (svn rev 713904) and Monday Nov 18 (svn rev 718158) something
> changed which causes the following at link time:
>
> /usr/bin/ld: `.L10258' referenced in section
> `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
> `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o
>
> /usr/bin/ld: `.L10513' referenced in section
> `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
> `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o
>
> /usr/bin/ld: `.L9874' referenced in section
> `.gnu.linkonce.r._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o: defined in discarded section
> `.gnu.linkonce.t._ZNSt6vectorIN4qpid3UrlESaIS1_EED1Ev' of
> qpid/broker/.libs/ConnectionHandler.o
>
>
> The second message above repeats many times. The resulting lib appears
> to run, but the voluminous warnings are a bit disconcerting. Does
> anyone recall changing something in that area that may explain this?
>
> Thanks,
> -Steve
>
Odd; I can't see anything in the diff between those two revision that
looks like it might be the culprit.
Last change to ConnectionHandler was r713739 (last Thursday, 13th). Url
hasn't changed this month.
Do you see the same errors on a clean build (or is this from a clean build)?