Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
I mean them downloading from the psybnc website and installing from that tarball, I guess an option I can provide is to compile from ports and make some sort of script to install the binaries to the user's dir. Chris On Sat, 29 Jan 2005 21:10:53 +1300, Jonathan Chen <[EMAIL PROTECTED]> wrote: > On Sat, Jan 29, 2005 at 02:45:27AM +, Chris wrote: > > I am talking about the psybnc source because its for users on the > > server who cannot compile software from ports. > > If they can't compile from ports, then they certainly won't be able to > install it; won't that mean that they won't be able to use it? > > If they want to do is compile it, all they have to do is to apply the > patches from the port. > -- > Jonathan Chen <[EMAIL PROTECTED]> > -- >"Only the meek get pinched. The bold survive." > - Ferris Bueller > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Sat, Jan 29, 2005 at 02:45:27AM +, Chris wrote: > I am talking about the psybnc source because its for users on the > server who cannot compile software from ports. If they can't compile from ports, then they certainly won't be able to install it; won't that mean that they won't be able to use it? If they want to do is compile it, all they have to do is to apply the patches from the port. -- Jonathan Chen <[EMAIL PROTECTED]> -- "Only the meek get pinched. The bold survive." - Ferris Bueller ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
I am talking about the psybnc source because its for users on the server who cannot compile software from ports. Chris On Thu, 27 Jan 2005 21:03:05 -0800 (PST), Rob <[EMAIL PROTECTED]> wrote: > > --- Kris Kennaway <[EMAIL PROTECTED]> wrote: > > > On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote: > > > > > > Hi, > > > > > > There seems to be a bug with the gcc version of > > 5.3 > > > STABLE (gcc 3.4.2), when using: > > > > > > #define _GLIBCXX_DEBUG > > > #define _GLIBCXX_DEBUG_PEDANTIC > > > > What are those? FreeBSD doesn't use GLIBC, so how > > do you know it's a FreeBSD bug? > > What these are, I don't know, but these are used > by LyX (or generated by the auto-tools). > Noone else on the LyX-devel mailinglist has problems > with them, except me. > > On that mailinglist, I'm the only FreeBSD user > and the problems seem aris with the specific version > of gcc on FreeBSD 5.3. > > Please do not misunderstand: I'm not complaining, > I just inform 5.3 users of this issue. > > Regards, > Rob. > > > __ > Do you Yahoo!? > The all-new My Yahoo! - Get yours free! > http://my.yahoo.com > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
--- Kris Kennaway <[EMAIL PROTECTED]> wrote: > On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote: > > > > Hi, > > > > There seems to be a bug with the gcc version of > 5.3 > > STABLE (gcc 3.4.2), when using: > > > > #define _GLIBCXX_DEBUG > > #define _GLIBCXX_DEBUG_PEDANTIC > > What are those? FreeBSD doesn't use GLIBC, so how > do you know it's a FreeBSD bug? What these are, I don't know, but these are used by LyX (or generated by the auto-tools). Noone else on the LyX-devel mailinglist has problems with them, except me. On that mailinglist, I'm the only FreeBSD user and the problems seem aris with the specific version of gcc on FreeBSD 5.3. Please do not misunderstand: I'm not complaining, I just inform 5.3 users of this issue. Regards, Rob. __ Do you Yahoo!? The all-new My Yahoo! - Get yours free! http://my.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote: > I then decided to try psybnc myself and this is what happens using > gcc 3.4.2 bundled with 5.3. > > Initializing bouncer compilation > [*] Running Conversion Tool for older psyBNC Data. > tools/convconf.c: In function `cofile': > tools/convconf.c:81: error: label at end of compound statement > *** Error code 1 > > Stop in /usr/home/chrysalis/psybnc. The above isn't using the ports collection, right? Thus your complaint is not justified. You simply blame the compiler. Yes, compilers have bugs but the do evolve too. And in this case GCC 3.4.x catches a bug _in_ the source that previous GCC versions missed. > however if I install gcc 3.3.6 and then edit the top line in Makefile > to cc = gcc33 then it compiles fine. You really should have looked at the place GCC complained about: it _is_ a bug in the source! There is a label and no statement after the label. Add a ; and it will compile. Older GCC versionss accept that. > I will as you suggest try a later gcc in the 3.4.x branch as there is > newer version then what is bundled in 5.3 and I will report back. I would suggest that you update+use ports because the ports-collection has a patch for this particular problem: files/patch-tools-convconf.c > I havent test ezbounce with 3.3.6 yet. This is C++ and probably a different issue. Gunther ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Thu, Jan 27, 2005 at 12:17:37AM -0800, Kris Kennaway wrote: > On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote: > > Well it started out with me getting a complaint from a user on my > > server saying he couldnt compile psybnc since I upgraded to 5.3 I told > > him I would investigate when I get time, I then found out later that > > ezbounce also failed (i use ezbounce) on 5.3, but my binary which was > > backed up from when I compiled on 5.2.1 works fine. I also heard from > > many friends on irc that psybnc doesnt work with 5.3 so obviously the > > problem is wide spread and it was one reason why a lot of shell > > companies were not upgrading from 4.x yet. I then decided to try > > psybnc myself and this is what happens using gcc 3.4.2 bundled with > > 5.3. > > > > Initializing bouncer compilation > > [*] Running Conversion Tool for older psyBNC Data. > > tools/convconf.c: In function `cofile': > > tools/convconf.c:81: error: label at end of compound statement > > *** Error code 1 > > That's a source code bug, of course, not a gcc bug. Do try to get > your accusations straight. > > The ezbounce port compiles fine on 5.3: > > http://pointyhat.freebsd.org/errorlogs/i386-5-full-logs/ezbounce-1.04.b.log.bz2 > > The psybnc port is not compilable automatically since it's > interactive, so this problem has not been detected by the automated > builds. You should raise it with the psybnc port maintainer or the > software developers. In fact, the psybnc port builds fine too. Don't you look foolish now? :-) Kris pgpBxA5gvPbjq.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Thu, Jan 27, 2005 at 07:42:11AM +, Chris wrote: > Well it started out with me getting a complaint from a user on my > server saying he couldnt compile psybnc since I upgraded to 5.3 I told > him I would investigate when I get time, I then found out later that > ezbounce also failed (i use ezbounce) on 5.3, but my binary which was > backed up from when I compiled on 5.2.1 works fine. I also heard from > many friends on irc that psybnc doesnt work with 5.3 so obviously the > problem is wide spread and it was one reason why a lot of shell > companies were not upgrading from 4.x yet. I then decided to try > psybnc myself and this is what happens using gcc 3.4.2 bundled with > 5.3. > > Initializing bouncer compilation > [*] Running Conversion Tool for older psyBNC Data. > tools/convconf.c: In function `cofile': > tools/convconf.c:81: error: label at end of compound statement > *** Error code 1 That's a source code bug, of course, not a gcc bug. Do try to get your accusations straight. The ezbounce port compiles fine on 5.3: http://pointyhat.freebsd.org/errorlogs/i386-5-full-logs/ezbounce-1.04.b.log.bz2 The psybnc port is not compilable automatically since it's interactive, so this problem has not been detected by the automated builds. You should raise it with the psybnc port maintainer or the software developers. Kris pgpfZAdtcC3gu.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
Well it started out with me getting a complaint from a user on my server saying he couldnt compile psybnc since I upgraded to 5.3 I told him I would investigate when I get time, I then found out later that ezbounce also failed (i use ezbounce) on 5.3, but my binary which was backed up from when I compiled on 5.2.1 works fine. I also heard from many friends on irc that psybnc doesnt work with 5.3 so obviously the problem is wide spread and it was one reason why a lot of shell companies were not upgrading from 4.x yet. I then decided to try psybnc myself and this is what happens using gcc 3.4.2 bundled with 5.3. Initializing bouncer compilation [*] Running Conversion Tool for older psyBNC Data. tools/convconf.c: In function `cofile': tools/convconf.c:81: error: label at end of compound statement *** Error code 1 Stop in /usr/home/chrysalis/psybnc. I can duplicate this problem every single time on any 5.3 box it has a 100% failure rate so I would be interested to know how psybnc worked for you, however if I install gcc 3.3.6 and then edit the top line in Makefile to cc = gcc33 then it compiles fine. I will as you suggest try a later gcc in the 3.4.x branch as there is newer version then what is bundled in 5.3 and I will report back. I havent test ezbounce with 3.3.6 yet. Chris On Wed, 26 Jan 2005 21:06:26 +0100, Björn König <[EMAIL PROTECTED]> wrote: > Chris schrieb: > > >there is also a bug which prevents compiling of ezbounce and psybnc, I > >wonder how much testing went into the new gcc compiler or was it just > >bundled into the release, considering this is the reccommended release > >for production server's now this is a bad oversight, I think the gcc > >should be changed in the next patch level back to 3.3.6. > > > > > I compiled psybnc already a few times with FreeBSD 5.3 successfully. If > there is a problem then please tell it. > > Regards Björn > > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
Chris schrieb: there is also a bug which prevents compiling of ezbounce and psybnc, I wonder how much testing went into the new gcc compiler or was it just bundled into the release, considering this is the reccommended release for production server's now this is a bad oversight, I think the gcc should be changed in the next patch level back to 3.3.6. I compiled psybnc already a few times with FreeBSD 5.3 successfully. If there is a problem then please tell it. Regards Björn ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Wed, Jan 26, 2005 at 02:48:01AM -0800, Rob wrote: > > Hi, > > There seems to be a bug with the gcc version of 5.3 > STABLE (gcc 3.4.2), when using: > > #define _GLIBCXX_DEBUG > #define _GLIBCXX_DEBUG_PEDANTIC What are those? FreeBSD doesn't use GLIBC, so how do you know it's a FreeBSD bug? Kris pgp1dKlJmmhwK.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Wed, Jan 26, 2005 at 12:03:28PM +, Chris wrote: > there is also a bug which prevents compiling of ezbounce and psybnc, I > wonder how much testing went into the new gcc compiler or was it just > bundled into the release, considering this is the reccommended release > for production server's now this is a bad oversight. If you're going to make assertions of negligence, back them up with facts or you just come across as trying to stir up trouble. What problems? How would you suggest we prove that the next version of gcc is free from bugs before we "bundle it into the release" (and maybe you should also tell the gcc people as I'm sure they'd also love to know)? Kris pgpbmlv9XQqEF.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
On Wednesday, 26. January 2005 13:03, Chris wrote: > there is also a bug which prevents compiling of ezbounce and psybnc, I > wonder how much testing went into the new gcc compiler or was it just > bundled into the release, considering this is the reccommended release > for production server's now this is a bad oversight, I think the gcc > should be changed in the next patch level back to 3.3.6. Not gonna happen (would break binary compat). If you think you have found bugs in gcc, try to get them fixed upstream, preferably in the gcc-branch -STABLE is currently using (i.e., right now 3.4). Updates of the base-gcc within the same branch are possible if warranted. -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpI3PJqHWkoP.pgp Description: PGP signature
Re: Linking problems with gcc 3.4.2 and glibc on 5.3-stable
there is also a bug which prevents compiling of ezbounce and psybnc, I wonder how much testing went into the new gcc compiler or was it just bundled into the release, considering this is the reccommended release for production server's now this is a bad oversight, I think the gcc should be changed in the next patch level back to 3.3.6. Chris On Wed, 26 Jan 2005 02:48:01 -0800 (PST), Rob <[EMAIL PROTECTED]> wrote: > > Hi, > > There seems to be a bug with the gcc version of 5.3 > STABLE (gcc 3.4.2), when using: > > #define _GLIBCXX_DEBUG > #define _GLIBCXX_DEBUG_PEDANTIC > > I discovered this when compiling the LyX sources, and > the LyX mailing list pointed out that this is gcc/OS > FreeBSD issue. > > The linking ends with errors that complain about > "__gnu_norm::", for example: > > BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE9_M_insertENS_14_List_iteratorIS1_EERKS1_+0x19): > In function `__gnu_norm::list std::allocator>>::_M_insert(__gnu_norm::_List_iterator, > Branch const&)': > > /usr/include/c++/3.4/bits/locale_facets.tcc:2443: > undefined reference to > `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' > BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE8_M_eraseENS_14_List_iteratorIS1_EE+0xd): > In function `__gnu_norm::list std::allocator>>::_M_erase(__gnu_norm::_List_iterator)': > > /usr/include/c++/3.4/debug/list:122: undefined > reference to > `__gnu_norm::_List_node_base::unhook()' > > [...cut...] > > /usr/include/c++/3.4/bits/stl_algobase.h:155: > undefined reference to > `__gnu_norm::_List_node_base::transfer(__gnu_norm::_List_node_base*, > __gnu_norm::_List_node_base*)' > ../boost/libs/signals/src/.libs/libboost_signals.a(trackable.o)(.gnu.linkonce.t._ZN10__gnu_norm4listIN5boost7signals10connectionESaIS3_EE9_M_insertENS_14_List_iteratorIS3_EERKS3_+0x28): > > In function > `__gnu_norm::list std::allocator>>::_M_insert(__gnu_norm::_List_iterator, > > boost::signals::connection const&)': > > /usr/include/c++/3.4/debug/formatter.h:359: undefined > reference to > `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' > > Is this a known issue? > > Rob. > > __ > Do you Yahoo!? > Meet the all-new My Yahoo! - Try it today! > http://my.yahoo.com > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Linking problems with gcc 3.4.2 and glibc on 5.3-stable
Hi, There seems to be a bug with the gcc version of 5.3 STABLE (gcc 3.4.2), when using: #define _GLIBCXX_DEBUG #define _GLIBCXX_DEBUG_PEDANTIC I discovered this when compiling the LyX sources, and the LyX mailing list pointed out that this is gcc/OS FreeBSD issue. The linking ends with errors that complain about "__gnu_norm::", for example: BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE9_M_insertENS_14_List_iteratorIS1_EERKS1_+0x19): In function `__gnu_norm::list>>::_M_insert(__gnu_norm::_List_iterator, Branch const&)': /usr/include/c++/3.4/bits/locale_facets.tcc:2443: undefined reference to `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' BranchList.o(.gnu.linkonce.t._ZN10__gnu_norm4listI6BranchSaIS1_EE8_M_eraseENS_14_List_iteratorIS1_EE+0xd): In function `__gnu_norm::list>>::_M_erase(__gnu_norm::_List_iterator)': /usr/include/c++/3.4/debug/list:122: undefined reference to `__gnu_norm::_List_node_base::unhook()' [...cut...] /usr/include/c++/3.4/bits/stl_algobase.h:155: undefined reference to `__gnu_norm::_List_node_base::transfer(__gnu_norm::_List_node_base*, __gnu_norm::_List_node_base*)' ../boost/libs/signals/src/.libs/libboost_signals.a(trackable.o)(.gnu.linkonce.t._ZN10__gnu_norm4listIN5boost7signals10connectionESaIS3_EE9_M_insertENS_14_List_iteratorIS3_EERKS3_+0x28): In function `__gnu_norm::list>>::_M_insert(__gnu_norm::_List_iterator, boost::signals::connection const&)': /usr/include/c++/3.4/debug/formatter.h:359: undefined reference to `__gnu_norm::_List_node_base::hook(__gnu_norm::_List_node_base*)' Is this a known issue? Rob. __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
