According to ed on 1/24/2010 8:00 PM:
> I am uncertain as to the implications of the following message when I was
> compiling OpenCASCADE6.3.0 but I thought I would send it to you anyways.
> thank you
>
> checking X11/extensions/multibuf.h usability... no
> checking X11/extensions/multibuf.h prese
I am uncertain as to the implications of the following message when I was
compiling OpenCASCADE6.3.0 but I thought I would send it to you anyways.
thank you
checking X11/extensions/multibuf.h usability... no
checking X11/extensions/multibuf.h presence... yes
configure: WARNING: X11/extensions/mult
Hello Marek,
Thanks for the report.
* Marek Burza wrote on Wed, May 09, 2007 at 05:57:45PM CEST:
>
> I was trying to install an extension (network-2.0) to Haskell on cygwin
> and I got an error or warning which requested to be reported to you :)
> You can see the output below and if you need more
Hi,
I was trying to install an extension (network-2.0) to Haskell on cygwin
and I got an error or warning which requested to be reported to you :)
You can see the output below and if you need more info I'll be glad to
provide it to you.
Best regards,
Mark
Configuring network-2.0...
configure:
Hello Robert,
* Robert Boyer wrote on Tue, Jun 06, 2006 at 04:58:25PM CEST:
> If one fetches Gnu Common Lisp from "cvs head", a la
>
> setenv CVSROOT :pserver:[EMAIL PROTECTED]:/sources/gcl
> cvs -z9 -q checkout gcl
>
> and then does
>
> configure --disable-statsysbfd --enable-locbfd
If one fetches Gnu Common Lisp from "cvs head", a la
setenv CVSROOT :pserver:[EMAIL PROTECTED]:/sources/gcl
cvs -z9 -q checkout gcl
and then does
configure --disable-statsysbfd --enable-locbfd --enable-debug --enable-ansi
One gets, somewhere in the 35,000 characters of output:
che
Installing ntp-4.2.0_1 via the FreeBSD ports collection.
5.4-RELEASE FreeBSD 5.4-RELEASE #0
Best regards,
-nick/
configure: WARNING: sys/proc.h: present but cannot be compiled
configure: WARNING: sys/proc.h: check for missing prerequisite headers?
configure: WARNING: sys/proc.h: proceeding with
...
checking mcrypt.h usability... yes
checking mcrypt.h presence... no
configure: WARNING: mcrypt.h: accepted by the compiler, rejected by the
preprocessor!
configure: WARNING: mcrypt.h: proceeding with the preprocessor's result
configure: WARNING: ## ##
c
> configure: WARNING: ## Report this to [EMAIL PROTECTED] ##
Hello,
thank you for your bug report.
Please forward this to the bug report address of the project you tried to
compile, we cannot do anything about it.
Tell them to read the section "Present But Cannot Be Compiled" of the
manual
Hello
This is a first for me. Not sure what is expected.
I was installing Slackware and Asterisk (amongst other things) as per the
directions found here:
http://astguiclient.sourceforge.net/scratch_install.html
I was following the instructions to the letter. I have built successful linux
box
Hello,
> > They have misconfigured the bug report address in AC_INIT, so also tell
>
> Autoconf ~2.57, which always requested a report to [EMAIL PROTECTED]
thank you Noah, for enlightening me.
Anyway, I hope it's good to react to such reports by telling the user to
send bug report to the packag
On Wed, Mar 09, 2005 at 11:14:49AM +0100, Stepan Kasal wrote:
> They have misconfigured the bug report address in AC_INIT, so also tell
> them to change it to *their* bug report address.
FTR, his error message was from Autoconf ~2.57, which always requested a report
to [EMAIL PROTECTED] If it wer
Hello,
On Wed, Mar 09, 2005 at 01:54:32AM +0100, Johan Nessaether wrote:
> 2005-03-09 01:07 1 255 629 lame-3.96.1.tar.gz
you should report this bug to the bug report address of the "lame"
project. Tell them to read the section "Present But Cannot Be Compiled"
of the manual to autoconf-2
2005-03-09 01:07 1 255 629 lame-3.96.1.tar.gz
cygwin-1.5.11-1
checking whether time.h and sys/time.h may both be included... yes
checking for working alloca.h... yes
checking for alloca... yes
checking for gettimeofday... yes
checking for strtol... yes
checking winsock2.h usability... no
c
On Fri, Mar 04, 2005 at 09:40:13AM +, James Youngman wrote:
> On Fri, Mar 04, 2005 at 08:24:24AM +0100, Stepan Kasal wrote:
>
> > you should report this bug to the bug report address of the "grip"
> > project. Tell them to read the section "Present But Cannot Be Compiled"
> > of the manual to
Hi James,
On Fri, Mar 04, 2005 at 09:40:13AM +, James Youngman wrote:
> In retrospect it would have saved many emails to this mailing list if
> the error message had indicated explicitly that the bug is in the
> package being configured, not in autoconf. The message could even
> have included
On Fri, Mar 04, 2005 at 08:24:24AM +0100, Stepan Kasal wrote:
> you should report this bug to the bug report address of the "grip"
> project. Tell them to read the section "Present But Cannot Be Compiled"
> of the manual to autoconf-2.59.
In retrospect it would have saved many emails to this mai
Hi,
On Thu, Mar 03, 2005 at 11:12:57PM +, sam wrote:
> generated while running configure in grip-3.2.0 on slackware-10.1 x86
you should report this bug to the bug report address of the "grip"
project. Tell them to read the section "Present But Cannot Be Compiled"
of the manual to autoconf-2.
generated while running configure in grip-3.2.0 on slackware-10.1 x86 hardware
copied direct from terminal after error generated...
Yours hoping to help
checking cdda_interface.h usability... yes
checking cdda_interface.h presence... yes
checking for cdda_interface.h... yes
checking cdda_para
Bug reported by configure while compiling Apache 2.0.52 on NetBSD 2.0.1:
.
.
.
checking sys/sysctl.h usability... no
checking sys/sysctl.h presence... yes
configure: WARNING: sys/sysctl.h: present but cannot be compiled
configure: WARNING: sys/sysctl.h: check for missing prerequisite headers?
confi
20 matches
Mail list logo