Re: [cpp-netlib-devel] Branching to Implement HTTP 1.0

[<rhy...@gm...>]

Hi,

Always glad to see progress :-) I've checked the code under a Debian 
Linux box with Boost trunk, and it fails to compile, since pthread is 
required by Boost.System. It is fairly easy to cope with. Add this line 
to the trunk/libs/network/test/Jamfile.v2 file in the project requirements:

    <toolset>gcc:<source>pthread

Then the code compiles. But, I got linking errors, and I've got no idea 
how to settle them:

...failed gcc.link 
libs/network/test/bin/gcc-4.1.3/debug/link-static/message_transform_test...
...skipped 
<plibs/network/test/bin/gcc-4.1.3/debug/link-static>message_transform_test.passed 
for lack of 
<plibs/network/test/bin/gcc-4.1.3/debug/link-static>message_transform_test...
gcc.compile.c++ 
libs/network/test/bin/gcc-4.1.3/debug/link-static/http_1_0_test.o
gcc.link libs/network/test/bin/gcc-4.1.3/debug/link-static/http_1_0_test
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-write.o): 
In function `__write_nocancel':
(.text+0x26): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-write.o): 
In function `__write_nocancel':
(.text+0x56): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-close.o): 
In function `__close_nocancel':
(.text+0x20): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-close.o): 
In function `__close_nocancel':
(.text+0x4b): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-connect.o): 
In function `__connect':
(.text+0x23): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-connect.o):(.text+0x52): 
more undefined references to `__syscall_error' follow
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(sigaction.o): 
In function `__libc_sigaction':
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/../sysdeps/unix/sysv/linux/i386/sigaction.c:83: 
undefined reference to `_dl_sysinfo_dso'
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/../sysdeps/unix/sysv/linux/i386/sigaction.c:83: 
undefined reference to `_dl_sysinfo_dso'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(init.o): 
In function `__pthread_initialize_minimal_internal':
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/init.c:264: 
undefined reference to `__libc_setup_tls'
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/init.c:387: 
undefined reference to `_dl_init_static_tls'
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/init.c:389: 
undefined reference to `_dl_wait_lookup_done'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(pthread_create.o): 
In function `allocate_stack':
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/allocatestack.c:411: 
undefined reference to `_dl_stack_flags'
/build/buildd/glibc-2.6.1/build-tree/glibc-2.6.1/nptl/allocatestack.c:547: 
undefined reference to `_dl_stack_flags'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-read.o): 
In function `__read_nocancel':
(.text+0x26): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-read.o): 
In function `__read_nocancel':
(.text+0x56): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-open.o): 
In function `__open_nocancel':
(.text+0x26): undefined reference to `__syscall_error'
/usr/lib/gcc/i486-linux-gnu/4.1.3/../../../../lib/libpthread.a(ptw-open.o): 
In function `__open_nocancel':
(.text+0x56): undefined reference to `__syscall_error'



Dean Michael Berris wrote:
> Hi Guys,
>
> I know, it's been a while. However now I just got myself a spanking
> new machine on which I can do the development of the network library
> on -- without having to interfere with the work I do. This gives me a
> reason to 1) go home earlier and 2) develop the network library more.
>
> Now that I'm pretty much setting up the dispatcher library I've been
> working on for review in the near future (am waiting for a
> considerably important enhancement to Boost.Function to get that
> going, while it's not there yet I'm setting my eyes on low hanging
> fruit) I'm looking forward to getting some things done quickly as far
> as the network library is concerned.
>
> I certainly hope interest hasn't waned yet. I know mine hasn't, and I
> just hope we can get at least 1.0 released before the end of the year.
>
> As for the subject, I'm not an SVN expert -- do you guys know how to
> branch, switch to the branch, continue developing code there (possibly
> broken stuff), and then later merge back the changes to trunk? And
> what do you suggest for the branching convention, so that those who
> are interested in branching off and working on stuff will be able to
> do so without having to deal with too many issues later?
>
> I hope to be able to check in the (crude) HTTP 1.0 client
> implementation in a while. I'll send another email when I'm done. For
> the meantime, I'm going to be checking code into the trunk, of course
> still making sure that the tests aren't broken.
>
> Have a great day everyone (evening from here), and I certainly hope to
> hear from you soon!
>
>