make-kpkg ( line 2: syntax error: unexpected end of file)

2003-08-14 Thread Pete Trachy
I have tried compiling the 2.4.21 and available 2.6
kernels using the debian source packages.  I have been
following the instructions on the newbie doc
(http://newbiedoc.sourceforge.net/system/kernel-pkg.html)
but when I try to compile either kernel version i get
almost exactly the same error after running:

fakeroot make-kpkg --append-to-version=.20030812 kernel_image

Which is (for the 2.6 try):

lots and lots of output..
.
and finally

make[1]: Leaving directory
`/usr/src/kernel-source-2.6.0-test2'
echo done   stamp-build
/usr/bin/make -f /usr/share/kernel-package/rules
real_stamp_image
make[1]: Entering directory
`/usr/src/kernel-source-2.6.0-test2'
/bin/sh: -c: line 2: syntax error: unexpected end of file
make[1]: *** [real_stamp_image] Error 2
make[1]: Leaving directory
`/usr/src/kernel-source-2.6.0-test2'
make: *** [kernel-image-deb] Error 2

Also I am on unstable.

Thanks in advance for any help.

Pete

ps I'm doing this for an IBM T40, does anyone know what is
the best processor type to pick for pentium m?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: make-kpkg ( line 2: syntax error: unexpected end of file)

2003-08-14 Thread Engosh
On Tue, 12 Aug 2003 17:37:19 +0800 (CST)
Pete Trachy [EMAIL PROTECTED] wrote:

 I have tried compiling the 2.4.21 and available 2.6
 kernels using the debian source packages.  I have been
 following the instructions on the newbie doc
 (http://newbiedoc.sourceforge.net/system/kernel-pkg.html)
 but when I try to compile either kernel version i get
 almost exactly the same error after running:
 
 fakeroot make-kpkg --append-to-version=.20030812 kernel_image
 
 Which is (for the 2.6 try):
 
 lots and lots of output..
 .
 and finally
 
 make[1]: Leaving directory
 `/usr/src/kernel-source-2.6.0-test2'
 echo done   stamp-build
 /usr/bin/make -f /usr/share/kernel-package/rules
 real_stamp_image
 make[1]: Entering directory
 `/usr/src/kernel-source-2.6.0-test2'
 /bin/sh: -c: line 2: syntax error: unexpected end of file
 make[1]: *** [real_stamp_image] Error 2
 make[1]: Leaving directory
 `/usr/src/kernel-source-2.6.0-test2'
 make: *** [kernel-image-deb] Error 2
 
 Also I am on unstable.
 
 Thanks in advance for any help.
 
 Pete
 
 ps I'm doing this for an IBM T40, does anyone know what is
 the best processor type to pick for pentium m?
 

Yes, I've got the same errors as you, but no with the 2.6.0-test3 kernel.
Another problem I have is that with the 2.6 kernel I'm not able to make kernel-nvidia 
module. And have somebody tried to execute modprobe with the 2.6 kernel, 'cause I get 
some errors and I'd like to know if that is normal.

Thanx
Engosh

 
 -- 
 To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: make-kpkg ( line 2: syntax error: unexpected end of file)

2003-08-14 Thread Jeronimo Pellegrini
 fakeroot make-kpkg --append-to-version=.20030812 kernel_image
 
 Which is (for the 2.6 try):
 
 lots and lots of output..
 .
 and finally
 
 make[1]: Leaving directory
 `/usr/src/kernel-source-2.6.0-test2'
 echo done   stamp-build
 /usr/bin/make -f /usr/share/kernel-package/rules
 real_stamp_image
 make[1]: Entering directory
 `/usr/src/kernel-source-2.6.0-test2'
 /bin/sh: -c: line 2: syntax error: unexpected end of file

What version oa kernel-package? See http://bugs.debian.org/204856
(It's fixed in the latest version -- I've compiled test3 here without
problems)

J.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: make-kpkg ( line 2: syntax error: unexpected end of file)

2003-08-14 Thread Jeronimo Pellegrini
 The interfaces have also changed, meaning that the nvidia driver you got from
 nvidia will not work with newer kernels without some hacking.  Just google
 around and check nvnews.com, as there are plenty of kernel hackers out there
 on the bleeding edge that have gotten theirs to work and then supplied patches.

I've heard the best one is this: http://minion.de/  (the guy seem to
have worked for NVidia).

J.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: make-kpkg ( line 2: syntax error: unexpected end of file)

2003-08-12 Thread Roberto Sanchez
 --- Engosh [EMAIL PROTECTED] escribió: 
 
 Yes, I've got the same errors as you, but no with the 2.6.0-test3 kernel.
 Another problem I have is that with the 2.6 kernel I'm not able to make
 kernel-nvidia module. And have somebody tried to execute modprobe with the
 2.6 kernel, 'cause I get some errors and I'd like to know if that is normal.

As of kernel 2.5.48, you must have the module-init-tools package (instead of
modutils) to be able to deal with kernel modules.

The interfaces have also changed, meaning that the nvidia driver you got from
nvidia will not work with newer kernels without some hacking.  Just google
around and check nvnews.com, as there are plenty of kernel hackers out there
on the bleeding edge that have gotten theirs to work and then supplied patches.

That's how I got my binary nforce drivers working under 2.6.0-test1 and -test2.

-Roberto

___
Yahoo! Messenger - Nueva versión GRATIS
Super Webcam, voz, caritas animadas, y más...
http://messenger.yahoo.es


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



tar - unexpected end of file

2002-02-09 Thread Gerhard Engler



Hallo Mailingliste,

ich habe vor dem Umstieg von Suse auf Debian meine 
Daten per tar auf eine zweite Platte gesichert. Leider mußte ich die z-Option 
einschalten, da ansonsten die Daten nicht draufgepaßt hätten.

Wenn ich nun 

tar zxvf /platte/datei.tar.gz 

eingebe werden einige Dateien entpackt. Leider 
bleibt der Vorgang mit der Fehlermeldung

gzip: stdin: unexpected end of file
tar: Unerwartetes Dateiende im Archiv.
tar: Kindprozeß gab Status 1 zurück.
tar: Fehler beim Beenden, verursacht, durch 
vorhergehenden Fehler

Was kann ich tun um zumindest einen Teil noch zu 
retten?

Vielen Dank!


Gerhard


Re: tar - unexpected end of file

2002-02-09 Thread Gerhard Engler

   tar zxvf /platte/datei.tar.gz 
  versuch mal
  tar xvfz /platte/datei.tar.gz
  manchmal hilft's,

Leider kommt da nur das gleiche Ergebnis.

Vielen Dank!

Gerhard


-- 
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)




Re: unexpected end of file

2000-01-17 Thread ulla . russell



Ethan you were partially correct in your reply.

When I comment out the if structure that tests for the
existence of .bashrc, and 'sources' it if it does exist,
there are no problems. That is, I can source the file 
without any problems.

However the problem seems still to be elsewhere. 

When I uncomment the if structure I am able to run the file as
an argument to bash, i.e bash .profile or, after changing
the files permissions, as a shell programme ./.profile. 
This suggest (to me at least) that the problem is not one 
of syntax.

It looks like something is broken. 

I have tried creating and then sourcing simple shell scripts 
and they suffer from the same problem.

Do you or anyone else have any sugestions?

TIA and thanks for your previous reply.




Its probably not as complicated as you are making it, more likely 
there is just a stray  or something

if there are any if then structures make sure they are terminated 
with a fi, all { have a matching } and so on.

all it takes is one stray  ' or ` to cause that, bash keeps looking 
for the closing quote, or the fi or whatever and if it gets to the 
end of file it complains.

Ethan




Re: unexpected end of file

2000-01-17 Thread Dänzer


--- [EMAIL PROTECTED] wrote:

 Ethan you were partially correct in your reply.
 
 When I comment out the if structure that tests for the
 existence of .bashrc, and 'sources' it if it does exist,
 there are no problems. That is, I can source the file 
 without any problems.
 
 However the problem seems still to be elsewhere. 
 
 When I uncomment the if structure I am able to run the file as
 an argument to bash, i.e bash .profile or, after changing
 the files permissions, as a shell programme ./.profile. 
 This suggest (to me at least) that the problem is not one 
 of syntax.
 
 It looks like something is broken. 
 
 I have tried creating and then sourcing simple shell scripts 
 and they suffer from the same problem.
 
 Do you or anyone else have any sugestions?

 Its probably not as complicated as you are making it, more likely 
 there is just a stray  or something
 
 if there are any if then structures make sure they are terminated 
 with a fi, all { have a matching } and so on.
 
 all it takes is one stray  ' or ` to cause that, bash keeps looking 
 for the closing quote, or the fi or whatever and if it gets to the 
 end of file it complains.

IIRC I used to get the error in the Subject when I forgot to add a blank line
at the end of scripts.


Michel


=
Software is like sex; it's better when it's free
 -- Linus Torvalds

If you continue running Windows, your system may become unstable.
 -- Windows 95 BSOD
__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com


Re: unexpected end of file

2000-01-16 Thread Hartmut Figge
[EMAIL PROTECTED] wrote:

 'bash: /root/.profile: line 11: syntax error: unexpected end of file'

i would would view this file with mc, switching to hex-mode and look for
suspicious characters.

-- 
hafi


Re: unexpected end of file

2000-01-16 Thread ulla . russell

I do not have mc installed. I used the -x switch on the f
ile (od -x .profile, this also allows files to be viewed 
in hex).

I didn't see anything suspicious. Does anyone have any
other ideas? 

If I was to install midnight commander what instruction 
would I have to give to view files in hex?

The problem is worse than I at first realised, since this
files contains $PATH for root and it's not being loaded. I 
suppose there are ways around this problem, but it would
be nice to find out why the problem arose in the first 
place or at least how to fix it.







At 01:38 16.1.2000 +0100, you wrote:
[EMAIL PROTECTED] wrote:

 'bash: /root/.profile: line 11: syntax error: unexpected end of file'

i would would view this file with mc, switching to hex-mode and look for
suspicious characters.

-- 
hafi


-- 
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED] 
/dev/null




Re: unexpected end of file

2000-01-16 Thread Ethan Benson

On 16/1/2000 [EMAIL PROTECTED] wrote:


I do not have mc installed. I used the -x switch on the f
ile (od -x .profile, this also allows files to be viewed
in hex).

I didn't see anything suspicious. Does anyone have any
other ideas?

If I was to install midnight commander what instruction
would I have to give to view files in hex?

The problem is worse than I at first realised, since this
files contains $PATH for root and it's not being loaded. I
suppose there are ways around this problem, but it would
be nice to find out why the problem arose in the first
place or at least how to fix it.


Its probably not as complicated as you are making it, more likely 
there is just a stray  or something


if there are any if then structures make sure they are terminated 
with a fi, all { have a matching } and so on.


all it takes is one stray  ' or ` to cause that, bash keeps looking 
for the closing quote, or the fi or whatever and if it gets to the 
end of file it complains.


Ethan


unexpected end of file

2000-01-15 Thread ulla . russell


I was using my computer, and logged in as root
using su and I started getting the following
irritating message.

'bash: /root/.profile: line 11: syntax error: unexpected end of file'

I have no idea why this started to appear. I
been using debian 2.1 now for almost a year
and this is the first time that this has happened.

I now get this message whenever I login as root. 
my other account works o.k.

I used 'od -c /root/.profile' and 'od -b /root/.profile'
to see if I could see anything suspicious but I
didn't find anything. 

Can anyone help ?

TIA