Hi, I would like some advice about something thanks. Any hint, or direction to look, is welcome.
I am building on a Raspberry Pi3. As I have mentioned before Quirky Linux, a Puppy fork, is created with Woof*, which builds the distro out of binary packages obtained from anywhere. My first Pi3 is "Quirky-Ubuntu", built with Ubuntu DEBs. This was my host for building with T2, and it worked, except I had to hack some host headers, some awful hacks. But, once i got into Stage2, she took off, very successful, and created enough binary packages for Woof to be able to create "Quirky-T2". Now, I am running Quirky-T2 on the Pi3, and having another go building with T2. Given that T2 packages are very "plain vanilla", I expected T2 to be much happier in stages 0 and 1. Yes, rocketed through stage0, but glibc failed at stage 1. Now, this is where my question comes in, as something odd has happened. >From the error-log, after entering glibc-2.24/ntpl, it runs this: install -c -m 644 ../include/limits.h /usr/include/limits.h This is an error, and fl_wrappers.so reports "writing outside basedir" Both source and destination "limits.h" exist, however, after that operation, the "limits.h" in the host, that is, /usr/include/limits.h, has been deleted! Do you know what would be responsible for that deletion? Is it done by T2? I also have another question. That "-c" in the install line, does nothing. "install --help" reports that "-c" is ignored. Maybe there is another version of install for which that "-c" does something? Oh, just thought of a third question. Sometime ago, I experimented with turning off "Enable TLS and NPTL" in the glibc configuration, however the build then reported that the addon "linuxthreads" is missing. Do, I take it then, that the linuxthreads option is no longer supported in T2? Right now I am stuck, any input is welcome. Yeah, this is not what I should be doing on Christmas Eve! Regards, Barry ----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to [email protected] with a subject of: unsubscribe t2
