From: Hans de Goede <hdegoede@redhat.com>
To: Pierre <pierre42d@9online.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: Problem compiling libv4l 0.6.3
Date: Tue, 03 Nov 2009 19:54:45 +0100 [thread overview]
Message-ID: <4AF07C75.8030402@redhat.com> (raw)
In-Reply-To: <4AEF0789.5030005@9online.fr>
Hi,
On 11/02/2009 05:23 PM, Pierre wrote:
> Hans de Goede wrote:
>> Hi,
>>
>> On 10/28/2009 06:43 PM, Pierre wrote:
>>> # make
>>> make -C libv4lconvert V4L2_LIB_VERSION=0.6.3 all
>>> make[1]: Entering directory `/tmp/libv4l-0.6.3/libv4lconvert'
>>> gcc -Wp,-MMD,"libv4lconvert.d",-MQ,"libv4lconvert.o",-MP -c -I../include
>>> -I../../../include -fvisibility=hidden -fPIC -DLIBDIR=\"/usr/local/lib\"
>>> -DLIBSUBDIR=\"libv4l\" -g -O1 -Wall -Wno-unused -Wpointer-arith
>>> -Wstrict-prototypes -Wmissing-prototypes -o libv4lconvert.o
>>> libv4lconvert.c
>>> cc1: error: unrecognized command line option "-fvisibility=hidden"
>>> make[1]: *** [libv4lconvert.o] Error 1
>>> make[1]: Leaving directory `/tmp/libv4l-0.6.3/libv4lconvert'
>>> make: *** [all] Error 2
>>>
>>
>> It would seem that you are using a very very old gcc.
>
> # gcc --version
> gcc (GCC) 3.4.3
> Copyright (C) 2004 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is
> NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
> PURPOSE.
>
> What is the version you recommend ?
[hans@localhost ~]$ gcc --version
gcc (GCC) 4.4.2 20091027 (Red Hat 4.4.2-7)
Is what I use but any 4.x which supports -fvisibility=hidden should work
fine. Note that you will probably also need newer kernel headers.
Regards,
Hans
prev parent reply other threads:[~2009-11-03 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 17:43 Problem compiling libv4l 0.6.3 Pierre
2009-10-29 11:00 ` Hans de Goede
2009-11-02 16:23 ` Pierre
2009-11-03 18:54 ` Hans de Goede [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AF07C75.8030402@redhat.com \
--to=hdegoede@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=pierre42d@9online.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox