"Duncan" == Duncan Simpson [EMAIL PROTECTED] writes:
Duncan You do not know that the test compiles without warnings. The
Duncan test decides whether you have snprintf by attempting to link a
Duncan small program conatining snprintf. In particular it can
Duncan succeed even if the declaration is
"Bruce" == Bruce Foster [EMAIL PROTECTED] writes:
Bruce With gcc, vsnprintf is defined in the file libioP.h:
Bruce extern int _IO_vsnprintf __P ((char *string, _IO_size_t maxlen,
Bruce __const char *format, _IO_va_list args));
And it's defined nowhere in /usr/include?
JMarc
> "Duncan" == Duncan Simpson <[EMAIL PROTECTED]> writes:
Duncan> You do not know that the test compiles without warnings. The
Duncan> test decides whether you have snprintf by attempting to link a
Duncan> small program conatining snprintf. In particular it can
Duncan> succeed even if the
> "Bruce" == Bruce Foster <[EMAIL PROTECTED]> writes:
Bruce> With gcc, vsnprintf is defined in the file libioP.h:
Bruce> extern int _IO_vsnprintf __P ((char *string, _IO_size_t maxlen,
Bruce> __const char *format, _IO_va_list args));
And it's defined nowhere in /usr/include?
JMarc
At 3:00 PM +0100 1/18/01, Jean-Marc Lasgouttes wrote:
"Klaus" == Klaus Dittrich [EMAIL PROTECTED] writes:
Klaus OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried
Klaus to get lyx-1.16 up, here my expieriences ..
Klaus In ./src/support/fmt.C --- I had to insert
You do not know that the test compiles without warnings. The test decides
whether you have snprintf by attempting to link a small program conatining
snprintf. In particular it can succeed even if the declaration is not in the
header files the example #include's. The declarations in some of
At 3:00 PM +0100 1/18/01, Jean-Marc Lasgouttes wrote:
> > "Klaus" == Klaus Dittrich <[EMAIL PROTECTED]> writes:
>
>Klaus> OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried
>Klaus> to get lyx-1.16 up, here my expieriences ..
>
>Klaus> In ./src/support/fmt.C ---
You do not know that the test compiles without warnings. The test decides
whether you have snprintf by attempting to link a small program conatining
snprintf. In particular it can succeed even if the declaration is not in the
header files the example #include's. The declarations in some of
"Klaus" == Klaus Dittrich [EMAIL PROTECTED] writes:
Klaus OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried
Klaus to get lyx-1.16 up, here my expieriences ..
Klaus In ./src/support/fmt.C --- I had to insert
Klaus the declaration of vsnprintf in string fmt(char
> "Klaus" == Klaus Dittrich <[EMAIL PROTECTED]> writes:
Klaus> OS: hpux-10.20 with both aCC an gcc-2.75.2 installed. I tried
Klaus> to get lyx-1.16 up, here my expieriences ..
Klaus> In ./src/support/fmt.C --- I had to insert
Klaus> the declaration of vsnprintf in string
Klaus,
I have had similar experiences. Regarding your Makefile problem, I do
not have it when I use GNU Make. I have read elsewhere that GNU make
is required for lyx 1.1.6.
For the fmt.C problem, I got around that problem after configuration
by removing the HAVE_*PRINTF variants in config.h
Klaus,
I have had similar experiences. Regarding your Makefile problem, I do
not have it when I use GNU Make. I have read elsewhere that GNU make
is required for lyx 1.1.6.
For the fmt.C problem, I got around that problem after configuration
by removing the HAVE_*PRINTF variants in config.h
OS: hpux-10.20 with both aCC an gcc-2.75.2 installed.
I tried to get lyx-1.16 up, here my expieriences ..
In po/Makefile there is a typo at line 52
--
POTFILE_IN_DEPS := $(shell find $(top_srcdir)/src -name Makefile.am)
In ./src/support/fmt.C
---
I had to insert
OS: hpux-10.20 with both aCC an gcc-2.75.2 installed.
I tried to get lyx-1.16 up, here my expieriences ..
In po/Makefile there is a typo at line 52
--
POTFILE_IN_DEPS := $(shell find $(top_srcdir)/src -name Makefile.am)
In ./src/support/fmt.C
---
I had to insert
14 matches
Mail list logo
