Hi,
As suggested I installed altgcc package and still could not compile the
program. The compiler complains about the undefined size of a variable.
I traced this to struct fd_set. The following code compiles on a bo box,
but not on a hamm box.
#include
#include
int main(void)
{
struct fd_set
On Tue, Nov 24, 1998 at 15:23:27 +0530, XRDLAB wrote:
> I wanted to compile a program on my hamm machine and ran into some problems.
> I found that the reason for the errors were due to libc5 dependency of the
> program. I installed libc5-altdev package and tried to compile the program
> with the
Hi,
I wanted to compile a program on my hamm machine and ran into some problems.
I found that the reason for the errors were due to libc5 dependency of the
program. I installed libc5-altdev package and tried to compile the program
with the following command line:
gcc -nostdinc -I/usr/i486-lin
> "Linux-Debian" == Linux-Debian Team <[EMAIL PROTECTED]> writes:
Linux-Debian> I have upgraded my system to libc6 with not much
Linux-Debian> troubles. Now, it seems that some programs have to
Linux-Debian> be compiled under libc5 anyway. Therefore altgcc and
Linux-Debian> al
I have upgraded my system to libc6 with not much troubles.
Now, it seems that some programs have to be compiled under
libc5 anyway. Therefore altgcc and altdev-libc5 have been
loaded into the system.
Now i need some documentation about how to instruct 'make'
to use the alternative environment.
Is
> |"Well, in my case I have one more line:
> |"
> |"libc.so.5 => /lib/libc.so.5
> |"
> |"and don't have libXext one. What Motif distribution are you using?
>
> This is the Red-Hat Motif 2.0 distribution.
That is so strange! I have Metrolink Motif 2.0.1 - _the_same_ RedHat is
using. What makes dif
|"Well, in my case I have one more line:
|"
|"libc.so.5 => /lib/libc.so.5
|"
|"and don't have libXext one. What Motif distribution are you using?
This is the Red-Hat Motif 2.0 distribution.
--
>>> Ronald van Loon ([EMAIL PROTECTED])
>>> <<<
I hold your hand
> |"> Debian happily uses some derivatives of commercial developmental suits.
> |"> The most obvious example would be -dmotif and -smotif packages in contrib.
> |"
> |"OK, point taken, -smotif libg++ packagres won't be possible without
> |"a libg++27-altdev. (Do I care? no, but others may, I agree)
|"> Debian happily uses some derivatives of commercial developmental suits.
|"> The most obvious example would be -dmotif and -smotif packages in contrib.
|"
|"OK, point taken, -smotif libg++ packagres won't be possible without
|"a libg++27-altdev. (Do I care? no, but others may, I agree).
I don't
>
> What you should do:
> install libc5-altdev and altgcc. libc5-altdev does _not_ conflict with
> libc6. Then you'll need to do something with
> your PATH so that the altgcc will be used by default instead of the
> libc6 gcc. (Probably read /usr/doc/altgcc/* to find out what).
> One pr
> > The only frequently
> > required library for X development wich is _not_ part of standard X
> > distribution left is xpm. Therefore I was wondering about availability
> > of xpm4.7-altdev.
> xmp may well posess the same features as xlib does, i.e. maybe we
> don't need an xmp-altdev.
uh, oh.
>
> > Debian happily uses some derivatives of commercial developmental suits.
> > The most obvious example would be -dmotif and -smotif packages in contrib.
>
> OK, point taken, -smotif libg++ packagres won't be possible without
> a libg++27-altdev. (Do I care? no, but others may, I agree).
-dmo
> > > If there is enough demand for a libg++272-altdev package, I'll release
> > > one,
> > > though.
> >
> > Joost,
> >
> > are you kidding?
>
> No, I'm dead serious. I now vow to never release a libg++272-altdev[1].
>
> > You probably don't understand that ALL commercial
> > develpmental su
> I thought I was polite, but I try to be even nicer ;)
Are you kidding me :)?
> Debian happily uses some derivatives of commercial developmental suits.
> The most obvious example would be -dmotif and -smotif packages in contrib.
OK, point taken, -smotif libg++ packagres won't be possible witho
> > >
> > > I know we've gone to libc6, but I'm not quite clear on how to compile
> > > with libc5 instead. I know I need libc5-altdev. Do I need to remove
> > > libc6-dev, which also requires removal of libg++272-dev? And do I need
> > > to install anything else?
> >
> > What you should do:
> >
> > I know we've gone to libc6, but I'm not quite clear on how to compile
> > with libc5 instead. I know I need libc5-altdev. Do I need to remove
> > libc6-dev, which also requires removal of libg++272-dev? And do I need
> > to install anything else?
>
> What you should do:
> install li
>
> I know we've gone to libc6, but I'm not quite clear on how to compile
> with libc5 instead. I know I need libc5-altdev. Do I need to remove
> libc6-dev, which also requires removal of libg++272-dev? And do I need
> to install anything else?
What you should do:
install libc5-altdev and a
Hi Rick -
I am *not* an expert on this, but I've asked about this stuff a little
before. :-)
The altdev packages are intended to coexist with libc6-dev, in the way
the regular libc5-dev packages cannot. So do keep that libc6-dev.
'Altgcc' is the compiler package intended to compile with libc5
I know we've gone to libc6, but I'm not quite clear on how to compile
with libc5 instead. I know I need libc5-altdev. Do I need to remove
libc6-dev, which also requires removal of libg++272-dev? And do I need
to install anything else?
I'm getting some strange errors compiling development versi
19 matches
Mail list logo
