On Fri, Nov 24, 2023 at 01:53:04AM +0100, Guillem Jover wrote:
> Hi!
Hi Guillem!
Apologies for not replying to these emails earlier.
> On Tue, 2023-10-31 at 10:52:40 +0100, Guillem Jover wrote:
>...
> > If PIE (via specs files) appears to work on x32, and changing the
> > defaults in gcc is too
Hi!
On Tue, 2023-10-31 at 10:52:40 +0100, Guillem Jover wrote:
> I guess I could do it the other way, and given this is apparently
> causing issues as reported by Adrian, and as seen recently from
> the referenced bug report which might require patching a specific
> package to disable PIE there, I
and because I was also expecting some word from the
relevant arch porters.
I guess I could do it the other way, and given this is apparently
causing issues as reported by Adrian, and as seen recently from
the referenced bug report which might require patching a specific
package to disable
> -Original Message-
> From: Leslie Rhorer [mailto:lrho...@satx.rr.com]
> Sent: Friday, May 29, 2009 9:32 PM
> To: debian-amd64@lists.debian.org
> Subject: RE: 64 bit LFS compile error
>
> > > > On amd64 off_t and all the others are naturally 64bit. And for
> > > On amd64 off_t and all the others are naturally 64bit. And for 32bit
> > > code you should rather enable LFS so off_t is 64bit instead of using
> > > off64_t (adding -D_FILE_OFFSET_BITS=64).
> >
> > I'm sorry, but I don't quite follow your meaning. Are you saying I
> should
> > replace all r
On Thu, May 28, 2009 at 06:18:56PM -0500, Leslie Rhorer wrote:
> > > I downloaded an application (mfs-tools) which I am trying to compile on
> > my
> > > Debian "Lenny" system, but the make is failing with the following
> > errors:
> > >
> &
> > I downloaded an application (mfs-tools) which I am trying to compile on
> my
> > Debian "Lenny" system, but the make is failing with the following
> errors:
> >
> > gcc -DHAVE_CONFIG_H -I. -I../include -I../include-g -O2 -MT
> > readwrite.o -MD
"Leslie Rhorer" writes:
> I downloaded an application (mfs-tools) which I am trying to compile on my
> Debian "Lenny" system, but the make is failing with the following errors:
>
> gcc -DHAVE_CONFIG_H -I. -I../include -I../include-g -O2 -MT
> readwrite.o -M
I downloaded an application (mfs-tools) which I am trying to compile on my
Debian "Lenny" system, but the make is failing with the following errors:
gcc -DHAVE_CONFIG_H -I. -I../include -I../include-g -O2 -MT
readwrite.o -MD -MP -MF .deps/readwrite.Tpo -c -o readwrite.o r
On Mon, Jun 16, 2008 at 10:36:50AM +0200, Goswin von Brederlow wrote:
> For the kernel I found that -j3 is a few seconds faster than -j4.
>
> But what really makes a difference for me is ccache. It won't hep the
> first time you compile something but the second time. I would b
ading of packages.
>
> The thing is, many Makefiles are NOT proper and will result in broken
> builds if you try to run them in parallel. So there is no way you can
> just say 'always do this' because sometimes it doesn't work.
>
> I find that 2xCores is a good
in broken
builds if you try to run them in parallel. So there is no way you can
just say 'always do this' because sometimes it doesn't work.
I find that 2xCores is a good value, since it tries to make sure each
core has something to compile even while doing disk io for another
compil
Am Sonntag, 15. Juni 2008 schrieb Lennart Sorensen:
> On Sun, Jun 15, 2008 at 02:01:18PM +0200, Hans-J. Ullrich wrote:
> > I would like to increase compiling speed of my system (AMD64, dual-core,
> > 2GB RAM).
> >
> > I suppose, there are some settings in /etc/apt/apt-build.conf, I can use
> > with
On Sun, Jun 15, 2008 at 02:01:18PM +0200, Hans-J. Ullrich wrote:
> I would like to increase compiling speed of my system (AMD64, dual-core, 2GB
> RAM).
>
> I suppose, there are some settings in /etc/apt/apt-build.conf, I can use with
> gcc or make (such like NICE=something) or let it run more pr
Am Sonntag, den 15.06.2008, 14:01 +0200 schrieb Hans-J. Ullrich:
> Hi all,
>
> I would like to increase compiling speed of my system (AMD64, dual-core, 2GB
> RAM).
>
> I suppose, there are some settings in /etc/apt/apt-build.conf, I can use with
> gcc or make (such like NICE=something) or let i
Hi all,
I would like to increase compiling speed of my system (AMD64, dual-core, 2GB
RAM).
I suppose, there are some settings in /etc/apt/apt-build.conf, I can use with
gcc or make (such like NICE=something) or let it run more processes at a
time.
Are there any experiences, somebody made at ?
Jonas Meurer <[EMAIL PROTECTED]> writes:
> On 13/09/2007 Goswin von Brederlow wrote:
>> >> And indeed some patches seem to be applied (see below). But i still
>> >> don't see any xen options in menuconfig. Maybe the 2.6.22 xen patches
>> >> are for i386 only and not ported to amd64 yet?
>> >
>> >
On 13/09/2007 Goswin von Brederlow wrote:
> >> And indeed some patches seem to be applied (see below). But i still
> >> don't see any xen options in menuconfig. Maybe the 2.6.22 xen patches
> >> are for i386 only and not ported to amd64 yet?
> >
> > Based on the output those patches do not contain
Gabor Gombas <[EMAIL PROTECTED]> writes:
> On Thu, Sep 13, 2007 at 01:42:22AM +0200, Jonas Meurer wrote:
>
>> What is the current situation with xen on amd64? the debian/sid archive
>> keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile
>> a 2.6.
On Thu, Sep 13, 2007 at 01:42:22AM +0200, Jonas Meurer wrote:
> What is the current situation with xen on amd64? the debian/sid archive
> keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile
> a 2.6.22 dom0 kernel with debian xen patches applied on my amd64 system.
I
Hello,
2007/9/13, Jonas Meurer <[EMAIL PROTECTED]>:
> What is the current situation with xen on amd64?
I have a dell SC1435 with 2 "Dual-Core AMD Opteron(tm) Processor 2212
HE" (4 Cores) I just installed the xen kernel image from etch
(2.6.18-4-xen-amd64) (installed it shortly - 1 or 2 weeks - be
hello,
What is the current situation with xen on amd64? the debian/sid archive
keeps no linux-image-2.6.22-2-xen-amd64, and I was not able to compile
a 2.6.22 dom0 kernel with debian xen patches applied on my amd64 system.
I have linux-source-2.6.22 and linux-patch-debian-2.6.22 installed, and
/usr/src/modules/kqemu/kqemu-mod.o'. Stop.
under 64 bit kernel, both
m-a -l 2.6.21-2-k7 a-i kqemu
m-a -l 2.6.21-2-amd64 a-i kqemu
fail to compile.
--
Jamil Djadala <[EMAIL PROTECTED]>
Jamil Djadala <[EMAIL PROTECTED]> writes:
> Hi all,
> I have 32 bit debian(testing) with 64 bit stock kernel
> (linux-image-2.6.18-4-amd64)
>
> (of course i have 64 bit processor)
>
> is there standard way to build 64 bit modules (nvidia, rt2500) with
> module-assistant ?
>
> i guess 64bit chroo
Hi all,
I have 32 bit debian(testing) with 64 bit stock kernel
(linux-image-2.6.18-4-amd64)
(of course i have 64 bit processor)
is there standard way to build 64 bit modules (nvidia, rt2500) with
module-assistant ?
i guess 64bit chroot may be solution, but any other ?
--
Jamil Djadala <[EMAI
Hi,
Can anyone tell me how to create the Boost libraries so that I can use
them using the mingw32 cross compiler? Can that be done using the cross
compiler itself or should I just compile Boost on a Windows machine and
copy the files?
TIA
--
Groeten,
Joost Kraaijeveld
Askesis B.V
On Thu, May 03, 2007 at 07:57:41PM +0200, Joost Kraaijeveld wrote:
> 1 program, multiple platforms?
Well some things (like ghostscript) have different makefiles for
different OSs, but shared code. Some use configure to try to detect a
billion parameters and work everything out based on that. Eit
On Thu, 2007-05-03 at 13:54 -0400, Lennart Sorensen wrote:
> On Thu, May 03, 2007 at 06:32:54PM +0200, Joost Kraaijeveld wrote:
> > Do you have a better (==simpler) sollution?
>
> Depends what you are actually trying to do.
1 program, multiple platforms?
--
Groeten,
Joost Kraaijeveld
Askesis B.
On Thu, May 03, 2007 at 06:32:54PM +0200, Joost Kraaijeveld wrote:
> Do you have a better (==simpler) sollution?
Depends what you are actually trying to do.
--
Len Sorensen
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hi,
Joost> On Thu, 2007-05-03 at 18:02 +0200, Lennart Sorensen wrote:
Joost> > Why are you using configure? autoconf may be useful at times but it
Joost> > isn't a magical cure to all porting issues.
Joost> Do you have a better (==simpler) sollution?
Joost>
You can learn from the sources of [1
On Thu, 2007-05-03 at 18:02 +0200, Lennart Sorensen wrote:
> Why are you using configure? autoconf may be useful at times but it
> isn't a magical cure to all porting issues.
Do you have a better (==simpler) sollution?
--
Groeten,
Joost Kraaijeveld
Askesis B.V.
Molukkenstraat 14
6524NB Nijmege
On Thu, May 03, 2007 at 09:07:44AM +0200, Joost Kraaijeveld wrote:
> I have written a small "Hello world" program that I want to cross
> compile from Debian to Windows using the Mingw32 package. I can run
> "configure" both on Debian and on Windows without problem
raaijeveld escribió:
> Hi,
>
> I have written a small "Hello world" program that I want to cross
> compile from Debian to Windows using the Mingw32 package. I can run
> "configure" both on Debian and on Windows without problem.
>
> Can anyone give me the c
Hi,
I have written a small "Hello world" program that I want to cross
compile from Debian to Windows using the Mingw32 package. I can run
"configure" both on Debian and on Windows without problem.
Can anyone give me the correct syntax for calling configure so that I
can co
On Fri, Mar 30, 2007 at 08:15:18AM +, A J Stiles wrote:
> I always thought that once the AMD64 processor was operating in 64-bit mode,
> certain 32-bit instructions were no longer available -- and the transition
> was an irreversible one.
No, not quite. You loose VM86 I believe, so no 16bit
On Thursday 29 March 2007 23:24, Alex Samad wrote:
> It seem silly that there is not programmatical method to pass data from a
> 64 bit app to a 32 bit dll. Might not be efficient but should still be
> possible
I always thought that once the AMD64 processor was operating in 64-bit mode,
certain
Alex Samad <[EMAIL PROTECTED]> writes:
> On Thu, Mar 29, 2007 at 02:57:34PM +0100, Rob Andrews wrote:
>> On 29-Mar-2007 13:32.19 (BST), spp mg wrote:
>> > How to compile amd64 package from i386 source?
>> >
>> > I would like use *gstreamer0
On Thu, Mar 29, 2007 at 02:57:34PM +0100, Rob Andrews wrote:
> On 29-Mar-2007 13:32.19 (BST), spp mg wrote:
> > How to compile amd64 package from i386 source?
> >
> > I would like use *gstreamer0.10-pitfdll* (and other.)but it's only
> > supply i386
On Thu, Mar 29, 2007 at 08:32:19PM +0800, spp mg wrote:
> How to compile amd64 package from i386 source?
>
> I would like use *gstreamer0.10-pitfdll* (and other.)but it's only
> supply i386 package.
> How can I compile?
>
> And ,How can I know I succeed?
There is n
On Thu, 29 Mar 2007 15:00:19 +0200, Rob Andrews wrote:
> This is why the package is not built for amd64!
Definitely true. Let's give more general advice though: sometimes you
find i386 only packages, especially from 3rd parties.
If you have the source repository:
# apt-get build-dep package
#
On 29-Mar-2007 13:32.19 (BST), spp mg wrote:
> How to compile amd64 package from i386 source?
>
> I would like use *gstreamer0.10-pitfdll* (and other.)but it's only
> supply i386 package.
> How can I compile?
Chances are, if it's not already built for amd64, t
hi all
How to compile amd64 package from i386 source?
I would like use *gstreamer0.10-pitfdll* (and other.)but it's only
supply i386 package.
How can I compile?
And ,How can I know I succeed?
thanks.
See in the follow bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=401201
___
Yahoo! Mail - Sempre a melhor op��o para voc�!
Experimente j� e veja as novidades.
http://br.yahoo.com/mailbeta/tudonovo/
--
To UNSU
On Wed, 2007-01-03 at 00:00 +0100, Gilles Sadowski wrote:
> Hello.
>
> I use "make-kpkg" (from "kernel-package" deb) to compile the Nvidia driver
> (I've just downloaded version 1.0.8776-3 of "nvidia-kernel-source").
>
> Then I get (after
Hello.
I use "make-kpkg" (from "kernel-package" deb) to compile the Nvidia driver
(I've just downloaded version 1.0.8776-3 of "nvidia-kernel-source").
Then I get (after building kernel 2.6.19.1):
---CUT---
NVIDIA: calling KBUILD...
make CC=gcc-4.0 -C /h
> I wonder if anyone can shed some light on my brain?
Double check if you are missing a needed boot flag in your /boot/grub/menu.1st
i.e.*in my case* 'nohpet'
# kopt=root=/dev/hda2 ro nohpet pci=routeirq
note!
you will have to do a 'sudo update-grub' if you change anything in 'menu.1st'
are you
On Sun, 01 Oct 2006 01:20:07 +0200, chris wakefield wrote:
> I wonder if anyone can shed some light on my brain?
Is there any special reason why you are compiling your own kernel? Aren't
stock Debian kernels not good enough? I guess if you need some particular
options it's better to take Debian's
Greetings all,
Compiling a kernel for a ASUS M2NPV-VM. With an amd64-x2 dual core. 2
gig's mem.
Been compiling kernels since 2.2 and for some reason my latest kernels
are all crashing. First it pauses while detecting the first cpu, then
goes on to crash at the point where the scheduler (cfq) seem
Aaron M. Ucko napsal(a):
Ondrej Zima <[EMAIL PROTECTED]> writes:
objdump: arch/x86_64/boot/compressed/.tmp_misc.o: File format is ambiguous
objdump: Matching formats: elf32-i386 elf32-i386-freebsd
This looks like http://bugs.debian.org/380539 ; if you have the
binutils-multiarch package insta
Ondrej Zima <[EMAIL PROTECTED]> writes:
> objdump: arch/x86_64/boot/compressed/.tmp_misc.o: File format is ambiguous
> objdump: Matching formats: elf32-i386 elf32-i386-freebsd
This looks like http://bugs.debian.org/380539 ; if you have the
binutils-multiarch package installed, removing it should
Hi all,
I make update to the latest Debian kernel source, but I run into some
wierd things... see log of compiling.
== making target debian/stamp-build-kernel [new prereqs:
sanity_check stamp-kernel-conf]==
This is kernel package version 10.050.
/usr/bin/makeARCH=x86_64 \
On Fri, Jul 07, 2006 at 02:26:39PM +0200, Goswin von Brederlow wrote:
> Emmanuel Fleury <[EMAIL PROTECTED]> writes:
>
> > mons wrote:
> >> Hi.
> >> I want to compile a kernel for my other computer. I have a ia32 chrooted
> >> enviroment. I tried
Emmanuel Fleury <[EMAIL PROTECTED]> writes:
> mons wrote:
>> Hi.
>> I want to compile a kernel for my other computer. I have a ia32 chrooted
>> enviroment. I tried to compile it but when I do make menuconfig i
>> allways have to choose only ia64 kernels.
I hig
mons wrote:
> Hi.
> I want to compile a kernel for my other computer. I have a ia32 chrooted
> enviroment. I tried to compile it but when I do make menuconfig i
> allways have to choose only ia64 kernels.
> What shoud I change in chroot32 enviroment to make ia32 kernels?
> Please
Hi.
I want to compile a kernel for my other computer. I have a ia32 chrooted
enviroment. I tried to compile it but when I do make menuconfig i
allways have to choose only ia64 kernels.
What shoud I change in chroot32 enviroment to make ia32 kernels?
Please, wrote it that so noob could
On Wednesday 28 June 2006 11:09, Jo Shields wrote:
> Francesco Pietra wrote:
> > I already received (with thanks) useful guidelines how to compile but I
> > realize that I have to clear my mind and perhaps also my computer to
> > succeed.
> >
> >
Francesco Pietra wrote:
I already received (with thanks) useful guidelines how to compile but I
realize that I have to clear my mind and perhaps also my computer to succeed.
__
First what
./configure -linux
requests:
---g77 and gcc found and accepted.
---Libraries are
I already received (with thanks) useful guidelines how to compile but I
realize that I have to clear my mind and perhaps also my computer to succeed.
__
First what
./configure -linux
requests:
---g77 and gcc found and accepted.
---Libraries are tested for existence in this
Greetings list.
Does anyone know the compiler & compile options used by debian for the
linux-images? Would these be the default options or some other flags?
(I'm only a 1/64th geek)
My goal is to compile 2.6.17-1 to debian amd64 specs, etc. (or better?) Done
my own for years, comp
Emmanuel Fleury <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow wrote:
>>
>> What you actualy do need is gcc-3.4 + ia32-libs-dev on sarge and
>> libc6-dev-i386 on etch/sid.
>
> Right, I had ia32-libs-dev installed (I had a lot of try and guesses).
>
> Another point, I am using gcc-4.1 as defau
Goswin von Brederlow wrote:
>
> What you actualy do need is gcc-3.4 + ia32-libs-dev on sarge and
> libc6-dev-i386 on etch/sid.
Right, I had ia32-libs-dev installed (I had a lot of try and guesses).
Another point, I am using gcc-4.1 as default. Is it mandatory to use
gcc-3,4 for this or is gcc-4.
Emmanuel Fleury <[EMAIL PROTECTED]> writes:
> Hi all,
>
> I'm trying to compile a software in 32-bits mode on my AMD64.
>
> I installed the packages:
> o binutils-multiarch
irelevant
> o ia32-libs
irelevant
> o ... and all the packages related to these ones
Hi all,
I'm trying to compile a software in 32-bits mode on my AMD64.
I installed the packages:
o binutils-multiarch
o ia32-libs
o ... and all the packages related to these ones through the dependancies.
Then, I compiled the software with the option '-m32'.
It's quite fine
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> gp-relative relocation against dynamic symbol cobex_handleinput
> /usr/bin/ld: final link failed: Nonrepresentable section on output
>
> Any ideas? Note that libobexftp, libmulticobex and libbfb are compiled as
> static libs only.
You cannot create a
Hi,
I have a strange problem with amd64 and alpha ports as the new obexftp package
fails to compile its PERL binding (using swig). All other ports can compile
this package.
Additionally, the error messages are very cryptic and differ for amd64 and
alpha.
For amd64:
http://buildd.debian.org
> Notice that I have an libGL.so.1.2. The libGL.so.1 isn't
> that important, but you also seem to be missing it. Those
> files are part of xlibmesa-gl.
>
> Do you have some nvidia drivers or something installed?
>
>
> Kurt
Thank you Kurt
You were right, sorry I shouldn't have overlooked that l
On Sat, Mar 25, 2006 at 05:37:11PM +0100, Gudjon I. Gudjonsson wrote:
> $ ls -la /usr/X11R6/lib/libGL*
> -rw-r--r-- 1 root root 1005478 2006-03-22 09:21 /usr/X11R6/lib/libGL.a
> lrwxrwxrwx 1 root root 12 2006-03-25 17:03 /usr/X11R6/lib/libGL.so ->
> libGL.so.1.2
> -rw-r--r-- 1 root root 9157
Þann Laugardagur 25. mars 2006 16:56 skrifaði Kurt Roeckx:
> On Sat, Mar 25, 2006 at 04:26:47PM +0100, Gudjon I. Gudjonsson wrote:
> > -L/usr/share/qt3/lib -L/usr/X11R6/lib -lz -lqt-mt -lGLU -lGL -lXmu
> > -lpthread /usr/bin/ld: /usr/X11R6/lib/libGL.a(glapi.o): relocation
> > R_X86_64_32 against `a
On Sat, Mar 25, 2006 at 04:26:47PM +0100, Gudjon I. Gudjonsson wrote:
> -L/usr/share/qt3/lib -L/usr/X11R6/lib -lz -lqt-mt -lGLU -lGL -lXmu -lpthread
> /usr/bin/ld: /usr/X11R6/lib/libGL.a(glapi.o): relocation R_X86_64_32 against
> `a local symbol' can not be used when making a shared object; recomp
Þann Laugardagur 25. mars 2006 11:47 skrifaði Kurt Roeckx:
> On Sat, Mar 25, 2006 at 11:03:47AM +0100, Gudjon I. Gudjonsson wrote:
> > Hi
> >Has anyone had the following problem when compiling C++ programs:
> > "/usr/X11R6/lib/libGL.a: could not read symbols: Bad value"
> > I found this on the
On Sat, Mar 25, 2006 at 11:03:47AM +0100, Gudjon I. Gudjonsson wrote:
> Hi
>Has anyone had the following problem when compiling C++ programs:
> "/usr/X11R6/lib/libGL.a: could not read symbols: Bad value"
> I found this on the internet which is the same problem in Ubuntu.
> http://www.cegui.org.
Hi
Has anyone had the following problem when compiling C++ programs:
"/usr/X11R6/lib/libGL.a: could not read symbols: Bad value"
I found this on the internet which is the same problem in Ubuntu.
http://www.cegui.org.uk/mantis/view.php?id=7
But my question is the following. Assuming the problem s
Hello everybody!
I would like to draw your attention the bug
http://ati.cchtml.com/show_bug.cgi?id=297 filed against 64-bit version
of ATI fglrx driver.
Quote:
The problem seems to be in
/lib/modules/fglrx/build_mod/firegl_agpgart/firegl_wrap.* (first appeared in
8.20.8). It seems to be based on
On Saturday 31 December 2005 06:18, Craig Hagerman wrote:
> Hi,
> I did
>
> %make clean && make bzImage && make modules && make modules_install
>
Don't forget to also delete /lib/modules/2.6.14/... before make
modules_install
Otherwise you might be mixing incompatible modules (unlikely).
Hi again,
I was not able to figure out all of the sound errors, but I have fixed
everything. I think that (maybe) the problem had to do with compiling
and installing a kernel manually vs. the debian way. I have been
wrestling with a new kernel compile all last night and this morning
and tried to
Hi,
I have spent the past day or so compiling and re-compiling a kernel to
try to get everything working right. My original reason was to be able
to activate dma. Fortunately DMA now works correctly. Now I have a new
problem - sound doesn't work. I am sure that I have the correct
choices selected
Hi all.
I trying compile qmail via qmailrocks.org on Debian Sarge amd64.
I get a following error while compiling ucspi-tcp-0.88
linux:/usr/src/qmail/ucspi-tcp-0.88#
make
./load tcpserver rules.o remoteinfo.o timeoutconn.o cdb.a \dns.a time.a unix.a byte.a `cat socket.lib
Hi all.
I trying compile qmail via qmailrocks.org on Debian Sarge amd64.
I get a following error while compiling ucspi-tcp-0.88
linux:/usr/src/qmail/ucspi-tcp-0.88# make ./load tcpserver rules.o remoteinfo.o timeoutconn.o cdb.a \dns.a time.a unix.a byte.a `cat socket.lib
Went ahead and gave it a try. These messages are apparently only
a warning. The kernel will compile properly. I am currently writing
from the system booted with the new kernel.
lance
Lance Hoffmeyer wrote:
Hey all,
I am running
Linux version 2.6.8-11-amd64-generic ([EMAIL PROTECTED
Hey all,
I am running
Linux version 2.6.8-11-amd64-generic ([EMAIL PROTECTED])
(gcc version 3.4.4 20050314 (prerelease) (Debian 3.4.3-13))
I want to recompile the kernel mainly because I want framebuffer support.
Using make-kpkg I get the following warning:
$make-kpkg --initrd --revision=cu
Le 29.06.2005 05:57:20, Stephen Gran a écrit :
This one time, at band camp, Jean-Luc Coulon (f5ibh) said:
> Hi,
>
> I'm trying to compile cinelerra (video editing program) in the 64
bit
> environment.
>
> After some tweaking, it fails with the following messages:
> /us
This one time, at band camp, Jean-Luc Coulon (f5ibh) said:
> Hi,
>
> I'm trying to compile cinelerra (video editing program) in the 64 bit
> environment.
>
> After some tweaking, it fails with the following messages:
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-
On Tue, Jun 28, 2005 at 06:29:24PM +, Jean-Luc Coulon (f5ibh) wrote:
> Hi,
>
> I'm trying to compile cinelerra (video editing program) in the 64 bit
> environment.
>
> After some tweaking, it fails with the following messages:
>
> gcc-4.0 -shared .libs/
El mar, 28-06-2005 a las 18:29 +, Jean-Luc Coulon (f5ibh) escribió:
> Hi,
>
> I'm trying to compile cinelerra (video editing program) in the 64 bit
> environment.
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux/4.0.1/../../../../lib64/libavcodec.a(dsputil_mm
Hi,
I'm trying to compile cinelerra (video editing program) in the 64 bit
environment.
After some tweaking, it fails with the following messages:
gcc-4.0 -shared .libs/atom.o .libs/avi_hdrl.o .libs/avi_idx1.o
.libs/avi_movi.o .libs/avi_strl.o .libs/avi_odml.o .libs/avi_ix.o
Hello Bruno,
Bruno Ducrot wrote:
On Wed, Jun 22, 2005 at 10:14:46PM +0200, Bruno Ducrot wrote:
linux/arch/i386/kernel/cpu/cpufreq/Kconfig contains those line:
Same for
linux/arch/x86_64/kernel/cpufreq/Kconfig (oops)
config X86_POWERNOW_K8_ACPI
bool
depends on X86_POWERNOW_
On Wed, Jun 22, 2005 at 10:14:46PM +0200, Bruno Ducrot wrote:
> linux/arch/i386/kernel/cpu/cpufreq/Kconfig contains those line:
Same for
linux/arch/x86_64/kernel/cpufreq/Kconfig (oops)
>
> config X86_POWERNOW_K8_ACPI
> bool
> depends on X86_POWERNOW_K8 && ACPI_PROCESSOR
> dep
On Wed, Jun 22, 2005 at 09:14:05PM +0200, Mart Frauenlob wrote:
> Hello,
>
> Bruno Ducrot wrote:
> >On Wed, Jun 22, 2005 at 05:56:27PM +0200, Mart Frauenlob wrote:
> >
> >>This only happens if i set AMD PowerNowK8 to be compiled directly into
> >>the kernel.
> >
> >
> >But acpi_processor is compi
Hello,
Bruno Ducrot wrote:
On Wed, Jun 22, 2005 at 05:56:27PM +0200, Mart Frauenlob wrote:
This only happens if i set AMD PowerNowK8 to be compiled directly into
the kernel.
But acpi_processor is compiled as a module, correct? If yes it's a
kconfig trouble.
CONFIG_ACPI=y
CONFIG_ACPI_BOOT
On Wed, Jun 22, 2005 at 05:56:27PM +0200, Mart Frauenlob wrote:
>
> This only happens if i set AMD PowerNowK8 to be compiled directly into
> the kernel.
But acpi_processor is compiled as a module, correct? If yes it's a
kconfig trouble.
--
Bruno Ducrot
-- Which is worse: ignorance or apath
]: Leaving directory `/usr/src/kernel-source-2.6.8'
make: *** [stamp-build] Error 2
--
This only happens if i set AMD PowerNowK8 to be compiled directly into
the kernel.
LKM compile is not affected.
I tried gcc 3.3 and 3.4.
uname -r
2.6.8-11-amd6
r conflicts with the NVIDIA driver, please
> reconfigure your kernel and *disable* rivafb support, then
> try installing the NVIDIA kernel module again.
>
> *** Failed rivafb sanity check. Bailing out! ***
>
> .. What on earth?? Do I need to compile my own kernel? I
Actually it may require a kernel recompile, because the rivafb is
present in the setup, in the .config file, and that's where it needs to be
removed for the compile to succeed. I guess. If doing that, and removing
the rivafb.ko, it may work. :-)
/n
On Wed, 25 May 2005, Jaime Ochoa Ma
gt; Your kernel was configured to include rivafb support!
>
> The rivafb driver conflicts with the NVIDIA driver, please
> reconfigure your kernel and *disable* rivafb support, then
> try installing the NVIDIA kernel module again.
>
> *** Failed rivafb sanity check. Bailing
again.
*** Failed rivafb sanity check. Bailing out! ***
.. What on earth?? Do I need to compile my own kernel? I've
installed an SMP kernel image via apt-get. Do I need to roll my own
kernel to get rid of this "rivafb" support? Please no!
Actually I can find a kernel module in:.
On Monday 09 May 2005 18:24, Ernest jw ter Kuile wrote:
> I suspect, however, you would be beter off on the gcc list. amd64 is
> officially supported there.
I will do this next. Thought it would fit in here better, because I only have
this problem with debian-amd64, same gcc-versions on from other
Mario <[EMAIL PROTECTED]> writes:
> Hi everyone!
>
> I'm trying to compile the source added below, which works on many other
> systems (32 Bit SuSE and Debian, 64Bit SuSE) but not with debian-amd64.
>
> My current compiler says the following, but the problem has be
if you want people to test, then this is missing.
> boost/spirit/core.hpp
I suspect, however, you would be beter off on the gcc list. amd64 is
officially supported there.
Cheers,
Ernest.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL
Hi everyone!
I'm trying to compile the source added below, which works on many other
systems (32 Bit SuSE and Debian, 64Bit SuSE) but not with debian-amd64.
My current compiler says the following, but the problem has been present in
amd64-pure64 repository since I started using debian-
On Sun, Apr 24, 2005 at 10:34:56PM +0200, Leopold Palomo Avellaneda wrote:
> I have followed your instructions and I could create a kernel for i386.
> However, I would like to configure it (make menuconfig) and I couldn't do it.
> Please, could you tell me how?. I have tested:
> export ARCH=i386;
1 - 100 of 129 matches
Mail list logo
