place, two places, but this had
gotten out of hand (since upgrading the kernel undoes what once worked and
introduces even more places to hit, it seems.
Should I file a bug about this? Documentation of this problem and fixes? Any
ideas?
This touches many compiles of kde applications, for example
Hi,
I've had a few problems trying to build a fresh 2.6.10 or 2.6.11
kernel. Nothing fancy. With gcc-4.0 I get tons of warnings, and
eventually it barfs when it gets to:
> CC drivers/eisa/eisa-bus.o
>cc1: warnings being treated as errors
>drivers/eisa/eisa-bus.c:421: warning: pointer targets
If it didn't get automatically created for you, then you can make a
new one using mkinitrd. Don't forget to check out
/etc/mkinitrd/{mkinitrd.conf,modules}. You may need something like:
ext3
ext2
in the modules if you need ext3 on boot.
% mkinitrd -o /boot/initrd.img-... /lib/modules/...
Andrew
On Mon, Jan 28, 2002 at 01:29:03AM -0500, James Lindenschmidt wrote:
> Adam Majer Spoke Thusly:
> > On Mon, Jan 28, 2002 at 12:27:47AM -0500, James
> Lindenschmidt wrote:
> > > Greetings. Yet another not-newbie, not-guru
> > > generated during the make-kpkg kernel_image?
[snip]
> >
> > If you are
Osamu Aoki Spoke Thusly:
> On Mon, Jan 28, 2002 at 01:29:03AM -0500, James
Lindenschmidt wrote:
> > No, that's the point. I'm trying to do this The Debian
> > Way, using apt-get install kernel-source and make-dpkg
> > kernel_image.
>
> # dpkg -i kernel-image*
>
> should replace it if you have new
On Mon, Jan 28, 2002 at 01:29:03AM -0500, James Lindenschmidt wrote:
>
> No, that's the point. I'm trying to do this The Debian Way,
> using apt-get install kernel-source and make-dpkg
> kernel_image.
>
# dpkg -i kernel-image*
should replace it if you have new system. At one point in history
Adam Majer Spoke Thusly:
> On Mon, Jan 28, 2002 at 12:27:47AM -0500, James
Lindenschmidt wrote:
> > Greetings. Yet another not-newbie, not-guru
> > end-user-type question here.
> >
> > I'm still having trouble compiling the kernel. I
> > scrapped the previous attempt using a kernel from
> > kernel
On Mon, Jan 28, 2002 at 12:27:47AM -0500, James Lindenschmidt wrote:
> Greetings. Yet another not-newbie, not-guru end-user-type
> question here.
>
> I'm still having trouble compiling the kernel. I scrapped
> the previous attempt using a kernel from kernel.org and got
> the source directly fro
Greetings. Yet another not-newbie, not-guru end-user-type
question here.
I'm still having trouble compiling the kernel. I scrapped
the previous attempt using a kernel from kernel.org and got
the source directly from debian.
The kernel compiled OK, but when I updated LILO and ran it,
I got the
* Greg Wiley ([EMAIL PROTECTED]) [010823 17:56]:
> Hi all-
>
> I have the feeling I am missing something obvious:
>
> If I install one of the pre-compiled kernel packages from stable, is a
> copy of the configuration file used for its build stored somewhere on
> my system?
Look in your /boot direc
Hi all-
I have the feeling I am missing something obvious:
If I install one of the pre-compiled kernel packages
from stable, is a copy of the configuration file used
for its build stored somewhere on my system?
Thanks,
-=greg
On Mon, Jul 02, 2001 at 02:09:16PM -0500, John Foster wrote:
>
> # environment settings
> LANG=C
> CONFIG_SMP=y
> CONCURRENCY_LEVEL=2
> DEBIAN_BUILDARCH=pentium
> # EOF
The CONCURRENCY_LEVEL variable only has meaning to make-kpkg, not to
make or to anything else. So adding it to your environment
On Mon, Jul 02, 2001 at 12:51:17PM -0500, John Foster wrote:
> If I put the CONCURRENCY_LEVEL := 2 in my root environment variable will
> it be useful in allowing all of my compiled applications to run with
> maximum efficiency on my dual processor system?
No, it will only affect the (one-time) co
I want to know how to use environment variables to manage the software
compiles for a dual processor system.
I have these as what I think might work as setting. I need tips, advice
on proceeding.
# environment settings
LANG=C
CONFIG_SMP=y
CONCURRENCY_LEVEL=2
DEBIAN_BUILDARCH=pentium
# EOF
Has
Steve Kowalik wrote:
>
> On Sun, Jul 01, 2001 at 02:42:20PM -0500, S.Salman Ahmed uttered:
> >
> > Is there any way to pass the "-j " option to make when building
> > kernels using make-kpkg ?
> >
> Read the README for kernel-package.
> Make a .kernel-pkg.conf in ~ as the user you compile it as.
>
S.Salman Ahmed <[EMAIL PROTECTED]> writes:
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
Yes. See kernel-pkg.conf(5) for details.
--
Leonard Stiles <[EMAIL PROTECTED]>
On Sun, Jul 01, 2001 at 02:42:20PM -0500, S . Salman Ahmed wrote:
>
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
RTFM. 'man kernel-pkg.conf' and search for CONCURRENCY_LEVEL or just
'-j'.
> I am hoping that by passing the "-j" option to make, ker
On Sun, Jul 01, 2001 at 02:42:20PM -0500, S.Salman Ahmed uttered:
>
> Is there any way to pass the "-j " option to make when building
> kernels using make-kpkg ?
>
Read the README for kernel-package.
Make a .kernel-pkg.conf in ~ as the user you compile it as.
[EMAIL PROTECTED]:~$ grep -i concurr
On Fri, Jun 22, 2001 at 08:44:51PM +0200, Robert Waldner wrote:
> now do a `make clean` (just to get rid of the modules, mostly) and
make-kpkg clean
> re-do steps 1-3 for the second machine and the third and...
It will complain if you use machines' hostnames in
On Fri, Jun 22, 2001 at 08:17:14PM +0200, MaD dUCK wrote:
> also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
> > True, but you can/should configure and compile separately for each
> > destination architecture, optimizing appropriately.
>
> so yes, the argument that my athlon (thunde
also sprach Robert Waldner (on Fri, 22 Jun 2001 08:44:51PM +0200):
> now do a `make clean` (just to get rid of the modules, mostly) and
> re-do steps 1-3 for the second machine and the third and...
>
> when you want to re-do for the first machine, just move the appropriate
> .config back, and
On Fri, 22 Jun 2001 20:28:04 +0200, MaD dUCK writes:
>also sprach Robert Waldner (on Fri, 22 Jun 2001 08:20:41PM +0200):
>> you don´t need to maintain seperate trees of the whole source. just
>> `make (menu|x|)config`, then backup the .config-file. that´s where the
>> information you entered/c
also sprach Robert Waldner (on Fri, 22 Jun 2001 08:20:41PM +0200):
> you don´t need to maintain seperate trees of the whole source. just
> `make (menu|x|)config`, then backup the .config-file. that´s where the
> information you entered/chose is kept.
i understand... but when i change the .conf
On Fri, 22 Jun 2001 20:17:14 +0200, MaD dUCK writes:
>also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
>> True, but you can/should configure and compile separately for each
>> destination architecture, optimizing appropriately.
>
>so yes, the argument that my athlon (thunderbird act
also sprach Bob Nielsen (on Fri, 22 Jun 2001 10:42:23AM -0700):
> True, but you can/should configure and compile separately for each
> destination architecture, optimizing appropriately.
so yes, the argument that my athlon (thunderbird actually) will
outperform the others still holds. but i'd need
also sprach Nathan E Norman (on Fri, 22 Jun 2001 12:42:37PM -0500):
> I fail to see why you think compiling a kernel on an Athlon, but
> optimising for a 486 cos you're installing on a 486 is a problem.
that's what i am doing btw. and sorry, i wasn't possibly thinking
about multiple .debs, just th
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
On Fri, Jun 22, 2001 at 01:19:49PM -0400, David L. Craig wrote:
> Sean Morgan <[EMAIL PROTECTED]> wrote:
>
> > zless /usr/share/doc/kernel-package/Rationale
>
> I haven't figured out if kernel-package includes the
> patches Herbert puts into the kernel-source .debs.
> I tried to patch in 2.4.5-ac
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
On Fri, Jun 22, 2001 at 06:34:25PM +0200, MaD dUCK wrote:
> also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> > Well, for one thing, you can compile kernels on your 1GHz Athlon
> > instead of your old 486 :) Since kernel-package creates a package, it
> > can be installed anywhe
27;s cutting edge, i do a whole lot of kernel compiles.
>
> in the past, i have always used .debs unless a software was too old or
> not available, in which case i beat the tarball around and installed
> into /usr/local. by now, i do it the "debian way," and use
> dpkg-bui
Sean Morgan <[EMAIL PROTECTED]> wrote:
> zless /usr/share/doc/kernel-package/Rationale
I haven't figured out if kernel-package includes the
patches Herbert puts into the kernel-source .debs.
I tried to patch in 2.4.5-ac17 yesterday over
kernel-source-2.4.5 and ran afoul of some conflicts.
Would s
also sprach Sean Morgan (on Fri, 22 Jun 2001 12:05:19PM -0400):
> zless /usr/share/doc/kernel-package/Rationale
exaclty what i wanted. thanks!
martin; (greetings from the heart of the sun.)
\ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
--
your fly might be open
also sprach Nathan E Norman (on Fri, 22 Jun 2001 11:01:13AM -0500):
> Well, for one thing, you can compile kernels on your 1GHz Athlon
> instead of your old 486 :) Since kernel-package creates a package, it
> can be installed anywhere.
but i usually choose the appropriate kernel architecture duri
s want to have at least one
> machine that's cutting edge, i do a whole lot of kernel compiles.
>
> in the past, i have always used .debs unless a software was too old or
> not available, in which case i beat the tarball around and installed
> into /usr/local. by now, i do it the
27;s cutting edge, i do a whole lot of kernel compiles.
>
> in the past, i have always used .debs unless a software was too old or
> not available, in which case i beat the tarball around and installed
> into /usr/local. by now, i do it the "debian way," and use
> dpkg-bui
d since i always want to have at least one
> machine that's cutting edge, i do a whole lot of kernel compiles.
>
> in the past, i have always used .debs unless a software was too old or
> not available, in which case i beat the tarball around and installed
> into /usr/local. by
i love debian. seriously, apt is a work of genius and the entire
system is exactly how i want it - unlike SuSE or RedHat. since i do a
fair bit of developing and since i always want to have at least one
machine that's cutting edge, i do a whole lot of kernel compiles.
in the past, i have a
> Hello,
>
> In fact, ltx2rtf gives better results with latex2e files. it properly
> translates italic, bold face... Latex2rtf only recongnizes latex2.09 commands.
>
Would you file a bug against the latex2rtf package?
> --Nabil
>
> Shaul Karl writes:
> > You might want to consider:
> >
>
Hello,
In fact, ltx2rtf gives better results with latex2e files. it properly
translates italic, bold face... Latex2rtf only recongnizes latex2.09 commands.
--Nabil
Shaul Karl writes:
> You might want to consider:
>
> [14:10:28 /tmp]$ grep-available latex2rtf
> Package: latex2rtf
> Pr
You might want to consider:
[14:10:28 /tmp]$ grep-available latex2rtf
Package: latex2rtf
Priority: optional
Section: tex
Installed-Size: 359
Maintainer: Chris Lawrence <[EMAIL PROTECTED]>
Architecture: i386
Version: 1.8aa-5
Depends: libc6 (>= 2.1.97)
Filename: pool/main/l/latex2rtf/latex2rtf
>
> > Hello,
> >
> > I want to compile ltx2rtf on a debian machine, but the make fails. However,
> > it
> > works on a redhat 6.2, but the binary file Segm-Faults on debian 2.2. Did
> > someone have an idea on the way to get it work on debian ? Is it a problem
> > of
> > gcc version ?
>
> how
The make log is below :
hathout:~/ltx2rtf/src-gcc>make -f makefile.lnx
rm -f main.o
gcc -g -funsigned-char -c fonts.c -o fonts.o
gcc -g -funsigned-char -c cdirect.c -o cdirect.o
gcc -g -funsigned-char -c commands.c -o commands.o
gcc -g -funsigned-char -c stack.c -o stack.o
gcc
How does it fail? What's the error message?
--
Andrew J Perrin - Ph.D. Candidate, UC Berkeley, Dept. of Sociology
Chapel Hill, North Carolina, USA - http://demog.berkeley.edu/~aperrin
[EMAIL PROTECTED] - [EMAIL PROTECTED
On Tue, Feb 27, 2001 at 03:34:05PM +0100, Nabil Hathout wrote:
> Hello,
>
> I want to compile ltx2rtf on a debian machine, but the make fails. However, it
> works on a redhat 6.2, but the binary file Segm-Faults on debian 2.2. Did
> someone have an idea on the way to get it work on debian ? Is it
Hello,
I want to compile ltx2rtf on a debian machine, but the make fails. However, it
works on a redhat 6.2, but the binary file Segm-Faults on debian 2.2. Did
someone have an idea on the way to get it work on debian ? Is it a problem of
gcc version ?
thank you,
--Nabil
>
> I installed slink on my laptop, and compiled my kernel with
> everything I need. Now when I try loading my PCMCIA netcard, I
> get some unresolved symbols. I compiled the ne.o net driver as a
> module, and that reduced the number of symbols not found, but are
> still complaining about 2 fu
I installed slink on my laptop, and compiled my kernel with
everything I need. Now when I try loading my PCMCIA netcard, I
get some unresolved symbols. I compiled the ne.o net driver as a
module, and that reduced the number of symbols not found, but are
still complaining about 2 functions it ca
compiles (2.0.36) work like a dream on both machines now, just as I
would expect them to ! Well at least as far as the make 'dep' 'clean' and
'zImage' go. I still have to test make 'modules' and 'modules_install'. But
I am now confident all is OK.
S
On Fri, Jan 15, 1999 at 09:02:38AM +, Nidge Jones wrote:
>
> Stephen Pitts Writes..
>
> > Whats wrong with the kernel compile? You shouldn't need anything from
> > oldlibs to make that work. What version do you have?
>
> Version of what !
>
The kernel. Sorry, I was unclear.
> > In a nutsh
Stephen Pitts Writes..
> Whats wrong with the kernel compile? You shouldn't need anything from
> oldlibs to make that work. What version do you have?
Version of what !
> In a nutshell, you need the -dev version of any library that a program needs.
> Example:
> To compile the kernel, you need
>
>
> Now I run Debian 2.0, I fiond a lot of my old stuff won't compile !
>
> What packages do i need to install from the oldlibs section to allow this.
> In particular to allow my kernel compile to work again, as at the moment it
> refuses to do just such.
The oldlibs section is mostly for pro
On Thu, Jan 14, 1999 at 10:47:32PM +, Nidge Jones wrote:
>
> Now I run Debian 2.0, I fiond a lot of my old stuff won't compile !
>
> What packages do i need to install from the oldlibs section to allow this.
> In particular to allow my kernel compile to work again, as at the moment it
> refus
Now I run Debian 2.0, I fiond a lot of my old stuff won't compile !
What packages do i need to install from the oldlibs section to allow this.
In particular to allow my kernel compile to work again, as at the moment it
refuses to do just such.
Is there anything else I need to do too !
Thanks in
It is true. Dynamically linked against glibc.
Thaths
--
The truth is not out there
The truth is not out there
The truth us not
-- Bart Simpson, "The Sprintfield Files"
Sudhakar C13n International Websites Enginee
This might have been passed around on the developer list but one of
the Debian developers(Ben Gertzfield <[EMAIL PROTECTED]>) used Debian(hamm)
to sucessfully compile a beta copy of the upcomming Netscape source
release. Check out http://everybody.got.net/~che/my-day.html for a nice
story about his
Evan Harris writes:
> reference to `_ctype'" messages on the link step, although my "hello,
> world" test program will compile and link (but nothing else will).
Please send the output from 'dpkg -l' and from compiling your program
with 'gcc -v'.
David
--
David EngelOptica
;just in case") several
times in the course of trying to get this working.
A few days ago, I tried kludging around the problem like your
suggestion, and then everything compiles fine, but on the link step, of
larger packages (like the kernel) I get back a bunch of "undefined
refer
It looks as if you aren't getting the definition of wchar_t.
To kluge around the problem put "typedef unsigned long wchar_t;" before
line 333 in stdio.h . The correct way to fix this is to get the latest
libc and libc-dev packages and install them. If the problem doesn't go
away, tell us.
OK... I've beat my head on this for long enough, maybe some of you can
help me out.
I upgraded my R6 system to 1.1beta last week, and after a few days (and
nights) of tweaking, I got everything setup to my liking... except
compiling. For some unknown reason, when I try to compile anything, I g
60 matches
Mail list logo
