]> On 26 Nov 1997, Eloy A. Paris wrote:
>> Hi,
>>
>> I am trying to port the ncpfs utilities that Volcker Lendecke
>> maintains to libc6. I am using the latest package he has released
>> (2.0.11).
>>
>> Initially, if you try to compile ncpfs 2.0.11 against libc6 (glibc2)
>> without changing anything, you'll get an infinite number of compiler
>> errors (symbol and structure redefinitons, etc.).
>>
]> [SNIPPED]
]> For the most part Linux utilities will not compile with the new glibc.
]> At the very least, you will need to define:
]> -D__USE_BSD -D__XOPEN_SOURCE_EXTENDED
Those are internal flags. Please have a look at <features.h> - and use
-D_BSD_SOURCE -D_XOPEN_SOURCE_EXTENDED.
]> ...on the gcc command line. Often code has to be rewritten because the
]> code presumes SysV behavior. For some political reason, glibc defaults
]> to BSD behavior (most of the time) in spite of the fact that probably
]> 90 percent of the existing software expects SysV behavior.
That's only the case for signal.
]> Anyway, presuming you already know this and want an interesting
]> challenge, remove all occcurances of:
]> #include <linux/something.h>
]> #include <asm/something.h>
]> Use only standard headers. Then, for the system-specific structure
]> information, include __only__ the specific file that contains that
]> information. You may have to use -D__KERNEL__ to make that information
]> visible.
I hope you did read the FAQ - and all the other information.
]> An additional warning, there __are__ bugs in the new glibc. It will
]> probably be a year or so before glibc is stable. I have been testing
]> primative functions. The latest "feature" I have found is that a write
]> to a closed file-descriptor sometimes succeeds. This is not good.
Nobody said that such a complex project has no bugs. But you should
have noticed from your on bug reports that we're trying to fix things.
IMHO glibc is quite stable and I guess more stable than libc5 ever
was.
]> More people have to test the glibc. The bug-reporting script in the
]> source tree works for rapid reporting. You will want to use it.
Send the reports in - but please read first the documentation,
especially FAQ, README and INSTALL.
Andreas
--
Andreas Jaeger aj@arthur.rhein-neckar.de jaeger@informatik.uni-kl.de
for pgp-key finger ajaeger@alma.student.uni-kl.de
http://www.student.uni-kl.de/~ajaeger/