kolumbus70
Anmeldungsdatum: 22. Dezember 2011
Beiträge: 19
Wohnort: Göttingen
|
Hallo zusammen, da ich momentan (immer) noch das Problem habe von meinem Sat-Reciever (Dreambox) zum PC ein Streaming einzurichten
hab ich in 'nem anderen Forum erfahren, dass ich meinen gstreamer updaten soll. Gesagt getan, ich bin auf die Web-Seite
gegangen und hab mir die Programm-Sources runtergeladen und entpackt. Da die Installation nicht über das Software-Center
funktioniert, muss die Installation händisch im Terminal durchgeführt werden. Wenn ich in die install-Anleitung gehe ist das Programmupdate eigentlich gut beschreiben.
Beim Befehl "./configure" ist noch alles in Ordnung. Wenn ich aber im nächsten Schritt "make" zur Kompellierung des
packages ausführe, bekomme ich die Fehlermeldung:
make: *** Keine Targets angegeben und keine »make«-Steuerdatei gefunden. Schluss.
und die Installation bricht ab. Wie muss ich vorgehen, dass das Update durchgeführt wird ?
Muss ich in das bereits installierte Programm als "target" verzweigen ? Ausserdem würde mich noch interessieren, ob ich
was beachten muss, wegen den anderen Komponenten des gstreamers und der Installationsreihenfolge ? Schönen Dank vorab für Eure Hilfe. Viele Grüsse Christoph Moderiert von tomtomtom: Ins passende Forum verschoben. Bitte beachte die Themenstickies.
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 54454
Wohnort: Berlin
|
Hallo, zeig doch mal den Inhalt des Ordners, den du entpackt hast, hier im Codeblock. Außerdem zeig bitte mal die Terminal-Ausgabe von dpkg -l build-essential hier.
|
kolumbus70
(Themenstarter)
Anmeldungsdatum: 22. Dezember 2011
Beiträge: 19
Wohnort: Göttingen
|
Hallo tomtomtom, hier der Inhalt des Ordners
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45 | root@data-desktop:/home/data/DreamStream-E2/gstreamer_vers/gstreamer-0.10.33# ls -l
insgesamt 4284
-rw-r--r-- 1 data data 76502 2011-05-10 09:27 ABOUT-NLS
-rw-r--r-- 1 data data 41289 2011-05-10 09:27 aclocal.m4
-rw-r--r-- 1 data data 1096 2010-04-20 17:20 AUTHORS
-rwxr-xr-x 1 data data 3485 2011-04-26 16:33 autogen.sh
-rw-r--r-- 1 data data 2462603 2011-05-10 09:36 ChangeLog
drwxr-xr-x 4 data data 4096 2011-05-10 09:47 common
-rwxr-xr-x 1 data data 3769 2011-05-10 09:27 compile
-rwxr-xr-x 1 data data 44959 2011-05-10 09:27 config.guess
-rw-r--r-- 1 data data 9811 2011-05-10 09:27 config.h.in
-rw-r--r-- 1 root root 61182 2012-02-03 18:42 config.log
-rwxr-xr-x 1 data data 18343 2011-05-10 09:27 config.rpath
-rwxr-xr-x 1 data data 34597 2011-05-10 09:27 config.sub
-rwxr-xr-x 1 data data 883975 2011-05-10 09:27 configure
-rw-r--r-- 1 data data 30992 2011-05-09 13:24 configure.ac
-rw-r--r-- 1 data data 25265 2010-04-20 17:20 COPYING
-rwxr-xr-x 1 data data 18615 2011-05-10 09:27 depcomp
drwxr-xr-x 11 data data 4096 2011-05-10 09:47 docs
drwxr-xr-x 3 data data 4096 2011-05-10 09:46 gst
-rw-r--r-- 1 data data 664 2011-01-08 03:59 gst-element-check.m4.in
-rw-r--r-- 1 data data 14014 2011-05-10 09:26 gstreamer.doap
-rw-r--r-- 1 data data 19116 2011-05-10 09:28 gstreamer.spec
-rw-r--r-- 1 data data 19168 2011-01-07 02:09 gstreamer.spec.in
-rw-r--r-- 1 data data 7831 2010-04-20 17:20 INSTALL
-rwxr-xr-x 1 data data 13663 2011-05-10 09:27 install-sh
drwxr-xr-x 3 data data 4096 2011-05-10 09:46 libs
-rwxr-xr-x 1 data data 282953 2011-05-10 09:27 ltmain.sh
drwxr-xr-x 2 data data 4096 2011-05-10 09:47 m4
-rw-r--r-- 1 data data 346 2010-04-20 17:20 MAINTAINERS
-rw-r--r-- 1 data data 8302 2011-01-07 02:09 Makefile.am
-rw-r--r-- 1 data data 48460 2011-05-10 09:27 Makefile.in
-rwxr-xr-x 1 data data 11419 2011-05-10 09:27 missing
-rw-r--r-- 1 data data 108679 2011-05-10 09:46 NEWS
drwxr-xr-x 2 data data 4096 2011-05-10 09:46 pkgconfig
drwxr-xr-x 4 data data 4096 2011-05-10 09:46 plugins
drwxr-xr-x 2 data data 4096 2011-05-10 09:47 po
-rw-r--r-- 1 data data 9500 2010-04-20 17:20 README
-rw-r--r-- 1 data data 12476 2011-05-10 09:43 RELEASE
drwxr-xr-x 2 data data 4096 2011-05-10 09:46 scripts
-rw-r--r-- 1 data data 10 2010-04-20 17:20 stamp.h.in
drwxr-xr-x 6 data data 4096 2011-05-10 09:46 tests
-rw-r--r-- 1 data data 0 2010-04-20 17:20 TODO
drwxr-xr-x 2 data data 4096 2011-05-10 09:46 tools
drwxr-xr-x 6 data data 4096 2011-05-10 09:46 win32
|
und hier die Ausgabe von "dpkg -l build-essential" | root@data-desktop:/home/data/DreamStream-E2/gstreamer_vers/gstreamer-0.10.33# dpkg -l build-essential
Gewünscht=Unbekannt/Installieren/R=Entfernen/P=Vollständig Löschen/Halten
| Status=Nicht/Installiert/Config/U=Entpackt/halb konFiguriert/
Halb installiert/Trigger erWartet/Trigger anhängig
|/ Fehler?=(kein)/R=Neuinstallation notwendig (Status, Fehler: GROSS=schlecht)
||/ Name Version Beschreibung
+++-=====================-=====================-==========================================================
ii build-essential 11.5ubuntu1 Informational list of build-essential packages
|
Schönen Dank für Deine Hilfe. Grüsse Christoph
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 54454
Wohnort: Berlin
|
Warum bist du als root eingeloggt? Was sagt cat /home/data/DreamStream-E2/gstreamer_vers/gstreamer-0.10.33/README ?
|
kolumbus70
(Themenstarter)
Anmeldungsdatum: 22. Dezember 2011
Beiträge: 19
Wohnort: Göttingen
|
Hi, die README-Datei sagt folgendes: 1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247 | WHAT IT IS
----------
This is GStreamer, a framework for streaming media.
WHERE TO START
--------------
We have a website at
http://gstreamer.freedesktop.org/
You should start by going through our FAQ at
http://gstreamer.freedesktop.org/data/doc/gstreamer/head/faq/html/
There is more documentation; go to
http://gstreamer.freedesktop.org/documentation
You can subscribe to our mailing lists; see the website for details.
We track bugs in GNOME's bugzilla; see the website for details.
You can join us on IRC - #gstreamer on irc.freenode.org
GStreamer 0.10 series
---------------------
Starring
GSTREAMER
The core around which all other modules revolve. Base functionality and
libraries, some essential elements, documentation, and testing.
BASE
A well-groomed and well-maintained collection of GStreamer plug-ins and
elements, spanning the range of possible types of elements one would want
to write for GStreamer.
And introducing, for the first time ever, on the development screen ...
THE GOOD
--- "Such ingratitude. After all the times I've saved your life."
A collection of plug-ins you'd want to have right next to you on the
battlefield. Shooting sharp and making no mistakes, these plug-ins have it
all: good looks, good code, and good licensing. Documented and dressed up
in tests. If you're looking for a role model to base your own plug-in on,
here it is.
If you find a plot hole or a badly lip-synced line of code in them,
let us know - it is a matter of honour for us to ensure Blondie doesn't look
like he's been walking 100 miles through the desert without water.
THE UGLY
--- "When you have to shoot, shoot. Don't talk."
There are times when the world needs a color between black and white.
Quality code to match the good's, but two-timing, backstabbing and ready to
sell your freedom down the river. These plug-ins might have a patent noose
around their neck, or a lock-up license, or any other problem that makes you
think twice about shipping them.
We don't call them ugly because we like them less. Does a mother love her
son less because he's not as pretty as the other ones ? No - she commends
him on his great personality. These plug-ins are the life of the party.
And we'll still step in and set them straight if you report any unacceptable
behaviour - because there are two kinds of people in the world, my friend:
those with a rope around their neck and the people who do the cutting.
THE BAD
--- "That an accusation?"
No perfectly groomed moustache or any amount of fine clothing is going to
cover up the truth - these plug-ins are Bad with a capital B.
They look fine on the outside, and might even appear to get the job done, but
at the end of the day they're a black sheep. Without a golden-haired angel
to watch over them, they'll probably land in an unmarked grave at the final
showdown.
Don't bug us about their quality - exercise your Free Software rights,
patch up the offender and send us the patch on the fastest steed you can
steal from the Confederates. Because you see, in this world, there's two
kinds of people, my friend: those with loaded guns and those who dig.
You dig.
The Lowdown
-----------
--- "I've never seen so many plug-ins wasted so badly."
GStreamer Plug-ins has grown so big that it's hard to separate the wheat from
the chaff. Also, distributors have brought up issues about the legal status
of some of the plug-ins we ship. To remedy this, we've divided the previous
set of available plug-ins into four modules:
- gst-plugins-base: a small and fixed set of plug-ins, covering a wide range
of possible types of elements; these are continuously kept up-to-date
with any core changes during the development series.
- We believe distributors can safely ship these plug-ins.
- People writing elements should base their code on these elements.
- These elements come with examples, documentation, and regression tests.
- gst-plugins-good: a set of plug-ins that we consider to have good quality
code, correct functionality, our preferred license (LGPL for the plug-in
code, LGPL or LGPL-compatible for the supporting library).
- We believe distributors can safely ship these plug-ins.
- People writing elements should base their code on these elements.
- gst-plugins-ugly: a set of plug-ins that have good quality and correct
functionality, but distributing them might pose problems. The license
on either the plug-ins or the supporting libraries might not be how we'd
like. The code might be widely known to present patent problems.
- Distributors should check if they want/can ship these plug-ins.
- People writing elements should base their code on these elements.
- gst-plugins-bad: a set of plug-ins that aren't up to par compared to the
rest. They might be close to being good quality, but they're missing
something - be it a good code review, some documentation, a set of tests,
a real live maintainer, or some actual wide use.
If the blanks are filled in they might be upgraded to become part of
either gst-plugins-good or gst-plugins-ugly, depending on the other factors.
- If the plug-ins break, you can't complain - instead, you can fix the
problem and send us a patch, or bribe someone into fixing them for you.
- New contributors can start here for things to work on.
PLATFORMS
---------
- Linux is of course fully supported
- FreeBSD is reported to work; other BSD's should work too
- Solaris is reported to work; a specific sunaudiosink plugin has been written
- MacOSX is reported to work; specific audio and video sinks have been written
- Windows support is experimental but improving. Output sinks have been
written but are not yet included in the code. We support
- MSys/MingW builds
- Microsoft Visual Studio 6 builds (see win32/README.txt)
INSTALLING FROM PACKAGES
------------------------
You should always prefer installing from packages first. GStreamer is
well-maintained for a number of distributions, including Fedora, Debian,
Ubuntu, Mandrake, Gentoo, ...
Only in cases where you:
- want to hack on GStreamer
- want to verify that a bug has been fixed
- do not have a sane distribution
should you choose to build from source tarballs or git.
Find more information about the various packages at
http://gstreamer.freedesktop.org/download/
COMPILING FROM SOURCE TARBALLS
------------------------------
- again, make sure that you really need to install from source !
If GStreamer is one of your first projects ever that you build from source,
consider taking on an easier project.
- check output of ./configure --help to see if any options apply to you
- run
./configure
make
to build GStreamer.
- if you want to install it (not required, but what you usually want to do), run
make install
- try out a simple test:
gst-launch -v fakesrc num_buffers=5 ! fakesink
(If you didn't install GStreamer, prefix gst-launch with tools/)
If it outputs a bunch of messages from fakesrc and fakesink, everything is
ok.
If it did not work, keep in mind that you might need to adjust the
PATH and/or LD_LIBRARY_PATH environment variables to make the system
find GStreamer in the prefix where you installed (by default that is /usr/local).
- After this, you're ready to install gst-plugins, which will provide the
functionality you're probably looking for by now, so go on and read
that README.
COMPILING FROM GIT
------------------
When building from git sources, you will need to run autogen.sh to generate
the build system files.
You will need a set of additional tools typical for building from git,
including:
- autoconf
- automake
- libtool
autogen.sh will check for recent enough versions and complain if you don't have
them. You can also specify specific versions of automake and autoconf with
--with-automake and --with-autoconf
Check autogen.sh options by running autogen.sh --help
autogen.sh can pass on arguments to configure - you just need to separate them
from autogen.sh with -- between the two.
prefix has been added to autogen.sh but will be passed on to configure because
some build scripts like that.
When you have done this once, you can use autoregen.sh to re-autogen with
the last passed options as a handy shortcut. Use it.
After the autogen.sh stage, you can follow the directions listed in
"COMPILING FROM SOURCE"
You can also run your whole git stack uninstalled. The script in
the gstreamer module /scripts/gst-uninstalled) is helpful in setting
up your environment for this.
PLUG-IN DEPENDENCIES AND LICENSES
---------------------------------
GStreamer is developed under the terms of the LGPL (see LICENSE file for
details). Some of our plug-ins however rely on libraries which are available
under other licenses. This means that if you are distributing an application
which has a non-GPL compatible license (for instance a closed-source
application) with GStreamer, you have to make sure not to distribute GPL-linked
plug-ins.
When using GPL-linked plug-ins, GStreamer is for all practical reasons
under the GPL itself.
HISTORY
-------
The fundamental design comes from the video pipeline at Oregon Graduate
Institute, as well as some ideas from DirectMedia. It's based on plug-ins that
will provide the various codec and other functionality. The interface
hopefully is generic enough for various companies (ahem, Apple) to release
binary codecs for Linux, until such time as they get a clue and release the
source.
|
Hilft Dir das weiter ? Wenn Du mehr Info's brauchst → kein Problem
|
tomtomtom
Supporter
Anmeldungsdatum: 22. August 2008
Beiträge: 54454
Wohnort: Berlin
|
Bitte zeige mal die komplette Ausgabe von ./configure , du kannst diese auch per ./configure > Ausgabe.txt in eine Textdatei umleiten. Wie dir ja die README selbst sagt, hast du dir übrigens nicht gerade ein einfaches Projekt ausgesucht. 😉 Du könntest alternativ auch einfach erstmal von einem Live-USB-Stick aus testen, ob eine neuere gstreamer-Version hilft, da in Oneiric 0.10.35 genutzt wird.
|
kolumbus70
(Themenstarter)
Anmeldungsdatum: 22. Dezember 2011
Beiträge: 19
Wohnort: Göttingen
|
Hi tomtomtom, danke für den Tipp mit dem USB-Stick ... ich werd's auf jeden Fall mal probieren Anbei die Datei mit der ./configure Ausgabe:
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking nano version... 0 (release)
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
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 dependency style of gcc... gcc3
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 fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert i686-pc-linux-gnu file names to i686-pc-linux-gnu format... func_convert_file_noop
checking how to convert i686-pc-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... dlltool
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
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 for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) 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 for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
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
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking for CFPreferencesCopyAppValue... no
checking for CFLocaleCopyCurrent... no
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for VALGRIND... no
no
configure: Using GStreamer source release as package name
configure: Using Unknown package origin as package origin
configure: Using GST_PKG_CONFIG_PATH = $(top_builddir)/pkgconfig
configure: Setting GST_PACKAGE_RELEASE_DATETIME to 2011-05-10
checking whether byte ordering is bigendian... no
checking if unaligned memory access works correctly... (whitelisted) yes
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for gcc option to accept ISO C99... -std=gnu99
checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking whether gcc -std=gnu99 and cc understand -c and -o together... yes
checking dependency style of gcc -std=gnu99... gcc3
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 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 -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
configure: working c++ compiler found: yes
checking for perl... /usr/bin/perl
checking for bison... no Grüsse Christoph
|