Re: fatal error: 'wordexp.h' file not found
On Thu, July 9, 2020 5:53 pm, Ingo Schwarze wrote: > Hi, > > The interface is so outrageously ill-designed that we decided to not > provide it, even though it is part of POSIX. > > Talk to the upstream program author and ask them to use a saner API > instead. > > Yours, > Ingo > Hey, thanks for the reference. For word/path expansion even glob can be used, so I replaced all wordexp calls to glob, and it worked just as well. Have a good day!
Re: fatal error: 'wordexp.h' file not found
On 2020/07/09 20:36, deserter...@danwin1210.me wrote: > On Thu, July 9, 2020 5:53 pm, Ingo Schwarze wrote: > > Hi, > > > > The interface is so outrageously ill-designed that we decided to not > > provide it, even though it is part of POSIX. > > > > Talk to the upstream program author and ask them to use a saner API > > instead. > > > > Yours, > > Ingo > > > Hey, thanks for the reference. For word/path expansion even glob can be used, > so I replaced all wordexp calls to glob, and it worked just as well. > > Have a good day! > > > That (replace with glob) is what most things in ports are doing. Obviously not identical (doesn't handle environment expansion, ~, etc) but often good enough.
Re: fatal error: 'wordexp.h' file not found
Hi, deserter...@danwin1210.me wrote on Thu, Jul 09, 2020 at 05:38:18PM -: > wordexp.h is part of glibc: functions, constants and data types for word > expansion are declared in the header file `wordexp.h'. > > But it is not in my system! Is this by design? or an error? The absence of wordexp(3) from OpenBSD is intentional. https://marc.info/?l=openbsd-tech=127053352511782=2 "This patch adds support for wordexp(3) and wordfree(3) to libc." https://marc.info/?l=openbsd-tech=127056947124559=2 tedu@: "What a load of crap." https://marc.info/?l=openbsd-tech=127057160727771=2 deraadt@: "I think we should stand up to crap and not ever implement it." The interface is so outrageously ill-designed that we decided to not provide it, even though it is part of POSIX. Talk to the upstream program author and ask them to use a saner API instead. Yours, Ingo
