Mailing List Archive

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Varnish 1.1.2-5 seems to deliver blank pages when the request is
> done with HTTP/1.0. This problem should be fixed in the current
> trunk according to this ticket:
>
> http://varnish.projects.linpro.no/ticket/197

The patch in the PR is based on an incorrect understanding of the
code. The bug was fixed in r2091 in trunk, and can be obtained with
'svn diff -c2091' in a trunk checkout. I will merge it to 1.1 ASAP.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

I tried to build my own rpm's for RH EL4 from instructions you sent to
Ramon A Hermon. But unfortunately my environment seems to missing
rpmbuild and automake (and possibly other needed tools). Therefore I
kindly ask the list for help with building rpm's for Redhat EL4.

Regards
<fredrik />

On 3 mar 2008, at 11.50, Dag-Erling Sm?rgrav wrote:

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Varnish 1.1.2-5 seems to deliver blank pages when the request is
> done with HTTP/1.0. This problem should be fixed in the current
> trunk according to this ticket:
>
> http://varnish.projects.linpro.no/ticket/197

The patch in the PR is based on an incorrect understanding of the
code. The bug was fixed in r2091 in trunk, and can be obtained with
'svn diff -c2091' in a trunk checkout. I will merge it to 1.1 ASAP.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> I tried to build my own rpm's for RH EL4 from instructions you sent to
> Ramon A Hermon. But unfortunately my environment seems to missing
> rpmbuild and automake (and possibly other needed tools). Therefore I
> kindly ask the list for help with building rpm's for Redhat EL4.

You should only need rpmbuild, autoconf, automake and libtool. They
should all be part of the standard assortment of packages that come
with your OS (i.e. they should be on the installation CD or DVD that
you used).

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Alright... I will give it another try. But do I have to change
anything else? varnish.spec for example?

Regards
<fredrik />

On 3 mar 2008, at 15.49, Dag-Erling Sm?rgrav wrote:

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> I tried to build my own rpm's for RH EL4 from instructions you sent to
> Ramon A Hermon. But unfortunately my environment seems to missing
> rpmbuild and automake (and possibly other needed tools). Therefore I
> kindly ask the list for help with building rpm's for Redhat EL4.

You should only need rpmbuild, autoconf, automake and libtool. They
should all be part of the standard assortment of packages that come
with your OS (i.e. they should be on the installation CD or DVD that
you used).

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Alright... I will give it another try. But do I have to change
> anything else? varnish.spec for example?

Yes, you need to find the line in redhat/varnish.spec that says

# ./autogen.sh

and change it to

./autogen.sh

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Easy even for me ;-) Apart from automake, autoconf and libtool the
build process also wanted ncurses-devel. I changed the varnish.spec
and then tried the rpmbuild command. Unfortunately something went
wrong. Here's the output:

[root at sehan9078gota1 varnish]# rpmbuild -tb varnish-1.1.2.tar.gz
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.99170
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd /usr/src/redhat/BUILD
+ rm -rf varnish-1.1.2
+ /bin/gzip -dc /home/xlibris/varnish/varnish-1.1.2.tar.gz
+ tar -xf -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd varnish-1.1.2
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chown -Rhf root .
++ /usr/bin/id -u
+ '[' 0 = 0 ']'
+ /bin/chgrp -Rhf root .
+ /bin/chmod -Rf a+rX,u+w,g-w,o-w .
+ ./autogen.sh
+ aclocal
+ libtoolize --copy --force
+ autoheader
+ automake --add-missing --copy --foreign
configure.ac: installing `./install-sh'
configure.ac: installing `./missing'
bin/varnishadm/Makefile.am: installing `./compile'
bin/varnishadm/Makefile.am: installing `./depcomp'
+ autoconf
+ exit 0
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.47906
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd varnish-1.1.2
+ CFLAGS='-O2 -g -march=i386 -mcpu=i686'
+ export CFLAGS
+ CXXFLAGS='-O2 -g -march=i386 -mcpu=i686'
+ export CXXFLAGS
+ FFLAGS='-O2 -g -march=i386 -mcpu=i686'
+ export FFLAGS
+ ./configure --host=i686-redhat-linux-gnu --build=i686-redhat-linux-
gnu --target=i386-redhat-linux --program-prefix= --prefix=/usr --exec-
prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --
datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib --
libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/usr/com
--mandir=/usr/share/man --infodir=/usr/share/info --disable-static --
localstatedir=/var/lib

checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking target system type... i386-redhat-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for i686-redhat-linux-gnu-gcc... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... nm
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for i686-redhat-linux-gnu-g++... no
checking for i686-redhat-linux-gnu-c++... no
checking for i686-redhat-linux-gnu-gpp... no
checking for i686-redhat-linux-gnu-aCC... no
checking for i686-redhat-linux-gnu-CC... no
checking for i686-redhat-linux-gnu-cxx... no
checking for i686-redhat-linux-gnu-cc++... no
checking for i686-redhat-linux-gnu-cl... no
checking for i686-redhat-linux-gnu-FCC... no
checking for i686-redhat-linux-gnu-KCC... no
checking for i686-redhat-linux-gnu-RCC... no
checking for i686-redhat-linux-gnu-xlC_r... no
checking for i686-redhat-linux-gnu-xlC... no
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build)

RPM build errors:
Bad exit status from /var/tmp/rpm-tmp.47906 (%build)


I checked the config.log file and last log messages is:

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define HAVE_DLFCN_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_MEMORY_H 1
#define HAVE_STDINT_H 1
#define HAVE_STDLIB_H 1
#define HAVE_STRINGS_H 1
#define HAVE_STRING_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_UNISTD_H 1
#define PACKAGE "varnish"
#define PACKAGE_BUGREPORT "varnish-dev at projects.linpro.no"
#define PACKAGE_NAME "Varnish"
#define PACKAGE_STRING "Varnish 1.1.2"
#define PACKAGE_TARNAME "varnish"
#define PACKAGE_VERSION "1.1.2"
#define STDC_HEADERS 1
#define VERSION "1.1.2"
#define _GNU_SOURCE 1
#endif
#ifdef __cplusplus
void exit (int);

configure: exit 1

On my Feodora box rpmbuild creates the rpm's successfully, but not on
my Redhat EL 4.
Advice is appreciated.

Regards
<fredrik />

On 3 mar 2008, at 17.31, Dag-Erling Sm?rgrav wrote:

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Alright... I will give it another try. But do I have to change
> anything else? varnish.spec for example?

Yes, you need to find the line in redhat/varnish.spec that says

# ./autogen.sh

and change it to

./autogen.sh

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Easy even for me ;-) Apart from automake, autoconf and libtool the
> build process also wanted ncurses-devel.

Ah, right. We removed that in trunk (it will just skip the ncurses
parts if you don't have it), but not in 1.1.

> checking how to run the C++ preprocessor... /lib/cpp
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build)
>
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.47906 (%build)
>
> I checked the config.log file and last log messages is:

The last log message is irrelevant, it's always the same. What's
interesting is the error message that comes a few dozen lines further
up. It would be easiest if you would just mail me the entire file.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no

The problem is solved. The missing piece was gcc-c++. When we
installed that package the build process executed without problems.
Thank you for your help.

Regards
<fredrik />

On 4 mar 2008, at 10.50, Dag-Erling Sm?rgrav wrote:

Fredrik Nygren <fredrik.nygren at gotamedia.se> writes:
> Easy even for me ;-) Apart from automake, autoconf and libtool the
> build process also wanted ncurses-devel.

Ah, right. We removed that in trunk (it will just skip the ncurses
parts if you don't have it), but not in 1.1.

> checking how to run the C++ preprocessor... /lib/cpp
> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
> See `config.log' for more details.
> error: Bad exit status from /var/tmp/rpm-tmp.47906 (%build)
>
> RPM build errors:
> Bad exit status from /var/tmp/rpm-tmp.47906 (%build)
>
> I checked the config.log file and last log messages is:

The last log message is irrelevant, it's always the same. What's
interesting is the error message that comes a few dozen lines further
up. It would be easiest if you would just mail me the entire file.

DES
--
Dag-Erling Sm?rgrav
Senior Software Developer
Linpro AS - www.linpro.no