Pavel Vazharov writes:
> I started the whole build again and it gave the
> following error later in the build, on a different place:
> CC ffserver.o
> ffserver.c: In function 'main':
> ffserver.c:4728: error: 'SA_RESTART' undeclared
> (first use in this function)
This is now fixed in git
Pavel Vazharov writes:
> Everything builds fine with --disable-ffserver switch.
Consider running fate now, you need rsync installed,
then run:
$ make SAMPLES=fate-suite fate-rsync
$ make SAMPLES=fate-suite fate
Or, if you don't feel like downloading the samples:
$ make fate
Carl Eugen
__
Hi,
Everything builds fine with --disable-ffserver switch.
Thanks again.
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Carl Eugen Hoyos writes:
> Is SA_RESTART defined somewhere in /usr/include/* ?
It appears the definition was removed from
qnx because it is not implemented.
You will have to add --disable-ffserver until
a configure check exists.
Carl Eugen
___
Lib
Pavel Vazharov writes:
> CC ffserver.o
> ffserver.c: In function 'main':
> ffserver.c:4728: error: 'SA_RESTART' undeclared
/usr/include/signal.h includes /usr/include/bits/sigaction.h
here which defines SA_RESTART.
Is SA_RESTART defined somewhere in /usr/include/* ?
(You can of course us
Hi,
This time I forgot to save the exact information, but still.
make V=1 version.h
gave an error that version.sh has no permissions to be executed.
I changed the permissions of version.sh and then the above command ran fine.
I started the whole build again and it gave the following error later
Pavel Vazharov writes:
> I managed to install a bash and then the
> "./configure" ran fine.
Thank you for testing!
> CC cmdutils.o
> cmdutils.c:51:21: error: version.h: No such file or directory
What does "make V=1 version.h" show?
I suspect you copied the git checkout together with
th
Hi,
You were right. Thanks very much. I managed to install a bash and then the
"./configure" ran fine.
However, the "make all" command gave this error. (Here are the last lines
from the console output).
CC libavutil/timecode.o
CC libavutil/tree.o
CC libavutil/utils.o
CC libav
Hi,
I did the debug with the echo commands but the results are probably not so
important because, as you said, the problem is very likely to be a broken
shell.
I'll try to update it or to install bash.
Thanks.
On Thu, Jul 11, 2013 at 8:58 AM, Carl Eugen Hoyos wrote:
> Pavel Vazharov writes:
Pavel Vazharov writes:
> #sh --version
> sh: sh --: unknown option
> I think that the shell in QNX is in fact kshell
> because the /bin/sh file is a link to /bin/ksh
> and there is no bash on the system.
>
> #echo $BASH_VERSION
>
> #echo $KSH_VERSION
> @(#)PD KSH v5.2.14 99/07/13.2
(prehisto
Hi,
#sh --version
sh: sh --: unknown option
I think that the shell in QNX is in fact kshell because the /bin/sh file is
a link to /bin/ksh and there is no bash on the system.
#echo $BASH_VERSION
#echo $KSH_VERSION
@(#)PD KSH v5.2.14 99/07/13.2
I hope I'll find a little time today to do the deb
Pavel Vazharov writes:
> # ./configure
> Memory fault (core dumped)
What does the following command show?
# sh --version
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Pavel Vazharov writes:
> As you could see I waited about 3 minutes and there
> was no other visual output on the screen and the
> config.log ending was the same. I could provide
> screen shots as a prove of my words, too.
That wasn't what I meant, sorry.
(There just was no prompt in your orig
Hi,
I hope that this date time and tail information proves that I've waited
enough for the configure to end.
===
# date ; ./configure
Wed Jul 10 07:44:53 PDT 2013
Memory fault (core dumped)
# date
Wed Jul 10 07:47:43 PDT 2
Pavel Vazharov writes:
> # ./configure
> Memory fault (core dumped)
Is this the whole output?
Or are you possibly not waiting for the rest to come?
[...]
> -Werror=vla -c -o /tmp/ffconf..localhost..16134179.o
> /tmp/ffconf..localhost..16134179.c
The reason I ask is that my config.log also en
Hi,
The big problem.
I made the change and run configure
=
# ./configure
Memory fault (core dumped)
Last lines from the config log.
=
BEGIN /tmp/ffconf..localhost..16134179.c
1int x;
END /tmp/ffconf..localhost..16134179.c
gc
Pavel Vazharov writes:
> check_cmd $ld $LDFLAGS $flags $(ld_o $TMPE) $TMPO $libs $extralibs
>
> should become
>
> check_cmd $ld $LDFLAGS $flags -o $TMPE $TMPO $libs $extralibs.
You are correct, the same problem
(but another commit).
Carl Eugen
___
Hi,
I understand the situation. No problem.
I changed the line as you suggested. Here is the console output.
==
# ./configure
gcc is unable to create an executable file.
If gcc is a cross-compiler, use the --enable-cross-compile option.
Only do this if
Pavel Vazharov writes:
> # uname -m
> x86pc
> # uname -s
> QNX
Both are supported, so it should not be necessary
to set --arch or --target-os
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/libav-user
Pavel Vazharov writes:
> check_ld cc
> check_cc
> BEGIN /tmp/ffconf..localhost..22065188.c
> 1 int main(void){ return 0; }
> END /tmp/ffconf..localhost..22065188.c
> gcc -c -o /tmp/ffconf..localhost..22065188.c
> gcc: no input files
Please find the following line in the function
"check_cc
Hi,
Sorry about top posting. I didn't noticed that gmail does this by default.
Is it ok in this way or I should do bottom posting?
=
# uname -m
x86pc
# uname -s
QNX
=
Last 25 lines from the config.log.
yuv4mpegpipe_
Carl Eugen Hoyos writes:
> > --arch=x86
> > --target-os=qnx
>
> Is this really needed?
To rephrase this question:
What do "uname -m" and "uname -s" report?
Carl Eugen
___
Libav-user mailing list
Libav-user@ffmpeg.org
http://ffmpeg.org/mailman/listin
Pavel Vazharov writes:
> Include the log file "config.log" produced by configure
> as this will help solving the problem
The last 25 lines should be enough.
Please stop top-posting, it is considered rude here,
Carl Eugen
___
Libav-user mailing list
Ok. I'm trying again as I was advised. Baby steps.
I downloaded and built yasm on my QNX virtual machine.
Then I make - "git clone git://source.ffmpeg.org/ffmpeg.git ffmpeg" on my
physical machine and then copied the whole ffmpeg folder to my QNX virtual
machine (I don't want to build Git for QNX
Ok. Thanks.
On Sun, Jul 7, 2013 at 10:33 AM, Carl Eugen Hoyos wrote:
> Pavel Vazharov writes:
>
> > I don't think that the optimizations are disabled.
>
> You misunderstood:
> I did not ask you if you disabled optimizations, I
> asked you if you disabled them intentionally
> because you also d
Pavel Vazharov writes:
> I don't think that the optimizations are disabled.
You misunderstood:
I did not ask you if you disabled optimizations, I
asked you if you disabled them intentionally
because you also disabled debugging and debugging
normally is the only reason why developers want
to
Hi Ramu,
I'm pretty sure that the symbols aren't present in the static libraries.
objdump and nm tools shows them as undefined:
# nm libavcodec/libavcodec.a | grep ff_h264dsp_init
U ff_h264dsp_init
# objdump -t libavcodec/libavcodec.a | grep ff_h264dsp_init
*UND* 00
Pavel Vazharov writes:
> ./configure
A few unrelated comments (your explanations may
help improving the configure script):
> --arch=x86
> --target-os=qnx
Is this really needed?
> --enable-static
> --disable-shared
This is the default (unneeded).
> --disable-everything
> --disable-programs
i guess it could be linker problem. can you post the command line
statement, so that anyone can help if you are not pointing to right
libraries.
/R
On 3 July 2013 23:49, Pavel Vazharov wrote:
> Hello,
>
> I'm trying to build the ffmpege library with libx264 support for QNX.
>
> I'm using the fo
Hello,
I'm trying to build the ffmpege library with libx264 support for QNX.
I'm using the following configure script:
./configure \
--arch=x86 \
--disable-debug \
--enable-static \
--disable-shared \
--target-os=qnx \
--disable-programs \
--disable-ffplay \
30 matches
Mail list logo
