Jon,
I will check out the documentation. I had only checked on Wget's
site, I had thought that all the same documentation would be there as
well, but that what I get for assuming.
Many thanks
Bryan
On Thu, 24 Feb 2005 02:22:30 +, Jonathan Share <[EMAIL PROTECTED]> wrote:
> On Tue, 22 Feb
On Tue, 22 Feb 2005 19:09:11 +, Bryan <[EMAIL PROTECTED]> wrote:
>
> Automize cannot access PKI-enabled websites, as it does not support
> that functionality. I was reading up about Wget, and I saw that you
> can send a specific cookie back to a website. This is almost exactly
> what I am lo
Did I ask the wrong question? I mean, it's not uncommon to ask about
the feasibility of adding new functionality.
If I am posting on the wrong list, I apologize.
Bryan
On Tue, 22 Feb 2005 19:09:11 +, Bryan <[EMAIL PROTECTED]> wrote:
> I work as a webmaster for a US Government agency. We c
On Wed, 23 Feb 2005, Hrvoje Niksic wrote:
> I see. Now I know why I didn't use AC_FUNC_FSEEKO -- Wget doesn't use
> fseeko anywhere. The only usage we have is:
>
> fseek (fp, 0, SEEK_END);
> size = ftell (fp); /* replaced with ftello where available */
>
> Is there need to use
"Maciej W. Rozycki" <[EMAIL PROTECTED]> writes:
>> I wonder what is the difference between AC_FUNC_FSEEKO and
>> AC_CHECK_FUNCS(seeko). The manual doesn't seem to explain.
>
> Well, that's what I have on my local system:
>
> - Macro: AC_FUNC_FSEEKO
> If the `fseeko' function is available,
On Wed, 23 Feb 2005, Hrvoje Niksic wrote:
> > You may also want AC_FUNC_FSEEKO for fseeko().
>
> I wonder what is the difference between AC_FUNC_FSEEKO and
> AC_CHECK_FUNCS(seeko). The manual doesn't seem to explain.
Well, that's what I have on my local system:
- Macro: AC_FUNC_FSEEKO
"Maciej W. Rozycki" <[EMAIL PROTECTED]> writes:
>> Is it possible to portably use open() and retain large file support?
>
> Try the AC_SYS_LARGEFILE autoconf macro.
That's what I thought I was using. I was just afraid that open()
wasn't correctly encompassed by the large file API's, a fear that
Simone Piunno <[EMAIL PROTECTED]> writes:
> On Tuesday 22 February 2005 00:10, Hrvoje Niksic wrote:
>
>> If wide chars were in that message, you could no longer print it with
>> printf, which means that a majority of gettext-using programs would be
>> utterly broken, Wget included. I imagine I wo
On Tuesday 22 February 2005 00:10, Hrvoje Niksic wrote:
> If wide chars were in that message, you could no longer print it with
> printf, which means that a majority of gettext-using programs would be
> utterly broken, Wget included. I imagine I would have gotten a bunch
> of bug reports for that
On Tue, 22 Feb 2005, Hrvoje Niksic wrote:
> However, I suspect that this will not work correctly with large files.
> strace shows that, when large files are used, Linux fopen includes
> O_LARGEFILE among the flags. Solaris, on the other hand, seems to use
> the open64 function. (But will open be
10 matches
Mail list logo
