On a related note, how does one recompile phobos on Linux? It fails in the current recls.

Ben Hinkle wrote:
| On a related note, how does one recompile phobos on Linux? It fails in
| the current recls.
|

Play a bit with the GCC settings in recls' makefile.
I think gcc-3.4.2 works but gcc-3.4.3 fails.

Thomas

Ben Hinkle wrote:
> On a related note, how does one recompile phobos on Linux? It fails in the current recls. 
> 
> 

I managed to recompile it (gcc 3.4, or was it 3.3?). What can't be done is use it in a program. It fails because std.recls has non-versioned extern(Windows) declarations. Obviously, ld will later complain. I don't know how to solve it, though.

_______________________
Carlos Santander Bernal

As "the author", I can say that I agreed with Walter some months ago that if I trimmed it down, he'd put it in. This I have done so, in the form of recls 1.6.1 (http://recls.org/downloads.html), but I've not heard anything about it from Walter as yet. I assume he's busy on other things.

As I mentioned in the announcement post, Walter had been reluctant to put it in since version 1.2, as it'd grown in size (both source and object), with the accumulation of features, particularly the FTP searching (Windows-only). Hence the trimming that's been done for 1.6.1.

As for when he'll do it, I can't say, but I'm also one who's keen to see it happen, as it'd simplify my projects. ;$


"Jamboree" <jam@bor.ee> wrote in message news:d1mco4$2q8t$1@digitaldaemon.com...
>
> 

"Ben Hinkle" <ben.hinkle@gmail.com> wrote in message news:d20vlk$2koi$1@digitaldaemon.com...
> On a related note, how does one recompile phobos on Linux? It fails in the current recls.

recls builds and executes for me without a whimper on Linux. As I said in the post (and as is mentioned on the recls website), one needs the latest STLSoft 1.8.3 beta.

Can you specify what the build problem(s) are?

"Carlos Santander B." <csantander619@gmail.com> wrote in message news:d21ba4$20e$1@digitaldaemon.com...
> Ben Hinkle wrote:
>> On a related note, how does one recompile phobos on Linux? It fails in the current recls.
>
> I managed to recompile it (gcc 3.4, or was it 3.3?). What can't be done is use it in a program. It fails because std.recls has non-versioned extern(Windows) declarations. Obviously, ld will later complain. I don't know how to solve it, though.

Can you be specific?

Alas - partly because of the stunning lack of Apple customer service - I've not yet got to the point of using D on Linux. I'd be more than happy for people to make changes to the std/recls.d file in the latest release (http://recls.org/downloads.html) and feed them back to me.

Or, if there's the interest, and it's not too bothersome to get GDC going on Linux, I could be motivated to get D on Linux going and do it myself. I've just not been motivated to do that - D on Linux, that is - as there's been no interest in incorporating later versions of recls in Phobos. Any feedback here - +ve or -ve - would be informative.

FTR: I get plenty of +ve recls feedback from non-D people (e.g. C/C++/STL/Python/Ruby - even .NET!), so I know the library's doing something(s) that people want to do. My suspicion is that the problems that've been part of recls/D - which are substantially out of my control - have made it much less attractive for D users. Of course, that's largely conjecture, since the only feedback has been complaints about the docs being out of step with the library and the problems with Linux builds.

The former is people's reasonable consternation at finding docs out of step with library. This occured because the documentation was submitted to Walter for a version post 1.2 (the current level of recls within Phobos), sometime around 1.4 or 1.5. Unfortunately, Walter rejected the library update on the grounds that there was too much source code, but put the new docs in! Ever since, I've been trying explaining this to users, and promising that, come a newer trimmed down version (which happens to be 1.6.1) all would be in sync.

The latter is more my responsibility, since I've not (yet) got around to having D on Linux. Is this easy to do? If so, I'll bite the bullet and get it done. Then it'll all be in Walter's court.

But please understand that getting any upgrade into Phobos is out of my control. Realistically, if people want a 'good' recls, they may have to go to the effort of using the latest release separately to Phobos. :-(

Matthew

One last thing, which may or may not be good news: There are no more 1.x releases of recls planned. I plan to do a complete rewrite - recls2 - which will do a great many things that I've learned should have been in recls 1, including:

    - date/time filtering
    - size filtering
    - content filtering (with plug-in file comparators)
    - search feedback
    - optional breadth-first (and depth-limited) search
    - plug-in pattern matching (along with example plug-ins using pcre, DMC++'s regexp, Windows PathMatch(), etc. etc.)
    - (optional) platform-independent data representation

and there'll be a greater spectrum of search spaces, including:

    - file systems
    - FTP host directories
    - Win32 registry
    - SourceSafe repositories
    - CVS repositories
    - anything else sensible that people request

and, perhaps of interest:

    - it's quite likely to be written substantially in C, for maximising portability and minimising size

This'll be the last big extension in my Positive Integration column, before I start looking at language embedding.

The bad news is that this is not likely to start for some months hence. My suggestion is, as per the understanding Walter and I made some months ago, that the best scenario for Phobos is that the current version (1.6.1) of recls be incorporated and then this newer, better (and probably smaller) recls2 can be incorporated towards the end of the year.



"Matthew" <admin.hat@stlsoft.dot.org> wrote in message news:d21vge$pkr$1@digitaldaemon.com...
>
> "Carlos Santander B." <csantander619@gmail.com> wrote in message news:d21ba4$20e$1@digitaldaemon.com...
>> Ben Hinkle wrote:
>>> On a related note, how does one recompile phobos on Linux? It fails in the current recls.
>>
>> I managed to recompile it (gcc 3.4, or was it 3.3?). What can't be done is use it in a program. It fails because std.recls has non-versioned extern(Windows) declarations. Obviously, ld will later complain. I don't know how to solve it, though.
>
> Can you be specific?
>
> Alas - partly because of the stunning lack of Apple customer service - I've not yet got to the point of using D on Linux. I'd be more than happy for people to make changes to the std/recls.d file in the latest release (http://recls.org/downloads.html) and feed them back to me.
>
> Or, if there's the interest, and it's not too bothersome to get GDC going on Linux, I could be motivated to get D on Linux going and do it myself. I've just not been motivated to do that - D on Linux, that is - as there's been no interest in incorporating later versions of recls in Phobos. Any feedback here - +ve or -ve - would be informative.
>
> FTR: I get plenty of +ve recls feedback from non-D people (e.g. C/C++/STL/Python/Ruby - even .NET!), so I know the library's doing something(s) that people want to do. My suspicion is that the problems that've been part of recls/D - which are substantially out of my control - have made it much less attractive for D users. Of course, that's largely conjecture, since the only feedback has been complaints about the docs being out of step with the library and the problems with Linux builds.
>
> The former is people's reasonable consternation at finding docs out of step with library. This occured because the documentation was submitted to Walter for a version post 1.2 (the current level of recls within Phobos), sometime around 1.4 or 1.5. Unfortunately, Walter rejected the library update on the grounds that there was too much source code, but put the new docs in! Ever since, I've been trying explaining this to users, and promising that, come a newer trimmed down version (which happens to be 1.6.1) all would be in sync.
>
> The latter is more my responsibility, since I've not (yet) got around to having D on Linux. Is this easy to do? If so, I'll bite the bullet and get it done. Then it'll all be in Walter's court.
>
> But please understand that getting any upgrade into Phobos is out of my control. Realistically, if people want a 'good' recls, they may have to go to the effort of using the latest release separately to Phobos. :-(
>
> Matthew
>
>
> 

Matthew wrote:
| "Ben Hinkle" <ben.hinkle@gmail.com> wrote in message
news:d20vlk$2koi$1@digitaldaemon.com...
|
|>On a related note, how does one recompile phobos on Linux? It fails in
the current recls.
|
|
| recls builds and executes for me without a whimper on Linux. As I said
in the post (and as is mentioned on the recls
| website), one needs the latest STLSoft 1.8.3 beta.
|
| Can you specify what the build problem(s) are?

See atached diff for G++-3.4.3's problems with dmd-0.119's phobos.
I don't have vanilla gdc sources at hand but I remember lot's of
problems just to create the object files (etc/c/recls) using g++-3.4.3
but no major problems with g++-3.4.2.

Thomas

In article <d21unh$p3b$1@digitaldaemon.com>, Matthew says...
>
>
>"Ben Hinkle" <ben.hinkle@gmail.com> wrote in message news:d20vlk$2koi$1@digitaldaemon.com...
>> On a related note, how does one recompile phobos on Linux? It fails in the current recls.
>
>recls builds and executes for me without a whimper on Linux. As I said in the post (and as is mentioned on the recls website), one needs the latest STLSoft 1.8.3 beta.
>
>Can you specify what the build problem(s) are?

using dmd-119:
make -C ./etc/c/recls -f linux.mak
make[1]: Entering directory `/home/bhinkle/dmd/src/phobos/etc/c/recls'
g++ -Wall  -O4 -mcpu=i686  -DNDEBUG -DUNIX -D_M_IX86 -c -I. -I../stlsoft
-orecls_fileinfo_unix.o recls_fileinfo_unix.cpp
./stlsoft/stlsoft_null.h: In function `const recls::recls_fileinfo_t*
recls::FileInfo_Allocate(size_t)':
./stlsoft/stlsoft_null.h:194: error: `stlsoft::NULL_v::NULL_v(const
stlsoft::NULL_v&)' is private
recls_fileinfo_unix.cpp:237: error: within this context
./stlsoft/stlsoft_null.h: In function `void recls::FileInfo_Release(const
recls::recls_fileinfo_t*)':
./stlsoft/stlsoft_null.h:194: error: `stlsoft::NULL_v::NULL_v(const
stlsoft::NULL_v&)' is private
recls_fileinfo_unix.cpp:256: error: within this context
./stlsoft/stlsoft_null.h: In function `recls::recls_rc_t
recls::FileInfo_Copy(const recls::recls_fileinfo_t*, const
recls::recls_fileinfo_t**)':
./stlsoft/stlsoft_null.h:194: error: `stlsoft::NULL_v::NULL_v(const
stlsoft::NULL_v&)' is private
recls_fileinfo_unix.cpp:277: error: within this context
make[1]: *** [recls_fileinfo_unix.o] Error 1

g++ -v gives:
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.2/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)