https://bugs.exim.org/show_bug.cgi?id=1805

--- Comment #3 from Todd Rinaldo <[email protected]> ---
(In reply to Heiko Schlittermann from comment #2)
> Probably we'll run into some portability issues, since auto allocation of
> memory (as done in getcwd()) seems to be a glibc extension.

I agree. I am in no way tied to the solution I submitted.

I suspected it was possible I could/should use big_buffer given the short
distance in code I needed to hold the info but it was Friday, my approach
seemed simpler given I hadn't thought about portability, and I wasn't confident
I could safely climb through the intervening code to determine if it was
feasable.

Todd

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##

Reply via email to