public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: wk <handygewinnspiel@gmx.de>
To: Hans Werner <HWerner4@gmx.de>,
	Linux DVB Mailing List <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] compiling on 2.6.28 broken?
Date: Sat, 10 Jan 2009 12:07:34 +0100	[thread overview]
Message-ID: <49688176.5030603@gmx.de> (raw)
In-Reply-To: <20090110103700.107530@gmx.net>

Hans Werner schrieb:
>> Hi all,
>>
>> Compiling on 2.6.28 seems to be broken (v4l-dvb-985ecd81d993,
>> linux-2.6.28, gcc-3.4.1), is this known or already some patch around?
>>     
>
>
> I can compile fine with 2.6.28, x86_64, gcc 4.2.4. Did you do 'make distclean' first?
>
>   
Well, i did not start with distclean, since i expect a freshly 
downloaded package to be distclean.
Nevertheless make distclean and/or make clean also doesnt work properly:

-bash-3.00# make distclean
make -C /usr/src/v4l-dvb-985ecd81d993/v4l distclean
make[1]: Entering directory `/usr/src/v4l-dvb-985ecd81d993/v4l'
find: .: Value too large for defined data type
make[1]: *** [clean] Fehler 1
make[1]: Leaving directory `/usr/src/v4l-dvb-985ecd81d993/v4l'
make: *** [distclean] Fehler 2

Note the very same error: 'value too large..' Looks like Makefile or 
script failure.

This is a 32bit machine running LinuxFromScratch btw. and not the first 
time compiling the dvb driver.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  parent reply	other threads:[~2009-01-10 11:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 10:27 [linux-dvb] compiling on 2.6.28 broken? handygewinnspiel
     [not found] ` <20090110103700.107530@gmx.net>
2009-01-10 11:07   ` wk [this message]
2009-01-10 18:21     ` wk
2009-01-12  5:49       ` Mauro Carvalho Chehab

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=49688176.5030603@gmx.de \
    --to=handygewinnspiel@gmx.de \
    --cc=HWerner4@gmx.de \
    --cc=linux-dvb@linuxtv.org \
    /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