Ken (and/or anyone else interested in this subject),
I am still slowly studying all these, below, have some updates with good
and bad news, inline. I am leaving all previous info, for easier reference.
Do not know if the thread should be moved to -dev.
Em 30-07-2013 08:36, Fernando de Oliveira escreveu:
> Em 29-07-2013 20:28, Ken Moffat escreveu:
>> On Mon, Jul 29, 2013 at 07:43:09PM -0300, Fernando de Oliveira wrote:
>>>
>>> I tried it before, and again today. Does not work so simply. First,
>>> tried with Arch's tar ball for ffmpeg-compat. Then, just used
>>> ffmpeg-0.8.7, but with their instructions to make it -compat. Build
>>> succeeded, audacity works, but with a dirty trick. For ffmeg-compat-0.8.7:
>>>
>>> ./configure \
>>> --prefix=/usr \
>>> --incdir=/usr/include/ffmpeg-compat \
>>> --libdir=/usr/lib/ffmpeg-compat \
>>> --shlibdir=/usr/lib/ffmpeg-compat \
>>> ...
>>>
>>> Then, DESTDIR install, remove $DESTDIR/usr/{bin,share}, copy to /usr.
>>> And it works fine, just used it with previous audacity that was removed
>>> (now) from /usr/local and new one at /usr.
>>>
>>> Audacity build with instructions a la Arch fails at make, complaining
>>> that cannot find gtk/gtk.h:
This did not happen in my developing system. It (audacity) *builds
fine*, after ffmpeg-compat-0.8.7 is installed in the system. I think
these are great news.
However, I have a new problem in this developing system, that could not
yet sort out: VLC fails to get info from the web, using *lua*. I have
rechecked what I did wrong with lua, but no idea yet.
Another problem, common to both systems, probably independent of
audacity and ffmpeg-compat, but included, as I am trying to make all
work together: vlc-2.0.8 *crashes* with a .flv I normally use to test
and also with some.MOV that my daughter sent to me, in both systems, so,
I reverted it to 2.0.7. Tried already not applying some or all patches,
seds, etc. This instability, I still have no idea where is coming from,
just segmentation fault, no info in logs, but I recently learned
something on how to trace seg faults, when debugging sane-frontends
xscanimage plugin failure in GIMP.
>>>
>>> CaptureEvents.cpp:34:21: fatal error: gtk/gtk.h: Arquivo ou diretório
>>> não encontrado
>>> compilation terminated.
>>> make[1]: ** [CaptureEvents.o] Erro 1
>>> ...
>>>
>>> But it is in the system:
>>>
>>> $ find /usr -name gtk.h 2>/dev/null
>>> /usr/include/gtk-3.0/gtk/gtk.h
>>> /usr/include/gtk-2.0/gtk/gtk.h <----------- must be this one
>>> /usr/src/linux-3.10.1-NG-pae/tools/perf/ui/gtk/gtk.h
>>> /usr/src/linux-3.10.2-NG-pae/tools/perf/ui/gtk/gtk.h
>>>
>>> I really do not understand how to tell make where they are, using
>>> CPPFLAGS and/or LDFLAGS, tried many wrong combinations. Also tried to
>>> instruct with PKG_CONFIG_PATH as done for configure.
>>>
>>> PKG_CONFIG_PATH+="/usr/lib/ffmpeg-compat/pkgconfig" make
>>>
>>> Finally, the dirty trick, please find attached the complete g++
>>> instruction, as it would be broken by the mail client:
>>>
>>> PKG_CONFIG_PATH+="/usr/lib/ffmpeg-compat/pkgconfig" \
>>> ./configure --prefix=/usr
>>> make
>>> cd src &&
>>> g++ -c -s `pkg-config gtk+-2.0 --cflags` `pkg-config gtk+-2.0 --libs` \
>>> -I../lib-src/portmixer/include ........... \
>>> CaptureEvents.cpp -o CaptureEvents.o &&
>>> cd .. &&
>>> make
>>> make install
>>> ...
>>>
>>> With "-s `pkg-config gtk+-2.0 --cflags` `pkg-config gtk+-2.0 --libs`"
>>> included, it succeeds compiling CaptureEvents.
I have a vague idea of what is wrong with this system, hidding gtk.h
from the compiler, but have to dig in a bit further, to see if my
suspicion is correct.
>>>
>>> I do not think anyone would consider this an acceptable solution, but I
>>> do not know how to tell make to do it properly.
>>>
>>> If possible to be done properly by modifying some flags for make, please
>>> educate me.
>>>
>>> Thanks in advance.
>>>
>> Glad you managed to work around the gtk header issue. I've no
>> idea what causes the problem. I would be interested in what changes
>> in the output from the different call to pkg-config. I guess I can
>> look at that on my own system when I'm back at a desktop machine.
>
>
> Thank you, ĸen,
>
> Since I received that mail, I am working to reply. No interesting to
> report up to now. I am starting to install dependencies in another
> system, just to check if I have a problem with this one.
>
As I wrote above, in this dev system, have already the dependencies
installed.
--
[]s,
Fernando
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
