1 |
On Mon, Aug 9, 2010 at 2:49 PM, walt <w41ter@×××××.com> wrote: |
2 |
|
3 |
> On 08/09/2010 12:33 PM, Kevin O'Gorman wrote: |
4 |
> |
5 |
> > ... |
6 |
> |
7 |
> Now I find that not only |
8 |
>> do the gdbm modules of python and perl reject my files, but so does a C |
9 |
>> program that uses the distributed |
10 |
>> libgdbm. |
11 |
>> |
12 |
> |
13 |
> You didn't say how long ago the problem started, but looking at the |
14 |
> files in sys-libs/gdbm I see nothing newer than March 20. Is your |
15 |
> problem newer than March 20? |
16 |
> |
17 |
> Have you tried running your test program with strace? |
18 |
> |
19 |
> |
20 |
I hadn't done anything with that application in over a year, so I did not |
21 |
have any way to narrow it down. |
22 |
As it happens, I had a sudden rush of brains to the head and read the ewarn |
23 |
message that comes out |
24 |
when you compile gdbm, to the effect that 32-bit systems may have to |
25 |
rebuild, etc, etc. |
26 |
|
27 |
As I suspected, it was LFS-related. |
28 |
|
29 |
Write it off as a case of RTFLog. |
30 |
|
31 |
Now all I have to do is discover why an ewarn wasn't emailed to me -- I |
32 |
thought I had that set up. |
33 |
|
34 |
-- |
35 |
Kevin O'Gorman, PhD |