aMule Forum

English => Compilation problems => Topic started by: stoatwblr on May 13, 2010, 04:18:30 AM

Title: 10142+ error
Post by: stoatwblr on May 13, 2010, 04:18:30 AM

10141 compiles fine

I'm getting the following failures  compiling  10142 and up:

10142-7 give this error:

/usr/bin/ccache g++ -g -W -Wall -Wshadow -Wundef -ggdb -fno-inline -fmessage-length=0 -O3 -m64 -mtune=native  -pthread   -lpthread  -o amule amule-CaptchaDialog.o amule-CaptchaGenerator.o amule-amule.o amule-BaseClient.o amule-CanceledFileList.o amule-ClientList.o amule-ClientCreditsList.o amule-ClientTCPSocket.o amule-ClientUDPSocket.o amule-CorruptionBlackBox.o amule-DownloadClient.o amule-DownloadQueue.o amule-ECSpecialCoreTags.o amule-EMSocket.o amule-EncryptedStreamSocket.o amule-EncryptedDatagramSocket.o amule-ExternalConn.o amule-FriendList.o amule-HTTPDownload.o amule-IPFilter.o amule-KnownFileList.o amule-ListenSocket.o amule-MuleUDPSocket.o amule-PartFileConvert.o amule-SearchFile.o amule-SearchList.o amule-ServerConnect.o amule-ServerList.o amule-ServerSocket.o amule-ServerUDPSocket.o amule-SharedFileList.o amule-TerminationProcessAmuleweb.o amule-ThreadTasks.o amule-UploadBandwidthThrottler.o amule-UploadClient.o amule-UploadQueue.o amule-Indexed.o amule-Kademlia.o amule-Prefs.o amule-Search.o amule-UDPFirewallTester.o amule-KademliaUDPListener.o amule-PacketTracking.o amule-RoutingZone.o amule-amule-gui.o amule-amuleDlg.o amule-AddFriend.o amule-CatDialog.o amule-ChatSelector.o amule-ClientDetailDialog.o amule-DirectoryTreeCtrl.o amule-FileDetailDialog.o amule-KadDlg.o amule-OScopeCtrl.o amule-PartFileConvertDlg.o amule-PrefsUnifiedDlg.o amule-SearchDlg.o amule-ServerWnd.o amule-SharedFilesWnd.o amule-StatisticsDlg.o amule-SearchListCtrl.o amule-DownloadListCtrl.o amule-ClientListCtrl.o amule-FriendListCtrl.o amule-ServerListCtrl.o amule-SharedFilesCtrl.o amule-MuleTrayIcon.o amule-MuleColour.o amule-TransferWnd.o amule-amuleAppCommon.o amule-ClientCredits.o amule-ECSpecialMuleTags.o amule-KnownFile.o amule-GetTickCount.o amule-GuiEvents.o amule-Logger.o amule-PartFile.o amule-Preferences.o amule-Proxy.o amule-Server.o amule-Statistics.o amule-StatTree.o amule-SHAHashSet.o amule-TerminationProcess.o amule-UserEvents.o amule-OtherFunctions.o amule-NetworkFunctions.o -L. -lmuleappcommon -Llibs/common -Llibs/ec/cpp -lmulecommon -lec -lbfd -liberty   -lz  -L/usr/lib -lcryptopp -L. -lmuleappcore  -lupnp -lthreadutil -lixml    -L. -lmuleappgui -pthread -Wl,-Bsymbolic-functions  -lwx_gtk2u_adv-2.8 -lwx_gtk2u_core-2.8 -lwx_baseu_net-2.8 -lwx_baseu-2.8   -lGeoIP 
amule-SharedFilesWnd.o: In function `CSharedFilesWnd::SelectionUpdated()':
/usr/src/amule/amule-2.2.6+svn-r10142/src/SharedFilesWnd.cpp:157: undefined reference to `CGenericClientListCtrl::ShowSources(std::__debug::vector<CKnownFile*, std::allocator<CKnownFile*> > const&)'
amule-SharedFilesWnd.o: In function `CSharedFilesWnd':
/usr/src/amule/amule-2.2.6+svn-r10142/src/SharedFilesWnd.cpp:56: undefined reference to `typeinfo for CSharedFilePeersListCtrl'
/usr/src/amule/amule-2.2.6+svn-r10142/src/SharedFilesWnd.cpp:56: undefined reference to `typeinfo for CSharedFilePeersListCtrl'
amule-DownloadListCtrl.o: In function `CDownloadListCtrl::OnItemSelectionChanged(wxListEvent&)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/DownloadListCtrl.cpp:603: undefined reference to `CGenericClientListCtrl::ShowSources(std::__debug::vector<CKnownFile*, std::allocator<CKnownFile*> > const&)'
amule-TransferWnd.o: In function `CTransferWnd':
/usr/src/amule/amule-2.2.6+svn-r10142/src/TransferWnd.cpp:87: undefined reference to `typeinfo for CSourceListCtrl'
/usr/src/amule/amule-2.2.6+svn-r10142/src/TransferWnd.cpp:87: undefined reference to `typeinfo for CSourceListCtrl'
amule-GuiEvents.o: In function `MuleNotify::SharedCtrlRemoveClient(CKnownFile const*, CUpDownClient const*)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:369: undefined reference to `CGenericClientListCtrl::RemoveSource(CUpDownClient const*, CKnownFile const*)'
amule-GuiEvents.o: In function `MuleNotify::SourceCtrlRemoveSource(CUpDownClient const*, CPartFile const*)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:342: undefined reference to `CGenericClientListCtrl::RemoveSource(CUpDownClient const*, CKnownFile const*)'
amule-GuiEvents.o: In function `MuleNotify::SharedCtrlRefreshClient(CUpDownClient*, SourceItemType)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:360: undefined reference to `CGenericClientListCtrl::UpdateItem(void const*, SourceItemType)'
amule-GuiEvents.o: In function `MuleNotify::SourceCtrlUpdateSource(CUpDownClient*, SourceItemType)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:324: undefined reference to `CGenericClientListCtrl::UpdateItem(void const*, SourceItemType)'
amule-GuiEvents.o: In function `MuleNotify::SharedCtrlAddClient(CKnownFile*, CUpDownClient*, SourceItemType)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:351: undefined reference to `CGenericClientListCtrl::AddSource(CKnownFile*, CUpDownClient*, SourceItemType)'
amule-GuiEvents.o: In function `MuleNotify::SourceCtrlAddSource(CPartFile*, CUpDownClient*, SourceItemType)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/GuiEvents.cpp:333: undefined reference to `CGenericClientListCtrl::AddSource(CKnownFile*, CUpDownClient*, SourceItemType)'
./libmuleappgui.a(libmuleappgui_a-muuli_wdr.o): In function `sharedfilesBottomDlg(wxWindow*, bool, bool)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/muuli_wdr.cpp:3459: undefined reference to `CSharedFilePeersListCtrl::CSharedFilePeersListCtrl(wxWindow*, int, wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&)'
./libmuleappgui.a(libmuleappgui_a-muuli_wdr.o): In function `transferBottomPane(wxWindow*, bool, bool)':
/usr/src/amule/amule-2.2.6+svn-r10142/src/muuli_wdr.cpp:473: undefined reference to `CSourceListCtrl::CSourceListCtrl(wxWindow*, int, wxPoint const&, wxSize const&, long, wxValidator const&, wxString const&)'
collect2: ld returned 1 exit status
make[3]: *** [amule] Error 1
make[3]: Leaving directory `/usr/src/amule/amule-2.2.6+svn-r10142/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/amule/amule-2.2.6+svn-r10142/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/amule/amule-2.2.6+svn-r10142'
make: *** [all] Error 2

Any idea what dependencies have changed?
Title: Re: 10142+ error
Post by: Kry on May 13, 2010, 04:43:35 AM
Nothing. You probably haven't run autogen.sh
Title: Re: 10142+ error
Post by: stoatwblr on May 13, 2010, 04:51:28 AM

Isn't that run as part of  the configure script?

Title: Re: 10142+ error
Post by: Kry on May 13, 2010, 07:10:46 AM
Nope
Title: Re: 10142+ error
Post by: Stu Redman on May 13, 2010, 12:25:58 PM
But it's supposed to be part of the tarball generation script (otherwise there would be no configure in the tarball). Running configure is all that should be required for tarball users (and only if files were added/removed as in 10142). Did you run configure? And maybe a make clean afterwards.
Title: Re: 10142+ error
Post by: ^marcell^ on May 13, 2010, 05:20:45 PM
How do you know he's using a tarball? I had some error compiling too and running the autogen.sh solved them.
Title: Re: 10142+ error
Post by: stoatwblr on May 13, 2010, 08:42:12 PM
Yes I'm using  a tarball, yes I ran configure and make clean.

This is the first time I've had to run autogen.sh manually.
Title: Re: 10142+ error
Post by: Kry on May 13, 2010, 09:55:24 PM
Because I added/deleted files.
Title: Re: 10142+ error
Post by: Stu Redman on May 13, 2010, 10:31:20 PM
How do you know he's using a tarball?
My magic crystal ball told me. Also, it helps to know only a handful of people have access to SVN and stoatwblr is not among them.
This is the first time I've had to run autogen.sh manually.
Hmm - I'll pm Vollstrecker that he checks his tarball script.
Title: Re: 10142+ error
Post by: Vollstrecker on May 16, 2010, 05:39:11 PM
How do you know he's using my tarballs? I always run autogen.sh befor packing them (right after removing all the svn-stuff from the checkout). I use the tarballs I release for building my packages, and that step worked here, so I guess he get's his stuff from another bad dealer.
Title: Re: 10142+ error
Post by: Stu Redman on May 16, 2010, 05:47:17 PM
Because GonoszTopi was away at the time.

Stoatwblr, did you use a fresh tarball, or did you apply a patch?
Title: Re: 10142+ error
Post by: GonoszTopi on May 16, 2010, 05:57:29 PM
I guess he get's his stuff from another bad dealer.
I don't know of anyone else than us two.

Stoatwblr, did you use a fresh tarball, or did you apply a patch?
That might be a reason.
Title: Re: 10142+ error
Post by: Vollstrecker on May 16, 2010, 05:59:28 PM
I guess he get's his stuff from another bad dealer.
I don't know of anyone else than us two.
I think there was a git-webfrontend somewhere. Maybe a checkout from there.
Stoatwblr, did you use a fresh tarball, or did you apply a patch?
That might be a reason.
Sounds reasonable. If that is the reason, I should add a hint to my patch-section to run autogen.sh when using them and an error occurs.
Title: Re: 10142+ error
Post by: GonoszTopi on May 16, 2010, 07:55:19 PM
I guess he get's his stuff from another bad dealer.
I don't know of anyone else than us two.
I think there was a git-webfrontend somewhere. Maybe a checkout from there.
That's also updated by me  8)
Title: Re: 10142+ error
Post by: Stu Redman on May 16, 2010, 08:57:36 PM
- but what's in it? SVN content or tarball content?
Title: Re: 10142+ error
Post by: Vollstrecker on May 16, 2010, 09:21:11 PM
I guess he get's his stuff from another bad dealer.
I don't know of anyone else than us two.
I think there was a git-webfrontend somewhere. Maybe a checkout from there.
That's also updated by me  8)
k, so maybe we are really the only ones that give people stuff they should better not touch. But as Stu said, if he checked that out from the git, it has no tarball content. At least I think so.
Title: Re: 10142+ error
Post by: GonoszTopi on May 16, 2010, 11:36:25 PM
The git repo is equivalent to the tarball content. Actually commits in the git repo are created from the tarballs - even if the tarball is later discarded and not uploaded to sourceforge (as is the case with e.g. translation-update tarballs).

But as Stu said, if he checked that out from the git, it has no tarball content. At least I think so.
Stu didn't say that.
Stoatwblr, did you use a fresh tarball, or did you apply a patch?
That might be a reason.
As he said and I pointed out, it might be the case that he used an older tarball from you, and just applied diffs (from your site) to that old tarball. I guess that diffs are from SVN, and not from actually comparing tarball content, right?
Title: Re: 10142+ error
Post by: Vollstrecker on May 17, 2010, 12:49:28 AM
The git repo is equivalent to the tarball content. Actually commits in the git repo are created from the tarballs - even if the tarball is later discarded and not uploaded to sourceforge (as is the case with e.g. translation-update tarballs).

But as Stu said, if he checked that out from the git, it has no tarball content. At least I think so.
Stu didn't say that.
Stu asked would have been the better sentence. I just understood him that way.
Stoatwblr, did you use a fresh tarball, or did you apply a patch?
That might be a reason.
As he said and I pointed out, it might be the case that he used an older tarball from you, and just applied diffs (from your site) to that old tarball. I guess that diffs are from SVN, and not from actually comparing tarball content, right?
Right, but it's going to be changed when I'm back from Netherlands next week. I wouldn't have called it reasonable if it wouldn't be possible with the patches I provide. And I think I'm the only patch-provider so far. When changing this, I maybe include a patch for last-stable to current.
Title: Re: 10142+ error
Post by: stoatwblr on May 17, 2010, 09:13:24 PM
Tarballs and patches - mainly from Vollstrecker's repo.

It's no big deal, now I know what to look for I'll run the script if needed.

Title: Re: 10142+ error
Post by: Vollstrecker on May 23, 2010, 12:04:29 AM
Jep, but the next who doesn't know will come soon.