Re: problems installing g++

2003-09-24 Thread A. Novruzi
Well,

The problem was urgent and I need the compiler. 
So ... reinstall Debian was the only solution. 

Now that I am reintalling my CDRW, I have difficulties.
I have compiler the kernel with the right options as said in
CDRW-how-to (and this did work in the previous system) but 
I have this complain:

/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
unregister_cdrom_Rsmp_703d3575
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
cdrom_release_Rsmp_b388b28c
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
cdrom_number_of_slots_Rsmp_5d8f3672
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
register_cdrom_Rsmp_5a61744f
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
cdrom_media_changed_Rsmp_0054e9fe
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
cdrom_ioctl_Rsmp_bb7265aa
/lib/modules/2.4.22/kernel/drivers/scsi/sr_mod.o: unresolved symbol
cdrom_open_Rsmp_837500f7


Any help? Thank you
Arian




Sebastian Kapfer [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED]...
 On Fri, 19 Sep 2003 00:40:12 +0200, A. Novruzi wrote:
 
  Now, I try to install g++. The system complains different problems
  like the package x requires package y, while y requires x. So it does
  not install g++.
 
 Please show the exact message. Probably it's just some old package which
 apt-get doesn't dare to remove. Once you remove it manually, the
 installation should work.
 
  My previous g++ worked perfeclty but what I have now, gcc, it does not
  know any *.h classes.
 
 What's a *.h class? Do you mean header files?
 
  Do I have to make a new install of my Debian or somthing better is possible.
 
 No, I'm 99% sure that you don't have to reinstall.
 
 -- 
 Best Regards,   |   Hi! I'm a .signature virus. Copy me into
  Sebastian  |   your ~/.signature to help me spread!


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



problems installing g++

2003-09-18 Thread A. Novruzi
Hi,

After some problems I had with libc6 version, I made an updrage with 
apt-get dist-upgrade.

Now, I try to install g++. The system complains different problems
like the package x requires package y, while y requires x. So it does
not install g++.

How one can deal with this problem?
My previous g++ worked perfeclty but what I have now, gcc, it does not
know any *.h classes.

Do I have to make a new install of my Debian or somthing better is possible.

Thank you for any help!
Arian


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



Re: problems installing g++

2003-09-18 Thread Colin Watson
On Thu, Sep 18, 2003 at 03:07:33PM -0700, A. Novruzi wrote:
 After some problems I had with libc6 version, I made an updrage with 
 apt-get dist-upgrade.
 
 Now, I try to install g++. The system complains different problems
 like the package x requires package y, while y requires x. So it does
 not install g++.

Please, never try to summarize error messages; that just makes them
harder to interpret. Just quote the original error message exactly and
let your audience deal with figuring it out.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


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



Re: problems installing g++

2003-09-18 Thread Sebastian Kapfer
On Fri, 19 Sep 2003 00:40:12 +0200, A. Novruzi wrote:

 Now, I try to install g++. The system complains different problems
 like the package x requires package y, while y requires x. So it does
 not install g++.

Please show the exact message. Probably it's just some old package which
apt-get doesn't dare to remove. Once you remove it manually, the
installation should work.

 My previous g++ worked perfeclty but what I have now, gcc, it does not
 know any *.h classes.

What's a *.h class? Do you mean header files?

 Do I have to make a new install of my Debian or somthing better is possible.

No, I'm 99% sure that you don't have to reinstall.

-- 
Best Regards,   |   Hi! I'm a .signature virus. Copy me into
 Sebastian  |   your ~/.signature to help me spread!


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



Re: How to change a symlink without breaking anything (problems with g++)

2003-07-02 Thread Colin Watson
On Tue, Jul 01, 2003 at 06:50:48PM -0400, David Z Maze wrote:
 Morten Eriksen [EMAIL PROTECTED] writes:
  What is the correct manner of changing a symlink file belonging to a
  Debian package? Is it sufficient to just rm and re-link, or should I
  use any of the package-handling tools?
 
 You can't.  (Well, you can, but the next time you upgrade the package,
 your change will be overwritten.)  If the package in question uses
 alternatives, you can use update-alternatives or directly change the
 link in /etc/alternatives.

There's one way you've missed: dpkg-divert. I'd say that's the correct
choice here.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


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



Re: How to change a symlink without breaking anything (problems with g++)

2003-07-02 Thread Marc Wilson
On Tue, Jul 01, 2003 at 08:14:34PM +0200, Morten Eriksen wrote:
 (In case someone is interested, I'm asking because I just stumbled
 over a surprising issue with the g++ packages: doing an
 
# apt-get install g++
 
 installed g++-3.3 (I was expecting just an upgrade to the previously
 installed g++-2.95), and made /usr/bin/g++ into a symlink pointing to
 it.

Why is this surprising?  This isn't happening in Woody, so you're either
using Sarge or Sid.  The C++ transition has endlessly been debated and
beaten to death in a variety of public fora... if you don't know about it,
you're living under a rock and probably shouldn't be using anything other
than stable.

 Just switching g++ versions like this is bound to cause mayhem for
 all development against any C++ libraries on the system already
 compiled with g++ v2.95, so I'm surprised that this happens just like
 that from the testing branch..?

Yep.  Amazingly enough, Debian planned this transition, and packages
needing to move to the new ABI are doing so.  Perhaps you haven't noticed
all the packages now with c102 in their names?  Sid is pretty much
complete, I think... Sarge probably has a way to go.  I've not updated my
Sarge box in a while so I don't know for sure.

Locally compiled applications, of course, have the potential to break.
OTOT, if you're compiling stuff locally, the assumption is that you have at
least minimal clue.

 Removing the g++-3.3 package doesn't
 work either, as apt-get seems to now refuse to remove or install
 _either_ g++-2.95 or g++-3.3 -- it insists on having both? Weird.)

So?  The compilers are independent... use 2.95 when you need to and use 3.3
when you need to.  Building kernels, for example, should not be done with
gcc 3.3 just yet (yes, I'm sure there's some idiot who's about to rant
about how wonderful his gcc_3.3-compiled kernel is... pay attention to lkml
for the number of regressions still being found).

Most of the rest of the world started this process some time ago.

-- 
 Marc Wilson | Confound these ancestors They've stolen our
 [EMAIL PROTECTED] | best ideas!  - Ben Jonson


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



Re: How to change a symlink without breaking anything (problems with g++)

2003-07-02 Thread Morten Eriksen
Marc Wilson [EMAIL PROTECTED] writes:

 The C++ transition has endlessly been debated and beaten to death in
 a variety of public fora... if you don't know about it, you're
 living under a rock [...]

I have indeed lived under a rock, not participating nor reading any of
the Debian public fora up until now. Sorry for my ignorance on this
issue.

 and probably shouldn't be using anything other than stable.

You are probably right. I developed the bad habit of considering
testing as stable back at the later stages of when Woody was
testing, and stable was more like green with fungus.  ;-)

Anyway, thanks for informing me.

Thanks also to the other respondents, who pointed at dpkg-divert,
which was the kind of solution I was initially looking for. My problem
turned out in the end to be better solved by doing apt-get remove
g++ followed with apt-get install g++/stable, as indicated by
Marc..

~# Morten


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



Re: How to change a symlink without breaking anything (problems with g++)

2003-07-02 Thread Colin Watson
On Wed, Jul 02, 2003 at 02:24:30PM +0200, Morten Eriksen wrote:
 Marc Wilson [EMAIL PROTECTED] writes:
  The C++ transition has endlessly been debated and beaten to death in
  a variety of public fora... if you don't know about it, you're
  living under a rock [...]
 
 I have indeed lived under a rock, not participating nor reading any of
 the Debian public fora up until now. Sorry for my ignorance on this
 issue.

One public forum you might like to read is debian-devel-announce. It's
pretty low-traffic, and while its posts often expect a fair degree of
technical knowledge it's a very good way to keep up to date with what's
happening in testing and unstable.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


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



How to change a symlink without breaking anything (problems with g++)

2003-07-01 Thread Morten Eriksen
Hi,

this is probably a newbie question, but I didn't see it covered in any
of the FAQs or HOW-TOs I found at debian.org/docs/ (and the list
search facilities seems quite sloppy, and I had no luck there either):

What is the correct manner of changing a symlink file belonging to a
Debian package? Is it sufficient to just rm and re-link, or should I
use any of the package-handling tools?

(In case someone is interested, I'm asking because I just stumbled
over a surprising issue with the g++ packages: doing an

   # apt-get install g++

installed g++-3.3 (I was expecting just an upgrade to the previously
installed g++-2.95), and made /usr/bin/g++ into a symlink pointing to
it. Just switching g++ versions like this is bound to cause mayhem for
all development against any C++ libraries on the system already
compiled with g++ v2.95, so I'm surprised that this happens just like
that from the testing branch..? Removing the g++-3.3 package doesn't
work either, as apt-get seems to now refuse to remove or install
_either_ g++-2.95 or g++-3.3 -- it insists on having both? Weird.)

~# Morten


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



Re: HELP: Problems with G++ : Try ./hello and not hello

1998-08-29 Thread shaul
Try ./hello instead of hello (at the bash promt)

 I am having difficulties getting g++ to compile properly.
 
 I am just testing it with a simple hello program.

 When I type ...
 
 g++ -g -Wall -ohello hello.cc
 
 The file - hello - is created.  When I type, hello to execute the program.  
 The bash shell tells me there is no such command.
  
 What am I doing wrong?  I need to get this working for my class on Monday.
  
 Thanks,
 Denis



HELP: Problems with G++

1998-08-28 Thread DMDP




I am having difficulties getting g++ to compile 
properly.

I am just testing it with a simple 
hello program.

When I type ...

g++ -g -Wall -ohello hello.cc

The file - hello - is created. When I 
type, hello to execute the program. The bash shell tells me there is no 
such command.

What am I doing wrong? I need to get this 
working for my class on Monday.

Thanks,
Denis


Re: HELP: Problems with G++

1998-08-28 Thread Michael Beattie
On Thu, 27 Aug 1998, DMDP wrote:

 I am having difficulties getting g++ to compile properly.
 
 I am just testing it with a simple hello program.
 
 When I type ...
 
 g++ -g -Wall -ohello hello.cc
 
 The file - hello - is created.  When I type, hello to execute the program.  
 The bash shell tells me there is no such command.
 
 What am I doing wrong?  I need to get this working for my class on Monday.
 
 Thanks,
 Denis
 

try `./hello` - If you are working as root (everyone says that is a Bad
Thing (tm)), the current directory is not in the path. If you are working
as your normal user (Good Thing (tm)), then I would suggest you bash (no
pun intended) me in the head and say Get outta the way! I'll ask a real
guru.  
Another thing to check, make sure it has executable permissions.
(r-xr-xr-x) or the like.

Good Luck,
   Michael Beattie ([EMAIL PROTECTED])

   PGP Key available, reply with pgpkey as subject.
 -
If you don't know where you want to go, we'll make sure you get taken.
  -Japanese Microsoft ad slogan translated back into English
 -
Debian GNU/Linux  Ooohh You are missing out!



Re: Problems with g++

1997-06-10 Thread joost witteveen
 On Jun 9, Sebastien Phelep wrote
  gcc is 2.7.2.2-4; libg++ is 2.7.2.1-9 / 2.7.2.5-1
  
  I guess it's because I've used unstable packages, but I'm note sure.
  Does anybody knows what's the problem is ?
 
 Debian's gcc 2.7.2.2 packages by default use with libc6; for libc6 you need
 the libg++272 package.

2.7.2.5-1 is the libg++272 (libc6) package. but 2.7.2.1-9 is the libc5
version. So, my guess is that Sebastien has --force-depends installed
the libc5 devel package on a libc6 system.

$ dpkg -l 'libg++*'|grep '^i'
ii  libg++272.7.2.1-9  The GNU C++ libraries (ELF version).
ii  libg++272   2.7.2.5-1  The GNU C++ libraries (ELF version).
ii  libg++272-dbg   2.7.2.5-1  The GNU C++ libraries (ELF version).
ii  libg++272-dev   2.7.2.5-1  The GNU C++ libraries (ELF version).

If you get that output, the compiling g++ stuff should be OK.
(at least it's on my system).

 As not all libraries are ready/available for libc6, it is probably best to
 downgrade your gcc (using dpkg) to the 2.7.2.1 version, and put it (and
 cpp) on Hold in dselect.

May work, but the g++ stuff works fine here (and I've got positive
reports from others too).


-- 
joost witteveen, [EMAIL PROTECTED]
#!/usr/bin/perl -sp0777iX+d*lMLa^*lN%0]dsXx++lMlN/dsM0j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$kSK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
#what's this? see http://www.dcs.ex.ac.uk/~aba/rsa/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .


Problems with g++

1997-06-09 Thread Sebastien Phelep
 Hello.
 
I'm having problems with g++: when I launch a program I've compiled with
it, I have a segmentation fault; I first thought that it was my program
that was bad, but even if I make a *very* simple program (a Point class,
with a main that just adds a new point and deletes it immediately after),
I get a SEGV signal.
I've tried to find what was wrong with gdb; it says that it comes from
getenv()... even if I don't use getenv !

gcc is 2.7.2.2-4; libg++ is 2.7.2.1-9 / 2.7.2.5-1

I guess it's because I've used unstable packages, but I'm note sure.
Does anybody knows what's the problem is ?

Thanks,
Seb.


PS: Oh yes, it compiles without any warnings...
---
Sébastien Phélep -  Etudiant en deuxième année d'informatique, IUT de Vannes.
[EMAIL PROTECTED] --- [EMAIL PROTECTED] --- [EMAIL PROTECTED]




--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] .
Trouble?  e-mail to [EMAIL PROTECTED] .


Re: Problems with g++

1997-06-09 Thread J.H.M.Dassen
On Jun 9, Sebastien Phelep wrote
 gcc is 2.7.2.2-4; libg++ is 2.7.2.1-9 / 2.7.2.5-1
 
 I guess it's because I've used unstable packages, but I'm note sure.
 Does anybody knows what's the problem is ?

Debian's gcc 2.7.2.2 packages by default use with libc6; for libc6 you need
the libg++272 package.

As not all libraries are ready/available for libc6, it is probably best to
downgrade your gcc (using dpkg) to the 2.7.2.1 version, and put it (and
cpp) on Hold in dselect.

HTH,
Ray
-- 
LEADERSHIP  A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch 
it'll be someone else's bones which go crack and not their own.   
- The Hipcrime Vocab by Chad C. Mulligan


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to
[EMAIL PROTECTED] . 
Trouble?  e-mail to [EMAIL PROTECTED] .