Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Victor A. Wagner, Jr.
indeed..but it's NOT listed as a subproject in the main jamfile
At Sunday 2003/03/16 18:45, you wrote:
On Sun, 16 Mar 2003 18:17:19 -0700, Victor A. Wagner, Jr. wrote

> it APPEARS that some library is needed.  What this library is, I do
> NOT know.
The Jamfile under libs/filesystem/build builds a library called
libfs.  There is a mention of this in the 'Do-List' page, but
it looks like the docs need a 'build' section that describes
this.
Jeff
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr.  http://rudbek.com
The five most dangerous words in the English language:
  "There oughta be a law"
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Beman Dawes
At 08:45 PM 3/16/2003, Jeff Garland wrote:

>On Sun, 16 Mar 2003 18:17:19 -0700, Victor A. Wagner, Jr. wrote
>
>> it APPEARS that some library is needed.  What this library is, I do
>> NOT know.
>
>The Jamfile under libs/filesystem/build builds a library called
>libfs.  There is a mention of this in the 'Do-List' page, but
>it looks like the docs need a 'build' section that describes
>this.
Done. Thanks!

--Beman

___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Beman Dawes
At 08:17 PM 3/16/2003, Victor A. Wagner, Jr. wrote:

>Agreed, something is amiss.  I've read the docs several times and all 
they
>seem to say is "everything is in the template includes".
>
>"Filesystem Library components are supplied by several headers, all in
>directory boost/filesystem:"
>
>my #includes aren't failing, or doesn't the above say what it appears to
>(i.e. there are NO installation requirements for using filesystem, just
>point at the correct includes)
>
>it APPEARS that some library is needed.  What this library is, I do NOT
>know.  I can find no reference to any such in the documents, and I note, 
in
>passing, that bjam from the root of boost will build no such libraries.

Ah! The boost-root/Jamfile is missing the filesystem entry. That isn't 
showing up in regression testing, because the regression tests don't use 
the boost-root/Jamfile.

Fixed in CVS.

>So it's likely not the filesystem CODE that is broken, perhaps it is only 

>the documents.

Yes, that's a problem, too. Fixed in CVS.

Thanks,

--Beman

___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Jeff Garland
On Sun, 16 Mar 2003 18:17:19 -0700, Victor A. Wagner, Jr. wrote

> it APPEARS that some library is needed.  What this library is, I do 
> NOT know.  

The Jamfile under libs/filesystem/build builds a library called
libfs.  There is a mention of this in the 'Do-List' page, but
it looks like the docs need a 'build' section that describes 
this.

Jeff
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Victor A. Wagner, Jr.
Agreed, something is amiss.  I've read the docs several times and all they 
seem to say is "everything is in the template includes".

"Filesystem Library components are supplied by several headers, all in 
directory boost/filesystem:"

my #includes aren't failing, or doesn't the above say what it appears to 
(i.e. there are NO installation requirements for using filesystem, just 
point at the correct includes)

it APPEARS that some library is needed.  What this library is, I do NOT 
know.  I can find no reference to any such in the documents, and I note, in 
passing, that bjam from the root of boost will build no such libraries.

So it's likely not the filesystem CODE that is broken, perhaps it is only 
the documents.

At Sunday 2003/03/16 17:50, you wrote:
At 01:57 AM 3/16/2003, Victor A. Wagner, Jr. wrote:

>Ok, I finally got all the junk straightened out.  got a clean update for
>the RC instead of the mainline, and guess what?
>It looks like it cannot find ANY functions that purportedly are defined in
>filesystem.
>
>oh, compilerVC7.1
>
>
>-- Build started: Project: SimpleSL, Configuration: Debug Win32 --
>
>Compiling...
>main.cpp
>Linking...
>main.obj : error LNK2019: unresolved external symbol "public: class
>std::basic_string,class
>std::allocator > __thiscall boost::filesystem::path::leaf(void)const
The regression tests convenience_test, operators_test, and path_test are 
still passing and not getting link errors for VC++ 7.1 final beta, and for 
virtually all other compilers tested on all other platforms. There have 
been no changes to the test setup for these particular tests for a long time.

Beyond the regression tests, other uses of this library using a VC++ 
solution are also still working fine.

All that leads me to think there is something amiss in your setup.

HTH,

--Beman

___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Victor A. Wagner Jr.  http://rudbek.com
The five most dangerous words in the English language:
  "There oughta be a law"
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


Re: [boost] RC_1_30_0 filesystem broken

2003-03-16 Thread Beman Dawes
At 01:57 AM 3/16/2003, Victor A. Wagner, Jr. wrote:

>Ok, I finally got all the junk straightened out.  got a clean update for
>the RC instead of the mainline, and guess what?
>It looks like it cannot find ANY functions that purportedly are defined 
in
>filesystem.
>
>oh, compilerVC7.1
>
>
>-- Build started: Project: SimpleSL, Configuration: Debug Win32 
--
>
>Compiling...
>main.cpp
>Linking...
>main.obj : error LNK2019: unresolved external symbol "public: class
>std::basic_string,class
>std::allocator > __thiscall 
boost::filesystem::path::leaf(void)const

The regression tests convenience_test, operators_test, and path_test are 
still passing and not getting link errors for VC++ 7.1 final beta, and for 
virtually all other compilers tested on all other platforms. There have 
been no changes to the test setup for these particular tests for a long 
time.

Beyond the regression tests, other uses of this library using a VC++ 
solution are also still working fine.

All that leads me to think there is something amiss in your setup.

HTH,

--Beman

___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost


[boost] RC_1_30_0 filesystem broken

2003-03-15 Thread Victor A. Wagner, Jr.
Ok, I finally got all the junk straightened out.  got a clean update for 
the RC instead of the mainline, and guess what?
It looks like it cannot find ANY functions that purportedly are defined in 
filesystem.

oh, compilerVC7.1

-- Build started: Project: SimpleSL, Configuration: Debug Win32 --

Compiling...
main.cpp
Linking...
main.obj : error LNK2019: unresolved external symbol "public: class 
std::basic_string,class 
std::allocator > __thiscall boost::filesystem::path::leaf(void)const 
" 
([EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@2@@std@@XZ) 
referenced in function _main
main.obj : error LNK2019: unresolved external symbol "public: __thiscall 
boost::filesystem::directory_iterator::directory_iterator(class 
boost::filesystem::path const &)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@12@@Z) referenced in 
function _main
main.obj : error LNK2019: unresolved external symbol "public: __thiscall 
boost::filesystem::directory_iterator::directory_iterator(void)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]) referenced in function _main
main.obj : error LNK2019: unresolved external symbol "public: class 
std::basic_string,class 
std::allocator > __thiscall 
boost::filesystem::path::native_directory_string(void)const " 
([EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@2@@std@@XZ) 
referenced in function _main
main.obj : error LNK2019: unresolved external symbol "bool __cdecl 
boost::filesystem::is_directory(class boost::filesystem::path const &)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@@Z) referenced in function 
_main
main.obj : error LNK2019: unresolved external symbol "public: class 
std::basic_string,class 
std::allocator > __thiscall 
boost::filesystem::path::native_file_string(void)const " 
([EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@2@@std@@XZ) 
referenced in function _main
main.obj : error LNK2019: unresolved external symbol "bool __cdecl 
boost::filesystem::exists(class boost::filesystem::path const &)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@@Z) referenced in function _main
main.obj : error LNK2019: unresolved external symbol "class 
boost::filesystem::path __cdecl boost::filesystem::system_complete(class 
boost::filesystem::path const &)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@ABV312@@Z) referenced in 
function _main
main.obj : error LNK2019: unresolved external symbol "public: __thiscall 
boost::filesystem::path::path(char const *,enum 
boost::filesystem::path_format)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@12@@Z) referenced in 
function _main
main.obj : error LNK2019: unresolved external symbol "class 
boost::filesystem::path const & __cdecl 
boost::filesystem::initial_path(void)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@XZ) referenced in function _main
main.obj : error LNK2019: unresolved external symbol "private: class 
boost::filesystem::path const & __thiscall 
boost::filesystem::directory_iterator::m_deref(void)const " 
([EMAIL PROTECTED]@[EMAIL PROTECTED]@@[EMAIL PROTECTED]@XZ) referenced 
in function "public: class boost::filesystem::path const & __thiscall 
boost::filesystem::directory_iterator::operator*(void)const " 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED]@XZ)
main.obj : error LNK2019: unresolved external symbol "private: void 
__thiscall boost::filesystem::directory_iterator::m_inc(void)" 
([EMAIL PROTECTED]@[EMAIL PROTECTED]@@AAEXXZ) referenced in function 
"public: class boost::filesystem::directory_iterator & __thiscall 
boost::filesystem::directory_iterator::operator++(void)" 
([EMAIL PROTECTED]@boost@@[EMAIL PROTECTED])
Debug/SimpleSL.exe : fatal error LNK1120: 12 unresolved externals

Build log was saved at 
"file://c:\Projects\Programming\personal\BoostTesting\SimpleSL\Debug\BuildLog.htm"
SimpleSL - 13 error(s), 0 warning(s)

-- Done --

Build: 0 succeeded, 1 failed, 0 skipped

Victor A. Wagner Jr.  http://rudbek.com
The five most dangerous words in the English language:
  "There oughta be a law"
___
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost