Re: readlink bug?

Hi Bruno,

> * Bruno Haible <[email protected]> [2017-03-15 20:37:51 +0100]:
>
>> Then we could write an autoconf test for it to only enable correcting
>> code when necessary.
>
> Autoconf tests are a good idea in general. But here there's a problem:
> The /proc file system can be mounted or unmounted. In chroot
> environments it is normally unmounted. Therefore it is possible that
> on a build machine of a distro, there will be no /proc file system,
> whereas on the machine of the end user, there will be.

I think this is a general risk that the build machine can be different
in some unknown way from the user box.

An egregious example would be the build machine be free of the [Pentium
FP bug](https://en.wikipedia.org/wiki/Pentium_FDIV_bug) thus building
the Linux kernel without the workaround.

However, Daniel's point is, IMO, quite solid.
The workaround should be in gnulib, not CLISP sources.
We should not have to think about this.

Ideally gnulib should provide

        char *gnulib_readlink(char* path);

which will malloc() it's return value (which the caller will free()).
I don't think the cost of malloc/free is on par with readlink which
requires disk access.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1504
http://steingoldpsychology.com http://www.childpsy.net http://mideasttruth.com
http://americancensorship.org http://no2bds.org https://jihadwatch.org
Live free or die.

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel