[asterisk-r2] Compilation issues

Tue Feb 3 08:57:35 CST 2009

La razón para usar el inglés es que no solo latinos visitan esta
lista. Hay gente al menos de Brasil también. Es discutible que el
portugues es muy similar al español, pero, yo, particularmente, entre
portugues e inglés, entiendo y escribo mejor el inglés. Es el mismo
caso para mucha gente. El inglés se usa como lenguaje intermedio para
entendernos. Aqui nunca se ha prohibido que alguien escriba en
español. Sin embargo si se pide que de ser posible se use el inglés.
Tienes mas posibilidades de alcanzar una audiencia mas grande.

Esta lista no solo está en México. Y el idioma, desde mi punto de
vista, se debe escoger por conveniencia, no por tradición. Y a mi
parecer, el inglés es mas conveniente cuando lo que quieres transmitir
es conocimiento técnico.

On Tue, Feb 3, 2009 at 12:28 AM, ERNESTO CERVANTES
<ernesto.cervantes at grupoicec.com> wrote:
> On Mon, 2 Feb 2009 23:01:42 -0600, Moises Silva wrote
>
> Hola que tal amigos de esta lista se que el idioma ingles es el mas importante a nivel
> mundial aunque el mandarin se mueve con gran importancia sin embargo he notado que la
> mayoria de los que estamos en la lista somos latinos en mi caso trago tortas ahogadas y
> cheves asi como tejuino y aunque se escribir ingles no comprendo por que nosotros
> tenemos que adaptarnos a este idioma si estamos por ejemplo mexico si estuviera en otro
> pais lo entiendo pero por que en mi pais tengo que andar con esto no es justo
>
> se que alguien me dira metete a un foro en español aqui no tienes lugar
>
> es solo un comentario
>
>
>> Juan,
>>
>> Sorry, all this is my fault. I have neglected to upload a new package.
>> The current package has a problem with the file timestamps. It is easy
>> to correct though. All you need to do is touch the files:
>>
>> # touch *
>>
>> Once you execute that command, run the ./configure script again and
>> proceed normally.
>>
>> On Mon, Feb 2, 2009 at 10:32 PM, Juan Felipe Rosero
>> <juan.rosero at nowtek.net> wrote:
>> > Well, it seems like it worked...
>> >
>> > Although I'm not sure if it's really going to work, but at least it compiled properly.
>> >
>> > What did I had to do:
>> >
>> > As the error said, I had to run  'aclocal' and 'autoconf' after I made sure
> AC_PROG_LIBTOOL was present in configure.in
>> >
>> > Then I had to copy the file 'compile' located in /usr/share/automake-1.9/ to the
> OpenR2 folder, then run 'make' again...
>> >
>> > I'm not quite sure about the copying another file thing but I guess I'll have to
> test it before jumping into conclusions.
>> >
>> > We'll see.
>> >
>> > -----Original Message-----
>> > From: asterisk-r2-bounces at lists.digium.com
> [mailto:asterisk-r2-bounces at lists.digium.com] On Behalf Of Juan Felipe Rosero
>> > Sent: lunes, 02 de febrero de 2009 10:32 p.m.
>> > To: asterisk-r2 at lists.digium.com
>> > Subject: Re: [asterisk-r2] Compilation issues
>> >
>> > Hi,
>> >
>> > Thank you for your reply, I'm trying to patch my existing version (I'm working on an
> Elastix distribution, could that be it?) but I can change my mind.
>> >
>> > But even before that, don't I need the OpenR2 libraries already installed before I
> can patch or install the SVN asterisk?
>> >
>> > I'm getting this error while trying to compile the OpenR2 library...
>> >
>> > But still, thank's again.
>> >
>> > Juan Felipe Rosero
>> > IT Engineer
>> > Syworks Latinamérica
>> > Bogota - COLOMBIA
>> > +57 1 742 5555 - +57 1 605 5151
>> >
>> > -----Original Message-----
>> > From: asterisk-r2-bounces at lists.digium.com
> [mailto:asterisk-r2-bounces at lists.digium.com] On Behalf Of Juan Carlos Huerta
>> > Sent: lunes, 02 de febrero de 2009 09:52 p.m.
>> > To: asterisk-r2 at lists.digium.com
>> > Subject: Re: [asterisk-r2] Compilation issues
>> >
>> > Hi,
>> >
>> > Have you tried to use an OpenR2-ready SVN? or are you trying to patch
>> > your self? Take a look to the PDF guide here:
>> >
>> > http://nucleum.com.mx/blog/?p=26
>> >
>> > Juan Carlos
>> > ~ Lo que no te mata te fortalece ~
>> >
>> >
>> >
>> > On Mon, Feb 2, 2009 at 8:04 PM, Juan Felipe Rosero
>> > <juan.rosero at nowtek.net> wrote:
>> >> Hello,
>> >>
>> >>
>> >>
>> >> I have been trying to install OpenR2 on my system but I keep failing while
>> >> trying to run the make command. Here's the output:
>> >>
>> >>
>> >>
>> >> cd . && /bin/sh /usr/src/openr2-1.0.0/missing --run automake-1.9 --foreign
>> >>
>> >> src/Makefile.am:10: Libtool library used but `LIBTOOL' is undefined
>> >>
>> >> src/Makefile.am:10:
>> >>
>> >> src/Makefile.am:10: The usual way to define `LIBTOOL' is to add
>> >> `AC_PROG_LIBTOOL'
>> >>
>> >> src/Makefile.am:10: to `configure.in' and run `aclocal' and `autoconf'
>> >> again.
>> >>
>> >> src/Makefile.am: required file `./compile' not found
>> >>
>> >> make: *** [Makefile.in] Error 1
>> >>
>> >>
>> >>
>> >> I looked for other errors like those and it seemed it had something to do
>> >> with automake, I have automake 1.9.6-2.1 installed.
>> >>
>> >>
>> >>
>> >> I saw some negative responses when I ran ./configure but I'm not sure which
>> >> of those are problematic:
>> >>
>> >>
>> >>
>> >> 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 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 ISO C89... none needed
>> >>
>> >> checking for style of include used by make... GNU
>> >>
>> >> checking dependency style of gcc... gcc3
>> >>
>> >> checking build system type... i686-redhat-linux-gnu
>> >>
>> >> checking host system type... i686-redhat-linux-gnu
>> >>
>> >> checking for a sed that does not truncate output... /bin/sed
>> >>
>> >> checking for grep that handles long lines and -e... /bin/grep
>> >>
>> >> checking for egrep... /bin/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... /usr/bin/nm -B
>> >>
>> >> checking whether ln -s works... yes
>> >>
>> >> checking how to recognise dependent libraries... pass_all
>> >>
>> >> checking how to run the C preprocessor... gcc -E
>> >>
>> >> 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 g++... g++
>> >>
>> >> checking whether we are using the GNU C++ compiler... yes
>> >>
>> >> checking whether g++ accepts -g... yes
>> >>
>> >> checking dependency style of g++... gcc3
>> >>
>> >> checking how to run the C++ preprocessor... g++ -E
>> >>
>> >> checking for g77... no
>> >>
>> >> checking for f77... no
>> >>
>> >> checking for xlf... no
>> >>
>> >> checking for frt... no
>> >>
>> >> checking for pgf77... no
>> >>
>> >> checking for cf77... no
>> >>
>> >> checking for fort77... no
>> >>
>> >> checking for fl32... no
>> >>
>> >> checking for af77... no
>> >>
>> >> checking for f90... no
>> >>
>> >> checking for xlf90... no
>> >>
>> >> checking for pgf90... no
>> >>
>> >> checking for pghpf... no
>> >>
>> >> checking for epcf90... no
>> >>
>> >> checking for gfortran... no
>> >>
>> >> checking for g95... no
>> >>
>> >> checking for f95... no
>> >>
>> >> checking for fort... no
>> >>
>> >> checking for xlf95... no
>> >>
>> >> checking for ifort... no
>> >>
>> >> checking for ifc... no
>> >>
>> >> checking for efc... no
>> >>
>> >> checking for pgf95... no
>> >>
>> >> checking for lf95... no
>> >>
>> >> checking for ftn... no
>> >>
>> >> checking whether we are using the GNU Fortran 77 compiler... no
>> >>
>> >> checking whether  accepts -g... no
>> >>
>> >> checking the maximum length of command line arguments... 32768
>> >>
>> >> checking command to parse /usr/bin/nm -B output from gcc object... ok
>> >>
>> >> checking for objdir... .libs
>> >>
>> >> checking for ar... ar
>> >>
>> >> checking for ranlib... ranlib
>> >>
>> >> checking for strip... strip
>> >>
>> >> checking if gcc supports -fno-rtti -fno-exceptions... no
>> >>
>> >> checking for gcc option to produce PIC... -fPIC
>> >>
>> >> checking if gcc PIC flag -fPIC works... yes
>> >>
>> >> checking if gcc static flag -static works... yes
>> >>
>> >> checking if gcc supports -c -o file.o... yes
>> >>
>> >> checking whether the gcc linker (/usr/bin/ld) supports shared libraries...
>> >> yes
>> >>
>> >> checking whether -lc should be explicitly linked in... no
>> >>
>> >> checking dynamic linker characteristics... GNU/Linux ld.so
>> >>
>> >> checking how to hardcode library paths into programs... immediate
>> >>
>> >> checking whether stripping libraries is possible... yes
>> >>
>> >> checking if libtool supports shared libraries... yes
>> >>
>> >> checking whether to build shared libraries... yes
>> >>
>> >> checking whether to build static libraries... yes
>> >>
>> >> configure: creating libtool
>> >>
>> >> appending configuration tag "CXX" to libtool
>> >>
>> >> checking for ld used by g++... /usr/bin/ld
>> >>
>> >> checking if the linker (/usr/bin/ld) is GNU ld... yes
>> >>
>> >> checking whether the g++ linker (/usr/bin/ld) supports shared libraries...
>> >> yes
>> >>
>> >> checking for g++ option to produce PIC... -fPIC
>> >>
>> >> checking if g++ PIC flag -fPIC works... yes
>> >>
>> >> checking if g++ static flag -static works... yes
>> >>
>> >> checking if g++ supports -c -o file.o... yes
>> >>
>> >> checking whether the g++ linker (/usr/bin/ld) supports shared libraries...
>> >> yes
>> >>
>> >> checking dynamic linker characteristics... GNU/Linux ld.so
>> >>
>> >> checking how to hardcode library paths into programs... immediate
>> >>
>> >> appending configuration tag "F77" to libtool
>> >>
>> >> checking for cosf in -lm... yes
>> >>
>> >> checking math.h usability... yes
>> >>
>> >> checking math.h presence... yes
>> >>
>> >> checking for math.h... yes
>> >>
>> >> checking pthread.h usability... yes
>> >>
>> >> checking pthread.h presence... yes
>> >>
>> >> checking for pthread.h... yes
>> >>
>> >> checking if gcc accepts -fvisibility=hidden option... yes
>> >>
>> >> GCC supports -fvisibility and will be used to compile the library
>> >>
>> >> checking linux/zaptel.h usability... no
>> >>
>> >> checking linux/zaptel.h presence... no
>> >>
>> >> checking for linux/zaptel.h... no
>> >>
>> >> checking zaptel/zaptel.h usability... yes
>> >>
>> >> checking zaptel/zaptel.h presence... yes
>> >>
>> >> checking for zaptel/zaptel.h... yes
>> >>
>> >> checking dahdi/user.h usability... no
>> >>
>> >> checking dahdi/user.h presence... no
>> >>
>> >> checking for dahdi/user.h... no
>> >>
>> >> r2test program will be compiled
>> >>
>> >> checking for svnversion... no
>> >>
>> >> configure: creating ./config.status
>> >>
>> >> config.status: creating Makefile
>> >>
>> >> config.status: creating src/Makefile
>> >>
>> >> config.status: creating config.h
>> >>
>> >> config.status: config.h is unchanged
>> >>
>> >> config.status: executing depfiles commands
>> >>
>> >>
>> >>
>> >> I'm trying to install OpenR2 on Centos 5.2 with zaptel 1.4.11-6 and asterisk
>> >> 1.4.22.0-6
>> >>
>> >>
>> >>
>> >> Any ideas?
>> >>
>> >>
>> >>
>> >> Thank you in advance.
>> >>
>> >>
>> >>
>> >> Juan Felipe Rosero
>> >>
>> >> IT Engineer
>> >>
>> >> Syworks Latinamérica
>> >>
>> >> Bogota - COLOMBIA
>> >>
>> >> +57 1 742 5555 - +57 1 605 5151
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >>
>> >> asterisk-r2 mailing list
>> >> To UNSUBSCRIBE or update options visit:
>> >>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >>
>> >
>> > _______________________________________________
>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >
>> > asterisk-r2 mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >
>> >
>> > _______________________________________________
>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >
>> > asterisk-r2 mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >
>> >
>> > _______________________________________________
>> > --Bandwidth and Colocation Provided by http://www.api-digital.com--
>> >
>> > asterisk-r2 mailing list
>> > To UNSUBSCRIBE or update options visit:
>> >   http://lists.digium.com/mailman/listinfo/asterisk-r2
>> >
>>
>> --
>> "I do not agree with what you have to say, but I'll defend to the
>> death your right to say it." Voltaire
>>
>> _______________________________________________
>> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>>
>> asterisk-r2 mailing list
>> To UNSUBSCRIBE or update options visit:
>>    http://lists.digium.com/mailman/listinfo/asterisk-r2
>
>
> --
> Ing. Ernesto Cervantes Castro
> ernesto.cervantes at grupoicec.com
> 0133-38110145 Ext. 103
> 0443313148727
>
>
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>

-- 
"I do not agree with what you have to say, but I'll defend to the
death your right to say it." Voltaire