barry-devel Mailing List for Barry (Page 4)
Status: Beta
Brought to you by:
ndprojects
Menu
▾
▴
barry-devel — Development discussion mailing list
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(29) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2006 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(20) |
Jul
(13) |
Aug
|
Sep
(4) |
Oct
(16) |
Nov
(4) |
Dec
(11) |
| 2007 |
Jan
(57) |
Feb
(40) |
Mar
(78) |
Apr
(20) |
May
(70) |
Jun
(50) |
Jul
(41) |
Aug
(81) |
Sep
(62) |
Oct
(20) |
Nov
(106) |
Dec
(115) |
| 2008 |
Jan
(14) |
Feb
(29) |
Mar
(32) |
Apr
(74) |
May
(75) |
Jun
(63) |
Jul
(77) |
Aug
(105) |
Sep
(62) |
Oct
(93) |
Nov
(130) |
Dec
(51) |
| 2009 |
Jan
(247) |
Feb
(238) |
Mar
(164) |
Apr
(82) |
May
(81) |
Jun
(106) |
Jul
(118) |
Aug
(52) |
Sep
(102) |
Oct
(24) |
Nov
(54) |
Dec
(97) |
| 2010 |
Jan
(31) |
Feb
(41) |
Mar
(38) |
Apr
(9) |
May
(43) |
Jun
(7) |
Jul
(30) |
Aug
(62) |
Sep
(42) |
Oct
(84) |
Nov
(15) |
Dec
(55) |
| 2011 |
Jan
(74) |
Feb
(53) |
Mar
(30) |
Apr
(14) |
May
(22) |
Jun
(34) |
Jul
(22) |
Aug
(6) |
Sep
(23) |
Oct
(19) |
Nov
(42) |
Dec
(12) |
| 2012 |
Jan
(31) |
Feb
(6) |
Mar
(4) |
Apr
(2) |
May
(17) |
Jun
(5) |
Jul
(20) |
Aug
(13) |
Sep
(5) |
Oct
(13) |
Nov
(8) |
Dec
|
| 2013 |
Jan
(3) |
Feb
(5) |
Mar
(5) |
Apr
(11) |
May
(6) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2014 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(10) |
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Chris F. <cd...@fo...> - 2012-09-21 20:37:06
|
On Thu, Sep 20, 2012 at 08:54:02PM -0500, Eddy Castillo wrote: > Is there any possibility that barry is not showing all the device databases? Not to my knowledge. If you need to make sure, try doing a backup with RIM's Windows Desktop software, and peek into the resulting backup file. You should see the same databases there as Barry gives. Also, if the Windows software can display the PRD number anywhere, then in theory, Barry should be able to fetch it as well. Be sure to search the Barry output in ASCII, and in hex, and in big and little endian. It may be binary encoded in one of the record dumps, so searching for it may be a bit of work. - Chris |
|
From: Eddy C. <edd...@gm...> - 2012-09-21 01:54:09
|
Hi Chris, Thank you for the answer. I've used btool to dump all the databases and it appears that this information is not on those databases. Is there any possibility that barry is not showing all the device databases? And if so, what would need to be modified in order to search for the missing ones? Thank you very much for your help. Regards, 2012/9/19 Chris Frey <cd...@fo...> > On Wed, Sep 19, 2012 at 02:00:06PM -0500, Eddy Castillo wrote: > > Do you know if there is a way to extract that information using barry or > > how to use barry to know what database stores that information and parse > it > > if needed? > > I'm not aware of where that data would be, but you might use btool to > dump all the databases in your device, and search the resulting hex dumps > for the expected data. > > Alternatively, you might expand one of the backup tarball files, and > do a binary search through the files. > > Once you know the database, it's just a matter of reverse engineering > the database format. You can look at the code in the src/r_*.cc files > for examples of some common formats. > > - Chris > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Barry-devel mailing list > Bar...@li... > https://lists.sourceforge.net/lists/listinfo/barry-devel > -- Eddy Castillo Statistics, Process Reengineering and Sofware Development Consultant Mobile: +52 (899) 214 5631 |
|
From: Chris F. <cd...@fo...> - 2012-09-19 20:07:37
|
On Wed, Sep 19, 2012 at 02:00:06PM -0500, Eddy Castillo wrote: > Do you know if there is a way to extract that information using barry or > how to use barry to know what database stores that information and parse it > if needed? I'm not aware of where that data would be, but you might use btool to dump all the databases in your device, and search the resulting hex dumps for the expected data. Alternatively, you might expand one of the backup tarball files, and do a binary search through the files. Once you know the database, it's just a matter of reverse engineering the database format. You can look at the code in the src/r_*.cc files for examples of some common formats. - Chris |
|
From: Eddy C. <edd...@gm...> - 2012-09-19 19:00:17
|
Hi There, Currently I'm doing some programs aimed to tasks automation using Blackberries and I need to extract the PRD information stored inside the phones. I know that PRD info is visible in the BB inside the device info located in the Engineering screens that in general are blocked. Do you know if there is a way to extract that information using barry or how to use barry to know what database stores that information and parse it if needed? Best Regards, -- Eddy Castillo Statistics, Process Reengineering and Sofware Development Consultant Mobile: +52 (899) 214 5631 |
|
From: Chris F. <cd...@fo...> - 2012-08-20 21:40:30
|
On Mon, Aug 20, 2012 at 09:15:10PM +0200, Nicolas CARRIER wrote: > Hello, > Please find attached the corresponding patch ! Thanks! Applied. - Chris |
|
From: Chris F. <cd...@fo...> - 2012-08-20 18:38:48
|
On Mon, Aug 20, 2012 at 01:15:38PM +0200, Nicolas CARRIER wrote: > Hello, > At last I could finish the general french translation, which you'll find > attached. > I've also ran make update-po to gain some time. Thanks very much! I've applied the patch. In the meantime, I've added a -T option to the bio command line. Here are the 2 new fuzzy sections. If you want to translate them via email, I can update the .po files for you. " -T Show only the names of the databases.\n" "No name-only option in this mode" > I still didn't manage to build barry for now but my internet connexion is > slow and french riviera isn't propitious to intense debugging... > I think I'll do some correction when I can test it in real condition. Sounds good. Enjoy the riviera :-) - Chris |
|
From: Chris F. <cd...@fo...> - 2012-08-08 18:40:59
|
On Wed, Aug 08, 2012 at 08:29:31AM +0200, Nicolas CARRIER wrote: > I think there is a room for improvement in a lot of places. > In fact I'd like to achieve a entire translation to have a global overview > and detect common patterns. > > I'll be doing a second pass, more precise, after the last .po is translated > which will take some time. Only 60% is translated so far. Then I think I'll > have some questions to post to the ml for certain unclear portions. That sounds great! And if you find common patterns, even in your first pass, feel free to modify the source code strings, if that will help you. I tried to make things as simple as I could, but there are some places where C++ iostreams breaks the string up. I used string_vprintf() to turn most of those into printf-style format strings, where appropriate. - Chris |
|
From: Nicolas C. <nic...@pa...> - 2012-08-08 06:57:43
|
On 07/08/2012 21:42, Chris Frey wrote: > On Mon, Aug 06, 2012 at 08:41:30PM +0200, Nicolas CARRIER wrote: >> Hello, >> Please find as an attachment the fifth fr.po file. >> I still couldn't test it, because I wasn't able to compile Barry from >> scratch. >> I'm working on the last file, but it contains half of the strings to >> translate :/ >> Not sure I will be able to finish this week... > > Thanks again for all your patches. I've applied them all, and did a small > bit of testing. Looks pretty good to me... although some strings turn out > to be a little long. I don't know how flexible the translations could > be in those situations. I think there is a room for improvement in a lot of places. In fact I'd like to achieve a entire translation to have a global overview and detect common patterns. I'll be doing a second pass, more precise, after the last .po is translated which will take some time. Only 60% is translated so far. Then I think I'll have some questions to post to the ml for certain unclear portions. > > Let me know if you continue to have build trouble. It would be good to > have you test the translations as well. Yes, I'll look a solution for these problems, once a first draft of the last translation is done. There is a lot of translations which need testing in real condition. > > Also, if some strings are marked "fuzzy", please remove that tag if > possible. Fuzzy strings don't always come through in the final program, > and the english version shows instead. The fuzzy marker is generally > there to show translators what needs work, since the last time the source > code was changed. Ok I though it was used to mark "unsure" translations. I will remove with future corrections. > > Thanks, > - Chris > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Barry-devel mailing list > Bar...@li... > https://lists.sourceforge.net/lists/listinfo/barry-devel > -- Nicolas CARRIER - 6081 - 2ème centre |
|
From: Chris F. <cd...@fo...> - 2012-08-07 19:42:35
|
On Mon, Aug 06, 2012 at 08:41:30PM +0200, Nicolas CARRIER wrote: > Hello, > Please find as an attachment the fifth fr.po file. > I still couldn't test it, because I wasn't able to compile Barry from > scratch. > I'm working on the last file, but it contains half of the strings to > translate :/ > Not sure I will be able to finish this week... Thanks again for all your patches. I've applied them all, and did a small bit of testing. Looks pretty good to me... although some strings turn out to be a little long. I don't know how flexible the translations could be in those situations. Let me know if you continue to have build trouble. It would be good to have you test the translations as well. Also, if some strings are marked "fuzzy", please remove that tag if possible. Fuzzy strings don't always come through in the final program, and the english version shows instead. The fuzzy marker is generally there to show translators what needs work, since the last time the source code was changed. Thanks, - Chris |
|
From: Chris F. <cd...@fo...> - 2012-08-07 18:28:00
|
On Sun, Aug 05, 2012 at 07:33:36PM +0200, Nicolas CARRIER wrote: > Hi ! > I had some time the week-end, so I started to work on French > translations for Barry. > I've worked on the 4 first smallest .po files on the 6 which are present > in the Barry project. > I'm working on the last 2, but as they are much longer, it will take > some more time... > > It's the first time I work on a translation, so please, be kind ^^ Thanks very much! > PS : I couldn't test the result, because I couldn't compile barry > successfully, when issuing a : > make clean > ./configure --enable-gui > make > > I've got the following error : > /usr/bin/ld: cannot find -lbarrybackup > > Any idea ? You need libtar installed to build the barrybackup library, which is needed for the backup GUI. I don't know what the output of your configure command is, but I'm guessing this might be it. If not, I'll need to see the output, and the config.log. Thanks, - Chris |
|
From: Nicolas C. <car...@gm...> - 2012-08-05 17:37:19
|
The last one for now. Both four patches apply to the current master's HEAD. |
|
From: Nicolas C. <car...@gm...> - 2012-08-05 17:36:16
Attachments:
0003-po-french-translation-for-gui.patch
|
|
From: Nicolas C. <car...@gm...> - 2012-08-05 17:35:33
|
The second translation, on 4 completed. |
|
From: Nicolas C. <car...@gm...> - 2012-08-05 17:33:49
|
Hi ! I had some time the week-end, so I started to work on French translations for Barry. I've worked on the 4 first smallest .po files on the 6 which are present in the Barry project. I'm working on the last 2, but as they are much longer, it will take some more time... It's the first time I work on a translation, so please, be kind ^^ Hope it will be of any help. PS : I couldn't test the result, because I couldn't compile barry successfully, when issuing a : make clean ./configure --enable-gui make I've got the following error : /usr/bin/ld: cannot find -lbarrybackup Any idea ? |
|
From: Thibi <thi...@gm...> - 2012-07-28 04:15:21
|
Chris, I have to apologise for the sloppiness of my earlier message. I was pushing the hours a bit and was flipping around between various versions of the toolkit and misplaced which one I was posting the log of. Thanks for pointing out the inclusion of libopensync in the snapshot! By using it, it removed the need for the change to the $PKG_CONFIG detection and successfully allowed me to compile both barry and libopensync without any downgrading as well. :) It seems that Arch Linux's libopensync 0.39 is fairly outdated, as it couldn't be built from source until I downgraded glib2 to 2.28. Now to set up this PKGBUILD. :) ~Thibi |
|
From: Chris F. <cd...@fo...> - 2012-07-27 07:15:16
|
Hi, I've just finished a few large commits, which convert strings to translatable gettext versions. This covers the library itself, command line tools, the backup gui, the plugins, and the desktop. The files to tackle are as follows, based on the root of the Barry git tree. Note that both fr.po and es.po, though mostly empty in some spots, have already been created. If you're translating those languages, start there. po/barry.pot gui/po/barry-backup.pot desktop/po/barrydesktop.pot desktop/po-osyncwrap/barryosyncwrap.pot opensync-plugin/po/barry-opensync-plugin.pot opensync-plugin-0.4x/po/barry-opensync-plugin-0-4x.pot Please post the mailing list if you claim a language, so you there is not duplication of effort, or coordinate with whoever voluteers. I'd really appreciate feedback from the translators. I tried to add notes where I thought things might be confusing. If there is something especially difficult, PLEASE let me know instead of banging your head against the wall. If changes need to be made, I'd rather make them early, while you're still working on it, than later. And if you have any questions along the way, please ask. Thanks! - Chris |
|
From: Chris F. <cd...@fo...> - 2012-07-25 21:51:26
|
On Wed, Jul 25, 2012 at 12:07:16PM -0700, Thibi wrote:
> Hello!
>
> I'm in the process of setting up a PKGBUILD for Arch Linux with the
> desktop and opensync-plugin-0.4x switches enabled, and I'm running
> into an issue of getting opensync-plugin-0.4x to make.
Hi Thibi!
Glad to hear it. Thank you for your effort.
> Are the recommended toolkit versions on the website incorrect for 0.17.1?
The dependencies on the website may have more than are needed for 0.17.1,
since the website is updated for version 0.18.3, but if you have them all
installed, 0.17.1 should build as well.
I see you're really building version 0.18.3, which is what I'd recommend. :-)
> If it makes any difference, I've replaced all instances of $PKG_CONFIG
> looking for "libopensync1" to "libopensync" to allow pkg-config to
> locate it successfully.
Why do you need to change the pkg-config name?
Which version of opensync are you building against? If you really want
to use the 0.4x plugin, you should use the latest opensync as well,
or you will run into linking and API changes that won't compile.
Plus, bugs have been fixed in the latest opensync.
The latest opensync is available in the binary-meta tarball in the
Barry file download area. The binary-meta tarball contains the source
code which the binary packages are based on, not just Barry's source,
but also opensync and plugins.
> Truncated, it ends up with this error:
>
> >> src/Makefile.am:26: Libtool library used but `LIBTOOL' is undefined
> >> src/Makefile.am:26:
> >> src/Makefile.am:26: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
> >> src/Makefile.am:26: to `configure.ac' and run `aclocal' and `autoconf' again.
> >> make[2]: *** [Makefile.in] Error 1
In the verbose log, I saw:
> >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x'
> >>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run aclocal-1.11
> >>> /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing: line 52: aclocal-1.11: command not found
> >>> WARNING: `aclocal-1.11' is missing on your system. You should only need it if
> >>> you modified `acinclude.m4' or `configure.ac'. You might want
> >>> to install the `Automake' and `Perl' packages. Grab them from
> >>> any GNU archive site.
> >>> cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run automake-1.11 --foreign
> >>> /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing: line 52: automake-1.11: command not found
> >>> WARNING: `automake-1.11' is missing on your system. You should only need it if
> >>> you modified `Makefile.am', `acinclude.m4' or `configure.ac'.
> >>> You might want to install the `Automake' and `Perl' packages.
> >>> Grab them from any GNU archive site.
> >>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run autoconf
> >>> aclocal.m4:16: warning: this file was generated for autoconf 2.67.
> >>> You have another version of autoconf. It may work, but is not guaranteed to.
> >>> If you have problems, you may need to regenerate the build system entirely.
> >>> To do so, use the procedure documented by the package, typically `autoreconf'.
> >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
> >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
> >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from...
> >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from...
> >>> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from...
> >>> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from...
> >>> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from...
> >>> m4/libtool.m4:138: _LT_SETUP is expanded from...
> >>> m4/libtool.m4:67: LT_INIT is expanded from...
> >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from...
> >>> configure.ac:17: the top level
> >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body
This concerns me, as it appears that during your build, the makefiles are
trying to regenerate themselves, and maybe you don't have all the required
tools. When configure or scripts start barfing with uppercase symbols,
it's probably because there's a missing piece, and the configure script did
not get created correctly.
I would check your autotools toolchain first, and make sure you have all
the latest versions. Above, you are using automake-1.9, but here, it's
looking for aclocal 1.11 and automake 1.11.
Let me know if you have more questions.
Thanks,
- Chris
|
|
From: Chris F. <cd...@fo...> - 2012-07-25 21:34:46
|
On Wed, Jul 25, 2012 at 11:38:04AM +0100, Toby Gray wrote: > Thanks for looking at this even though I didn't get time to respond to > your first email. Is the only abi change the tr1 smart_ptr support? If > so then I was planning on seeing if your suggestion for using boost to > provide tr1 on WinCE would work, as that would certainly be cleaner. No, there were also: 1) the uint8_t to uint16_t change in ThrowJVMError() was an ABI breakage. I might have been able to get away with that, as it is protected and only used internally, but didn't chance it. 2) lib: Removing some inline member definitions on exported classes. That caused warnings in my abi checker that I wasn't comfortable with... functions added and disappearing, I think. - Chris |
|
From: Chris F. <cd...@fo...> - 2012-07-25 21:31:23
|
On Wed, Jul 25, 2012 at 11:45:19AM +0100, Toby Gray wrote: > I've also realised that I should really transform wince/README into a > doc/www/wincebuild.php file. Or would you prefer to keep WinCE support a > bit hidden until it's been in there for a while? > > I should also probably create a doc/www/androidbuild.php and > doc/www/qnxbuild.php, as I've just realized that they are missing. No no, don't wait. The more docs the better, and in HTML, even better. :-) I update the official website manually anyhow, so git documentation can run ahead of the website until we're ready. - Chris |
|
From: Chris F. <cd...@fo...> - 2012-07-25 21:29:28
|
On Wed, Jul 25, 2012 at 01:10:24PM +0100, Toby Gray wrote:
> On 17/07/12 04:56, Chris Frey wrote:
> > I think it's better to go in the other direction. For systems that don't
> > have tr1, then:
> >
> > namespace std {
> > namespace tr1 {
> > using boost::shared_ptr;
> > }
> > }
> >
> > I hope that's possible. :-) It might even prevent the need to bump to 0.19.
>
> I've asked a C++ standards guru and adding to namespace std is undefined
> behaviour. From the C++11 standard section 17.6.4.2.1:
> " The behavior of a C++ program is undefined if it adds declarations or
> definitions to namespace std or to a
> namespace within namespace std unless otherwise specified"
>
> However the WinCE build needs to use STLPort anyway for the
> implementation of the std namespace. STLPORT does a #define on "std" so
> this should all be ok. I'll let you know once I've tried it and updated
> my branch if it does work.
Thanks. :-) If that doesn't work, maybe we need to create our own
Barry::tr1 namespace, and just import std or boost into it. I'm sure
that would be a v0.19.0 ABI change though.
> Regarding the struct vs. class, there's a question on Stackflow about
> what the standard says, which seems to conclude that it shouldn't matter:
> http://stackoverflow.com/questions/4866425/mixing-class-and-struct
>
> The important part though is that the name mangling that Visual Studios
> does uses 'U' to mean struct and 'V' to mean class (
> http://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B_Name_Mangling#Data_Type).
I've tested those two changes, and it doesn't affect ABI compatibility
on Linux, so I've merged those patches as well.
Thanks!
- Chris
|
|
From: Thibi <thi...@gm...> - 2012-07-25 19:08:05
|
Hello! I'm in the process of setting up a PKGBUILD for Arch Linux with the desktop and opensync-plugin-0.4x switches enabled, and I'm running into an issue of getting opensync-plugin-0.4x to make. Are the recommended toolkit versions on the website incorrect for 0.17.1? If it makes any difference, I've replaced all instances of $PKG_CONFIG looking for "libopensync1" to "libopensync" to allow pkg-config to locate it successfully. I modified the standard barry AUR PKGBUILD < https://aur.archlinux.org/packages/ba/barry/PKGBUILD > to export the recommended toolkit versioning according to the website to look thusly: > build() { > export ACLOCAL=/opt/automake-1.9/bin/aclocal > export AUTOCONF=/opt/autoconf/2.67/bin/autoconf > export AUTOMAKE=/opt/automake-1.9/bin/automake > export AC_PROG_LIBTOOL=/opt/libtool/1.5.22/bin/libtool > > # Apply patches > cd $srcdir/$pkgname-$pkgver/src > patch -p0 < ../../tarfile-ops-nt.cc.patch > > # Resolve pkg-config output difference > find $srcdir/$pkgname-$pkgver/opensync-plugin-0.4x/ -type f -exec sed -i 's/libopensync1/libopensync/g' {} + > > # Build the package > cd $srcdir/$pkgname-$pkgver > ./configure --prefix=/usr --enable-gui\ > --enable-desktop --enable-opensync-plugin-4x --libexec=/usr/lib > > make || return 1 > make DESTDIR=$pkgdir install > > # Remove libtool files > find "$pkgdir/" -name "*.la" -exec rm {} \; > } Truncated, it ends up with this error: >> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/test' >> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o libtest libtest-date.o libtest-data.o libtest-libtest.o ../src/libbarry.la ../src/libbarrysync.la -lglib-2.0 ../src/libbarrybackup.la -lpthread >> libtool: link: g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/libtest libtest-date.o libtest-data.o libtest-libtest.o ../src/.libs/libbarry.so ../src/.libs/libbarrysync.so -lglib-2.0 ../src/.libs/libbarrybackup.so -lpthread >> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/test' >> Making all in opensync-plugin-0.4x >> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >> CDPATH="${ZSH_VERSION+.}:" && cd . && /opt/automake-1.9/bin/aclocal >> cd . && /opt/automake-1.9/bin/automake --foreign >> Useless use of /d modifier in transliteration operator at /opt/automake-1.9/share/automake-1.9/Automake/Wrap.pm line 60. >> src/Makefile.am:26: Libtool library used but `LIBTOOL' is undefined >> src/Makefile.am:26: >> src/Makefile.am:26: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL' >> src/Makefile.am:26: to `configure.ac' and run `aclocal' and `autoconf' again. >> make[2]: *** [Makefile.in] Error 1 >> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3' >> make: *** [all] Error 2 The following is the build log if I go with my normal system toolkit versions: (autoconf=2.69, automake=1.12.2, libtool=2.4.2, gcc=4.7.1) >>> ==> Starting build()... >>> patching file tarfile-ops-nt.cc >>> checking for a BSD-compatible install... /usr/bin/install -c >>> checking whether build environment is sane... yes >>> checking for a thread-safe mkdir -p... /bin/mkdir -p >>> checking for gawk... gawk >>> checking whether make sets $(MAKE)... yes >>> checking for style of include used by make... GNU >>> checking for gcc... gcc >>> checking whether the C compiler works... yes >>> checking for C compiler default output file name... a.out >>> checking for suffix of executables... >>> checking whether we are cross compiling... no >>> checking for suffix of object files... o >>> checking whether we are using the GNU C compiler... yes >>> checking whether gcc accepts -g... yes >>> checking for gcc option to accept ISO C89... none needed >>> checking dependency style of gcc... gcc3 >>> checking how to run the C preprocessor... gcc -E >>> checking for grep that handles long lines and -e... /usr/bin/grep >>> checking for egrep... /usr/bin/grep -E >>> checking for ANSI C header files... yes >>> checking for sys/types.h... yes >>> checking for sys/stat.h... yes >>> checking for stdlib.h... yes >>> checking for string.h... yes >>> checking for memory.h... yes >>> checking for strings.h... yes >>> checking for inttypes.h... yes >>> checking for stdint.h... yes >>> checking for unistd.h... yes >>> checking minix/config.h usability... no >>> checking minix/config.h presence... no >>> checking for minix/config.h... no >>> checking whether it is safe to define __EXTENSIONS__... yes >>> checking whether NLS is requested... yes >>> checking for msgfmt... /usr/bin/msgfmt >>> checking for gmsgfmt... /usr/bin/msgfmt >>> checking for xgettext... /usr/bin/xgettext >>> checking for msgmerge... /usr/bin/msgmerge >>> checking build system type... i686-pc-linux-gnu >>> checking host system type... i686-pc-linux-gnu >>> checking for ld used by GCC... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking for shared library run path origin... done >>> checking for CFPreferencesCopyAppValue... no >>> checking for CFLocaleCopyCurrent... no >>> checking for GNU gettext in libc... yes >>> checking whether to use NLS... yes >>> checking where the gettext function comes from... libc >>> checking for gcc... (cached) gcc >>> checking whether we are using the GNU C compiler... (cached) yes >>> checking whether gcc accepts -g... (cached) yes >>> checking for gcc option to accept ISO C89... (cached) none needed >>> checking dependency style of gcc... (cached) gcc3 >>> checking for g++... g++ >>> checking whether we are using the GNU C++ compiler... yes >>> checking whether g++ accepts -g... yes >>> checking dependency style of g++... gcc3 >>> checking whether make sets $(MAKE)... (cached) yes >>> checking for a sed that does not truncate output... /bin/sed >>> checking for fgrep... /usr/bin/grep -F >>> checking for ld used by gcc... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>> checking whether ln -s works... yes >>> checking the maximum length of command line arguments... 1572864 >>> checking whether the shell understands some XSI constructs... yes >>> checking whether the shell understands "+="... yes >>> checking for /usr/bin/ld option to reload object files... -r >>> checking for objdump... objdump >>> checking how to recognize dependent libraries... pass_all >>> checking for ar... ar >>> checking for strip... strip >>> checking for ranlib... ranlib >>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>> checking for dlfcn.h... yes >>> checking whether we are using the GNU C++ compiler... (cached) yes >>> checking whether g++ accepts -g... (cached) yes >>> checking dependency style of g++... (cached) gcc3 >>> checking how to run the C++ preprocessor... g++ -E >>> checking for objdir... .libs >>> checking if gcc supports -fno-rtti -fno-exceptions... no >>> checking for gcc option to produce PIC... -fPIC -DPIC >>> checking if gcc PIC flag -fPIC -DPIC works... yes >>> checking if gcc static flag -static works... yes >>> checking if gcc supports -c -o file.o... yes >>> checking if gcc supports -c -o file.o... (cached) yes >>> checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes >>> checking whether -lc should be explicitly linked in... no >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether stripping libraries is possible... yes >>> checking if libtool supports shared libraries... yes >>> checking whether to build shared libraries... yes >>> checking whether to build static libraries... yes >>> checking for ld used by g++... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking for g++ option to produce PIC... -fPIC -DPIC >>> checking if g++ PIC flag -fPIC -DPIC works... yes >>> checking if g++ static flag -static works... yes >>> checking if g++ supports -c -o file.o... yes >>> checking if g++ supports -c -o file.o... (cached) yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether the C compiler accepts the -fvisibility=hidden flag... yes >>> checking whether the C++ compiler accepts the -fvisibility=hidden flag... yes >>> Guessing libtar location... may not compile... >>> checking for tar_open in -ltar... yes >>> configure: Found libtar, enabling libbarrybackup >>> Guessing zlib location... may not compile... >>> checking for pkg-config... /usr/bin/pkg-config >>> checking pkg-config is at least version 0.9.0... yes >>> checking for LIBUSB_0_1... yes >>> checking for LIBUSB_1_0... yes >>> checking for which USB library to use... libusb-1.0 >>> configure: using BOOST library... no >>> checking for FUSE... yes >>> checking for SDL... yes >>> checking for GLIB2... yes >>> checking for pthread_create in -lpthread... yes >>> checking for getpwuid... yes >>> checking for bind... yes >>> checking for crc32 in -lz... yes >>> checking for LIBXMLXX... yes >>> checking for iconv... yes >>> checking for working iconv... yes >>> checking for iconv declaration... >>> extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft); >>> checking for dirent.h that defines DIR... yes >>> checking for library containing opendir... none required >>> checking for ANSI C header files... (cached) yes >>> checking assert.h usability... yes >>> checking assert.h presence... yes >>> checking for assert.h... yes >>> checking for stdint.h... (cached) yes >>> checking time.h usability... yes >>> checking time.h presence... yes >>> checking for time.h... yes >>> checking whether time.h and sys/time.h may both be included... yes >>> checking whether struct tm is in sys/time.h or time.h... time.h >>> checking for working strnlen... yes >>> checking for strnlen... yes >>> checking whether closedir returns void... no >>> checking whether gcc needs -traditional... no >>> checking sys/select.h usability... yes >>> checking sys/select.h presence... yes >>> checking for sys/select.h... yes >>> checking sys/socket.h usability... yes >>> checking sys/socket.h presence... yes >>> checking for sys/socket.h... yes >>> checking types of arguments for select... int,fd_set *,struct timeval * >>> checking for bzero... yes >>> checking for gettimeofday... yes >>> checking for memset... yes >>> checking for select... yes >>> checking for strcasecmp... yes >>> checking for strchr... yes >>> checking for strerror... yes >>> checking for strtol... yes >>> checking for strtoul... yes >>> checking whether byte ordering is bigendian... no >>> configure: creating ./config.status >>> config.status: creating Makefile >>> config.status: creating po/Makefile.in >>> config.status: creating src/Makefile >>> config.status: creating tools/Makefile >>> config.status: creating examples/Makefile >>> config.status: creating man/Makefile >>> config.status: creating test/Makefile >>> config.status: creating libbarry-18.pc >>> config.status: creating libbarrydp-18.pc >>> config.status: creating libbarryjdwp-18.pc >>> config.status: creating libbarrysync-18.pc >>> config.status: creating libbarrybackup-18.pc >>> config.status: creating libbarryalx-18.pc >>> config.status: creating config.h >>> config.status: config.h is unchanged >>> config.status: executing depfiles commands >>> config.status: executing po-directories commands >>> config.status: creating po/POTFILES >>> config.status: creating po/Makefile >>> config.status: executing libtool commands >>> === configuring in opensync-plugin-0.4x (/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x) >>> configure: running /bin/sh ./configure --disable-option-checking '--prefix=/usr' '--enable-gui--enable-desktop' '--enable-opensync-plugin-4x' '--libexec=/usr/lib' 'CFLAGS=-march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2' 'LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro' 'CXXFLAGS=-march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2' --cache-file=/dev/null --srcdir=. >>> checking for a BSD-compatible install... /usr/bin/install -c >>> checking whether build environment is sane... yes >>> checking for a thread-safe mkdir -p... /bin/mkdir -p >>> checking for gawk... gawk >>> checking whether make sets $(MAKE)... yes >>> checking for style of include used by make... GNU >>> checking for gcc... gcc >>> checking whether the C compiler works... yes >>> checking for C compiler default output file name... a.out >>> checking for suffix of executables... >>> checking whether we are cross compiling... no >>> checking for suffix of object files... o >>> checking whether we are using the GNU C compiler... yes >>> checking whether gcc accepts -g... yes >>> checking for gcc option to accept ISO C89... none needed >>> checking dependency style of gcc... gcc3 >>> checking for library containing strerror... none required >>> checking for gcc... (cached) gcc >>> checking whether we are using the GNU C compiler... (cached) yes >>> checking whether gcc accepts -g... (cached) yes >>> checking for gcc option to accept ISO C89... (cached) none needed >>> checking dependency style of gcc... (cached) gcc3 >>> checking for gcc... (cached) gcc >>> checking whether we are using the GNU C compiler... (cached) yes >>> checking whether gcc accepts -g... (cached) yes >>> checking for gcc option to accept ISO C89... (cached) none needed >>> checking dependency style of gcc... (cached) gcc3 >>> checking how to run the C preprocessor... gcc -E >>> checking for grep that handles long lines and -e... /usr/bin/grep >>> checking for egrep... /usr/bin/grep -E >>> checking for ANSI C header files... yes >>> checking for g++... g++ >>> checking whether we are using the GNU C++ compiler... yes >>> checking whether g++ accepts -g... yes >>> checking dependency style of g++... gcc3 >>> checking build system type... i686-pc-linux-gnu >>> checking host system type... i686-pc-linux-gnu >>> checking for a sed that does not truncate output... /bin/sed >>> checking for fgrep... /usr/bin/grep -F >>> checking for ld used by gcc... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>> checking whether ln -s works... yes >>> checking the maximum length of command line arguments... 1572864 >>> checking whether the shell understands some XSI constructs... yes >>> checking whether the shell understands "+="... yes >>> checking for /usr/bin/ld option to reload object files... -r >>> checking for objdump... objdump >>> checking how to recognize dependent libraries... pass_all >>> checking for ar... ar >>> checking for strip... strip >>> checking for ranlib... ranlib >>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>> checking for sys/types.h... yes >>> checking for sys/stat.h... yes >>> checking for stdlib.h... yes >>> checking for string.h... yes >>> checking for memory.h... yes >>> checking for strings.h... yes >>> checking for inttypes.h... yes >>> checking for stdint.h... yes >>> checking for unistd.h... yes >>> checking for dlfcn.h... yes >>> checking whether we are using the GNU C++ compiler... (cached) yes >>> checking whether g++ accepts -g... (cached) yes >>> checking dependency style of g++... (cached) gcc3 >>> checking how to run the C++ preprocessor... g++ -E >>> checking for objdir... .libs >>> checking if gcc supports -fno-rtti -fno-exceptions... no >>> checking for gcc option to produce PIC... -fPIC -DPIC >>> checking if gcc PIC flag -fPIC -DPIC works... yes >>> checking if gcc static flag -static works... yes >>> checking if gcc supports -c -o file.o... yes >>> checking if gcc supports -c -o file.o... (cached) yes >>> checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes >>> checking whether -lc should be explicitly linked in... no >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether stripping libraries is possible... yes >>> checking if libtool supports shared libraries... yes >>> checking whether to build shared libraries... yes >>> checking whether to build static libraries... no >>> checking for ld used by g++... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking for g++ option to produce PIC... -fPIC -DPIC >>> checking if g++ PIC flag -fPIC -DPIC works... yes >>> checking if g++ static flag -static works... yes >>> checking if g++ supports -c -o file.o... yes >>> checking if g++ supports -c -o file.o... (cached) yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether the C compiler accepts the -fvisibility=hidden flag... yes >>> checking whether the C++ compiler accepts the -fvisibility=hidden flag... yes >>> checking for pkg-config... /usr/bin/pkg-config >>> checking pkg-config is at least version 0.9.0... yes >>> checking for GLIB2... yes >>> checking for OPENSYNC4X... yes >>> checking for BARRY... yes >>> checking for BARRYSYNC... yes >>> configure: creating ./config.status >>> config.status: creating Makefile >>> config.status: creating src/Makefile >>> config.status: creating config.h >>> config.status: config.h is unchanged >>> config.status: executing depfiles commands >>> config.status: executing libtool commands >>> make all-recursive >>> make[1]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3' >>> Making all in po >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/po' >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/po' >>> Making all in . >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3' >>> rm -f ./barry ./barry18 >>> ln -fs ./src ./barry >>> ln -fs . ./barry18 >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3' >>> Making all in src >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/src' >>> /bin/sh ../libtool --tag=CXX --mode=compile g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I.. -I/usr/include/libusb-1.0 -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT libbarrybackup_la-tarfile-ops-nt.lo -MD -MP -MF .deps/libbarrybackup_la-tarfile-ops-nt.Tpo -c -o libbarrybackup_la-tarfile-ops-nt.lo `test -f 'tarfile-ops-nt.cc' || echo './'`tarfile-ops-nt.cc >>> libtool: compile: g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I.. -I/usr/include/libusb-1.0 -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT libbarrybackup_la-tarfile-ops-nt.lo -MD -MP -MF .deps/libbarrybackup_la-tarfile-ops-nt.Tpo -c tarfile-ops-nt.cc -fPIC -DPIC -o .libs/libbarrybackup_la-tarfile-ops-nt.o >>> libtool: compile: g++ -DLOCALEDIR=\"/usr/share/locale\" -DHAVE_CONFIG_H -I.. -I/usr/include/libusb-1.0 -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT libbarrybackup_la-tarfile-ops-nt.lo -MD -MP -MF .deps/libbarrybackup_la-tarfile-ops-nt.Tpo -c tarfile-ops-nt.cc -o libbarrybackup_la-tarfile-ops-nt.o >/dev/null 2>&1 >>> mv -f .deps/libbarrybackup_la-tarfile-ops-nt.Tpo .deps/libbarrybackup_la-tarfile-ops-nt.Plo >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -fno-strict-aliasing -g -D__BARRY_LIBRARY_BUILD__ -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -version-info 18:3:0 -Wl,-O1,--sort-common,--as-needed,-z,relro -o libbarrybackup.la -rpath /usr/lib libbarrybackup_la-tarfile.lo libbarrybackup_la-tarfile-ops-nt.lo libbarrybackup_la-backup.lo libbarrybackup_la-restore.lo libbarry.la -ltar -lz -lpthread >>> libtool: link: rm -fr .libs/libbarrybackup.a .libs/libbarrybackup.la .libs/libbarrybackup.lai .libs/libbarrybackup.so .libs/libbarrybackup.so.18 .libs/libbarrybackup.so.18.0.3 >>> libtool: link: g++ -shared -nostdlib /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/../../../crti.o /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/crtbeginS.o .libs/libbarrybackup_la-tarfile.o .libs/libbarrybackup_la-tarfile-ops-nt.o .libs/libbarrybackup_la-backup.o .libs/libbarrybackup_la-restore.o -Wl,-rpath -Wl,/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/src/.libs ./.libs/libbarry.so -ltar -lz -lpthread -L/usr/lib/gcc/i686-pc-linux-gnu/4.7.1 -L/usr/lib/gcc/i686-pc-linux-gnu/4.7.1/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/crtendS.o /usr/lib/gcc/i686-pc-linux-gnu/4.7.1/../../../crtn.o -march=i686 -mtune=generic -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-soname -Wl,libbarrybackup.so.18 -o .libs/libbarrybackup.so.18.0.3 >>> libtool: link: (cd ".libs" && rm -f "libbarrybackup.so.18" && ln -s "libbarrybackup.so.18.0.3" "libbarrybackup.so.18") >>> libtool: link: (cd ".libs" && rm -f "libbarrybackup.so" && ln -s "libbarrybackup.so.18.0.3" "libbarrybackup.so") >>> libtool: link: ar cru .libs/libbarrybackup.a libbarrybackup_la-tarfile.o libbarrybackup_la-tarfile-ops-nt.o libbarrybackup_la-backup.o libbarrybackup_la-restore.o >>> libtool: link: ranlib .libs/libbarrybackup.a >>> libtool: link: ( cd ".libs" && rm -f "libbarrybackup.la" && ln -s "../libbarrybackup.la" "libbarrybackup.la" ) >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/src' >>> Making all in tools >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/tools' >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o btool btool-btool.o ../src/libbarry.la libutil.a libboostwrap.a -lusb-1.0 ../src/libbarrysync.la -lglib-2.0 ../src/libbarrybackup.la -lpthread >>> libtool: link: g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/btool btool-btool.o ../src/.libs/libbarry.so libutil.a libboostwrap.a -lusb-1.0 ../src/.libs/libbarrysync.so -lglib-2.0 ../src/.libs/libbarrybackup.so -lpthread >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o btardump btardump-btardump.o ../src/libbarry.la -lusb-1.0 ../src/libbarrybackup.la ../src/libbarrysync.la -lglib-2.0 -lpthread >>> libtool: link: g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/btardump btardump-btardump.o ../src/.libs/libbarry.so -lusb-1.0 ../src/.libs/libbarrybackup.so ../src/.libs/libbarrysync.so -lglib-2.0 -lpthread >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o btarcmp btarcmp-btarcmp.o ../src/libbarry.la ../src/libbarrybackup.la libutil.a -lusb-1.0 -lpthread >>> libtool: link: g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/btarcmp btarcmp-btarcmp.o ../src/.libs/libbarry.so ../src/.libs/libbarrybackup.so libutil.a -lusb-1.0 -lpthread >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -D__BARRY_SYNC_MODE__ -Wall -g -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o bio bio-bio.o ../src/libbarry.la ../src/libbarrysync.la -lglib-2.0 ../src/libbarrybackup.la libutil.a libboostwrap.a -lusb-1.0 -lpthread >>> libtool: link: g++ -D__BARRY_SYNC_MODE__ -Wall -g -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/bio bio-bio.o ../src/.libs/libbarry.so ../src/.libs/libbarrysync.so -lglib-2.0 ../src/.libs/libbarrybackup.so libutil.a libboostwrap.a -lusb-1.0 -lpthread >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/tools' >>> Making all in examples >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/examples' >>> make[2]: Nothing to be done for `all'. >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/examples' >>> Making all in man >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/man' >>> make[2]: Nothing to be done for `all'. >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/man' >>> Making all in test >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/test' >>> /bin/sh ../libtool --tag=CXX --mode=link g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1,--sort-common,--as-needed,-z,relro -o libtest libtest-date.o libtest-data.o libtest-libtest.o ../src/libbarry.la ../src/libbarrysync.la -lglib-2.0 ../src/libbarrybackup.la -lpthread >>> libtool: link: g++ -Wall -g -D__BARRY_SYNC_MODE__ -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -D__BARRY_BACKUP_MODE__ -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -o .libs/libtest libtest-date.o libtest-data.o libtest-libtest.o ../src/.libs/libbarry.so ../src/.libs/libbarrysync.so -lglib-2.0 ../src/.libs/libbarrybackup.so -lpthread >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/test' >>> Making all in opensync-plugin-0.4x >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run aclocal-1.11 >>> /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing: line 52: aclocal-1.11: command not found >>> WARNING: `aclocal-1.11' is missing on your system. You should only need it if >>> you modified `acinclude.m4' or `configure.ac'. You might want >>> to install the `Automake' and `Perl' packages. Grab them from >>> any GNU archive site. >>> cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run automake-1.11 --foreign >>> /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing: line 52: automake-1.11: command not found >>> WARNING: `automake-1.11' is missing on your system. You should only need it if >>> you modified `Makefile.am', `acinclude.m4' or `configure.ac'. >>> You might want to install the `Automake' and `Perl' packages. >>> Grab them from any GNU archive site. >>> CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run autoconf >>> aclocal.m4:16: warning: this file was generated for autoconf 2.67. >>> You have another version of autoconf. It may work, but is not guaranteed to. >>> If you have problems, you may need to regenerate the build system entirely. >>> To do so, use the procedure documented by the package, typically `autoreconf'. >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... >>> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from... >>> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from... >>> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... >>> m4/libtool.m4:5360: _LT_LANG_CXX_CONFIG is expanded from... >>> m4/libtool.m4:785: _LT_LANG is expanded from... >>> m4/libtool.m4:768: LT_LANG is expanded from... >>> m4/libtool.m4:796: _LT_LANG_DEFAULT_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> /bin/sh ./config.status --recheck >>> running CONFIG_SHELL=/bin/sh /bin/sh ./configure --disable-option-checking --prefix=/usr --enable-gui--enable-desktop --enable-opensync-plugin-4x --libexec=/usr/lib CFLAGS=-march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 LDFLAGS=-Wl,-O1,--sort-common,--as-needed,-z,relro CXXFLAGS=-march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 --cache-file=/dev/null --srcdir=. PKG_CONFIG_PATH=/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3:/usr/lib/pkgconfig:/opt/qt/lib/pkgconfig --no-create --no-recursion >>> checking for a BSD-compatible install... /usr/bin/install -c >>> checking whether build environment is sane... yes >>> checking for a thread-safe mkdir -p... /bin/mkdir -p >>> checking for gawk... gawk >>> checking whether make sets $(MAKE)... yes >>> checking for style of include used by make... GNU >>> checking for gcc... gcc >>> checking whether the C compiler works... yes >>> checking for C compiler default output file name... a.out >>> checking for suffix of executables... >>> checking whether we are cross compiling... no >>> checking for suffix of object files... o >>> checking whether we are using the GNU C compiler... yes >>> checking whether gcc accepts -g... yes >>> checking for gcc option to accept ISO C89... none needed >>> checking dependency style of gcc... gcc3 >>> checking for library containing strerror... none required >>> checking for gcc... (cached) gcc >>> checking whether we are using the GNU C compiler... (cached) yes >>> checking whether gcc accepts -g... (cached) yes >>> checking for gcc option to accept ISO C89... (cached) none needed >>> checking dependency style of gcc... (cached) gcc3 >>> checking for gcc... (cached) gcc >>> checking whether we are using the GNU C compiler... (cached) yes >>> checking whether gcc accepts -g... (cached) yes >>> checking for gcc option to accept ISO C89... (cached) none needed >>> checking dependency style of gcc... (cached) gcc3 >>> checking how to run the C preprocessor... gcc -E >>> checking for grep that handles long lines and -e... /usr/bin/grep >>> checking for egrep... /usr/bin/grep -E >>> checking for ANSI C header files... yes >>> checking for g++... g++ >>> checking whether we are using the GNU C++ compiler... yes >>> checking whether g++ accepts -g... yes >>> checking dependency style of g++... gcc3 >>> checking build system type... i686-pc-linux-gnu >>> checking host system type... i686-pc-linux-gnu >>> checking for a sed that does not truncate output... /bin/sed >>> checking for fgrep... /usr/bin/grep -F >>> checking for ld used by gcc... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B >>> checking the name lister (/usr/bin/nm -B) interface... BSD nm >>> checking whether ln -s works... yes >>> checking the maximum length of command line arguments... 1572864 >>> checking whether the shell understands some XSI constructs... yes >>> checking whether the shell understands "+="... yes >>> checking for /usr/bin/ld option to reload object files... -r >>> checking for objdump... objdump >>> checking how to recognize dependent libraries... pass_all >>> checking for ar... ar >>> checking for strip... strip >>> checking for ranlib... ranlib >>> checking command to parse /usr/bin/nm -B output from gcc object... ok >>> checking for sys/types.h... yes >>> checking for sys/stat.h... yes >>> checking for stdlib.h... yes >>> checking for string.h... yes >>> checking for memory.h... yes >>> checking for strings.h... yes >>> checking for inttypes.h... yes >>> checking for stdint.h... yes >>> checking for unistd.h... yes >>> checking for dlfcn.h... yes >>> checking whether we are using the GNU C++ compiler... (cached) yes >>> checking whether g++ accepts -g... (cached) yes >>> checking dependency style of g++... (cached) gcc3 >>> checking how to run the C++ preprocessor... g++ -E >>> checking for objdir... .libs >>> checking if gcc supports -fno-rtti -fno-exceptions... no >>> checking for gcc option to produce PIC... -fPIC -DPIC >>> checking if gcc PIC flag -fPIC -DPIC works... yes >>> checking if gcc static flag -static works... yes >>> checking if gcc supports -c -o file.o... yes >>> checking if gcc supports -c -o file.o... (cached) yes >>> checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes >>> checking whether -lc should be explicitly linked in... no >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether stripping libraries is possible... yes >>> checking if libtool supports shared libraries... yes >>> checking whether to build shared libraries... yes >>> checking whether to build static libraries... no >>> checking for ld used by g++... /usr/bin/ld >>> checking if the linker (/usr/bin/ld) is GNU ld... yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking for g++ option to produce PIC... -fPIC -DPIC >>> checking if g++ PIC flag -fPIC -DPIC works... yes >>> checking if g++ static flag -static works... yes >>> checking if g++ supports -c -o file.o... yes >>> checking if g++ supports -c -o file.o... (cached) yes >>> checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes >>> checking dynamic linker characteristics... GNU/Linux ld.so >>> checking how to hardcode library paths into programs... immediate >>> checking whether the C compiler accepts the -fvisibility=hidden flag... yes >>> checking whether the C++ compiler accepts the -fvisibility=hidden flag... yes >>> checking for pkg-config... /usr/bin/pkg-config >>> checking pkg-config is at least version 0.9.0... yes >>> checking for GLIB2... yes >>> checking for OPENSYNC4X... yes >>> checking for BARRY... yes >>> checking for BARRYSYNC... yes >>> configure: creating ./config.status >>> /bin/sh ./config.status >>> config.status: creating Makefile >>> config.status: creating src/Makefile >>> config.status: creating config.h >>> config.status: config.h is unchanged >>> config.status: executing depfiles commands >>> config.status: executing libtool commands >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> make[2]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> (CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/missing --run autoheader) >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... >>> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from... >>> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:4170: _LT_LINKER_SHLIBS is expanded from... >>> m4/libtool.m4:5253: _LT_LANG_C_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> configure.ac:17: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body >>> ../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from... >>> ../../lib/autoconf/general.m4:2661: _AC_LINK_IFELSE is expanded from... >>> ../../lib/autoconf/general.m4:2678: AC_LINK_IFELSE is expanded from... >>> m4/libtool.m4:1022: _LT_SYS_MODULE_PATH_AIX is expanded from... >>> m4/libtool.m4:5360: _LT_LANG_CXX_CONFIG is expanded from... >>> m4/libtool.m4:785: _LT_LANG is expanded from... >>> m4/libtool.m4:768: LT_LANG is expanded from... >>> m4/libtool.m4:796: _LT_LANG_DEFAULT_CONFIG is expanded from... >>> m4/libtool.m4:138: _LT_SETUP is expanded from... >>> m4/libtool.m4:67: LT_INIT is expanded from... >>> m4/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... >>> configure.ac:17: the top level >>> rm -f stamp-h1 >>> touch config.h.in >>> cd . && /bin/sh ./config.status config.h >>> config.status: creating config.h >>> config.status: config.h is unchanged >>> make all-recursive >>> make[3]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> Making all in src >>> make[4]: Entering directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/src' >>> /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libopensync1 -I/usr/include/barry18 -I/usr/include/barry18 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Werror -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT barry_sync.lo -MD -MP -MF .deps/barry_sync.Tpo -c -o barry_sync.lo barry_sync.cc >>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/libopensync1 -I/usr/include/barry18 -I/usr/include/barry18 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Werror -D__BARRY_HAVE_GCCVISIBILITY__ -fvisibility=hidden -march=i686 -mtune=generic -O2 -pipe -fstack-protector --param=ssp-buffer-size=4 -D_FORTIFY_SOURCE=2 -MT barry_sync.lo -MD -MP -MF .deps/barry_sync.Tpo -c barry_sync.cc -fPIC -DPIC -o .libs/barry_sync.o >>> barry_sync.cc: In function ‘osync_bool get_sync_info(OSyncPluginEnv*, OSyncError**)’: >>> barry_sync.cc:1112:53: error: ‘osync_plugin_set_initialize_func’ was not declared in this scope >>> barry_sync.cc:1113:49: error: ‘osync_plugin_set_finalize_func’ was not declared in this scope >>> barry_sync.cc:1114:49: error: ‘osync_plugin_set_discover_func’ was not declared in this scope >>> make[4]: *** [barry_sync.lo] Error 1 >>> make[4]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x/src' >>> make[3]: *** [all-recursive] Error 1 >>> make[3]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> make[2]: *** [all] Error 2 >>> make[2]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3/opensync-plugin-0.4x' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory `/tmp/yaourt-tmp-user/aur-barry/src/barry-0.18.3' >>> make: *** [all] Error 2 Thank you for your time and effort! ~Thibi |
|
From: Toby G. <tob...@re...> - 2012-07-25 12:39:49
|
On 17/07/12 04:56, Chris Frey wrote:
> I think it's better to go in the other direction. For systems that don't
> have tr1, then:
>
> namespace std {
> namespace tr1 {
> using boost::shared_ptr;
> }
> }
>
> I hope that's possible. :-) It might even prevent the need to bump to 0.19.
I've asked a C++ standards guru and adding to namespace std is undefined
behaviour. From the C++11 standard section 17.6.4.2.1:
" The behavior of a C++ program is undefined if it adds declarations or
definitions to namespace std or to a
namespace within namespace std unless otherwise specified"
However the WinCE build needs to use STLPort anyway for the
implementation of the std namespace. STLPORT does a #define on "std" so
this should all be ok. I'll let you know once I've tried it and updated
my branch if it does work.
Regarding the struct vs. class, there's a question on Stackflow about
what the standard says, which seems to conclude that it shouldn't matter:
http://stackoverflow.com/questions/4866425/mixing-class-and-struct
The important part though is that the name mangling that Visual Studios
does uses 'U' to mean struct and 'V' to mean class (
http://en.wikipedia.org/wiki/Microsoft_Visual_C%2B%2B_Name_Mangling#Data_Type).
Regards,
Toby
|
|
From: Toby G. <tob...@re...> - 2012-07-25 10:45:30
|
On 17/07/12 04:56, Chris Frey wrote: > On Mon, Jul 16, 2012 at 12:10:28PM +0100, Toby Gray wrote: >> Hi, >> >> I've been working on a port of Barry to WinCE. It's currently sitting in >> the "wince" branch on my github: >> https://github.com/tobygray/barry/tree/wince > Thanks Toby! Looks like a fair bit of code... I'll probably have more > comments after I review it more closely. Thank you for taking the time to review it. As you've probably noticed already I'm a bit busy at the moment so there's no rush to get it reviewed. >> The main commit which adds WinCE support is >> https://github.com/tobygray/barry/commit/d660a40f21b823510e5b81113f20fe4af3c3974a. >> This adds a wince directory in the root to contain the build files and >> implementations of some functions not present on WinCE, such as getopt and >> sleep. I have a feeling that these headers and source code should probably >> be moved into /src, to go near pre-existing support code such as >> getpwuidandroid.cc. Would that make sense? >> >> I have already done similarily for configfile.cc, splitting it up into >> common code, code for unix systems and code for win32 systems in >> https://github.com/tobygray/barry/commit/36131b090c3d6c1c34af441b40868b3b094fa66b > With all the headers in wince/, I'm tempted to try to keep wince-specific > code in its own directory, since it will likely be larger than a simple > file here or there like android. Ok. I'm happy to keep it separate as well. > None of Barry is specifically written with '/' vs. '\' in mind, so you > kind of have your work cut out for you, in those spots. :-) Fortunately, > most of that code is in the GUI code, I think. I would sincerely like to > keep such things as low level and out of the way as possible, so I like > what you've done with configfile.cc so far. Yes. I've currently only ported libbarry and some of the command line tools to WinCE. I've not dared to try to get any of the UI code to build yet. > > What do you think of creating a static library in wince/ which is linked > to the main library when building for Windows? Maybe that's what you're > doing already. > > >> As WinCE doesn't have tr1 support I had to change how the shared_ptr >> support in Barry was referenced. Instead of directly referencing >> tr1::shared_ptr, I changes this so that there is Barry::tr1::shared_ptr >> which is provided by boost::shared_ptr on WinCE and by tr1::shared_ptr >> on all pre-existing platforms. >> >> This was done in >> https://github.com/tobygray/barry/commit/b4a70d9f7feedaa52bebe46d78e7dce880e73b74. >> I'm not entirely happy with this, especially as it changes the external API >> for libbarry, but I couldn't think of an alternative solution. > I think it's better to go in the other direction. For systems that don't > have tr1, then: > > namespace std { > namespace tr1 { > using boost::shared_ptr; > } > } > > I hope that's possible. :-) It might even prevent the need to bump to 0.19. > > >> I added support for brawchannel to read and write the channel data over >> TCP, instead of STDIN and STDOUT as WinCE doesn't have great terminal >> support. This has made tools/brawchannel.cc a bit of a mess of #ifdef >> WIN32. I think the best thing to do is to split it into >> tools/brawchannel.cc, tools/brawchannel_unix.cc and >> tools/brawchannel_win32.cc. Does that make sense? > Yes, avoid #ifdefs if at all possible, please. :-) Ok. I'll rework that then. I've also realised that I should really transform wince/README into a doc/www/wincebuild.php file. Or would you prefer to keep WinCE support a bit hidden until it's been in there for a while? I should also probably create a doc/www/androidbuild.php and doc/www/qnxbuild.php, as I've just realized that they are missing. Regards, Toby |
|
From: Toby G. <tob...@re...> - 2012-07-25 10:38:16
|
On 21/07/12 07:46, Chris Frey wrote:
> On Mon, Jul 16, 2012 at 12:10:28PM +0100, Toby Gray wrote:
>> The rest of the commits are a combination of changes to the code to fix
>> warnings or errors from the Microsoft compiler. If the commit messages
>> aren't detailed enough for any of these then let me know and I'll fill
>> in the gaps (and update the commit messages).
> I'm merging in the obvious fixes into master, and the changes that I think
> might need to wait until version 0.19.0 (due to abi changes, etc), I've put
> in a new branch v0.19.0. Expect that branch to be rebased on master
> periodically. I'm not quite done yet.
Thanks for looking at this even though I didn't get time to respond to
your first email. Is the only abi change the tr1 smart_ptr support? If
so then I was planning on seeing if your suggestion for using boost to
provide tr1 on WinCE would work, as that would certainly be cleaner.
>
> You should be able to rebase your branch onto the v0.19.0 branch to see
> what I haven't processed yet.
>
>
> Some questions:
>
> 1)
>
> Can you explain why you need a lock() member in scoped_lock?
> The idea behind scoped_lock is to force its use in a scoped section,
> to prevent forgotten unlocks and to make the sections obvious.
>
> Was there a real need for it?
Only for the transferring of interest in a socket, which I'm hoping to
rework to avoid the need for this.
> 2)
>
> Author: Toby Gray <tob...@re...>
> Date: Thu Jun 7 15:46:53 2012 +0100
>
> lib: Fixing incorrect forward declaration of ProbeResult as a struct, it's r
> eally a class.
>
> diff --git a/src/controller.h b/src/controller.h
> index 8e3ba85..41727c7 100644
> --- a/src/controller.h
> +++ b/src/controller.h
> @@ -32,7 +32,7 @@ namespace Barry {
>
> // forward declarations
> class SocketRoutingQueue;
> -class ProbeResult;
> +struct ProbeResult;
>
> class PrivateControllerData;
>
>
> Is this a problem with the Microsoft compiler? I believe that strictly
> speaking, according to the C++ spec, class and struct can be used
> interchangeably.
It's certainly an issue with the Microsoft compiler. I can't quite
remember the issue but I think it was causing the mangled names of
either methods with ProbeResult as a parameter or the type information
(vtable etc.) for the class to not match up. I'll try to reproduce the
issue and add a bit more detail to the commit message.
Regards,
Toby
|
|
From: Toby G. <tob...@re...> - 2012-07-25 10:30:18
|
On 25/07/12 07:25, Chris Frey wrote: > On Mon, Jul 16, 2012 at 12:10:28PM +0100, Toby Gray wrote: >> I noticed a couple of issues with routing of data and sequence packets >> early on in channel setup if the device sends data to the PC quickly. I >> fixed these in >> https://github.com/tobygray/barry/commit/ebbdf4c9d5868a69d636119da354547918c70e1a >> and >> https://github.com/tobygray/barry/commit/6dff36f6c2cd1ef2c0006af2baebbf5ee0c0c291 > > I'm not overly keen on the TransferInterest() function. For one it > requires the non-scoped version of the scope_lock class, which I haven't > merged. And for another, it adds a new call point for callbacks. Both of those are good points. > Ideally, callbacks should occur from the same thread that calls DoRead, > whatever application thread is doing that main processing. I don't > think it is guaranteed that the worker thread will call TransferInterest(). > In fact, I think it is likely that it won't. That's also a very good point. > Is there a way to avoid TransferInterest completely? The application is > in control of its read thread, and so is the raw channel code, if I'm > not mistaken. Is there no way to drain the incoming queue before we > transfer interest to a callback? I did start by trying to do something similar but couldn't work out how to avoid the race between draining the incoming queue and registering the callback interest. If the registering of the callback is done first then it's possible for callbacks for new data to occur before the incoming queue is flushed. I think the alternative would be to support registering the callback before the socket is opened so that the packets can be routed correctly by the read thread while the thread opening the socket is still inside SocketZero::Open(). Unless I hear otherwise, I'll have a go at doing it this way and send an email to the list once I get some spare time. > P.S. I haven't heard much from you in response to my queries. If you're > just busy, that's ok, but if you're waiting for something from me, > please do let me know. :-) I've merged all I can so far. Sorry about taking so long to respond, I'm not waiting for anything from you, I'm just busy. I wanted to respond to your comments with suggested code fixes, but just as I think I've got time to do that something else turns up. Regards, Toby |
31 messages has been excluded from this view by a project administrator.
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X