Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Sat, 23 Jul 2022 23:06:49 + Tom Schwindl wrote: Dear Tom, > If a system says it's POSIX compliant, we can assume that the `-s' > option exists, but there is no standard which tells us whether > ranlib(1) is available or not. while I agree with your point in general, keep in mind that the

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Wed, 20 Jul 2022 12:23:01 + Tom Schwindl wrote: Dear Tom, > I've noticed that we use the non-standard ranlib(1) program to create > symbol tables for archives created by ar(1). This affects, as far as > I can tell, every creation of static libraries we have. > > ranlib(1) is, in fact, le

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Wed, 20 Jul 2022 12:23:01 + Tom Schwindl wrote: Dear Tom, > I've noticed that we use the non-standard ranlib(1) program to create > symbol tables for archives created by ar(1). This affects, as far as > I can tell, every creation of static libraries we have. > > ranlib(1) is, in fact, le

Re: [dev] Replace ranlib(1) calls?

2022-07-30 Thread Laslo Hunhold
On Sat, 23 Jul 2022 23:06:49 + Tom Schwindl wrote: Dear Tom, > If a system says it's POSIX compliant, we can assume that the `-s' > option exists, but there is no standard which tells us whether > ranlib(1) is available or not. while I agree with your point in general, keep in mind that the

[dev] zuccless.org

2022-07-30 Thread Christoph Lohmann
Greetings comrades, currently we are at brcon2022 in Belgrade, smoking meats and having fun. We decided to make it real: http://www.zuccless.org Come and join the future of meat! Sincerely, Christoph Lohmann Please activate Javascript to see the full signature.