directory names in linker

directory names in linker

[Ruslan Shevchenko]

After installing egcs-2.91.14 and compiling programs with
-belph, I receive error:
crtbegin.o: can not open file for reading

warning: /usr/local/lib/gcc-lib/elph/egcs-2.91.14/ not used
(or some in this style, I don't remember)

after
ln -s /usr/local/lib/gcc-lib/i586-pc-sco3.2v5.0.4/egcs-2.91.14
     /usr/local/lib/gcc-lib/elf/egcs-2.91.14

all work.


--

    @=
     //RSSH                              mailto:Ruslan@Shevchenko.Kiev.UA

Re: directory names in linker

[Jim Wilson]

	After installing egcs-2.91.14 and compiling programs with
	-belph, I receive error:
	crtbegin.o: can not open file for reading

-b is a gcc option that does not do what you think it does.  See the gcc
documentation.

Try using -melf/-mcoff instead.  I believe -melf is the default, so you
shouldn't need to specify it.

Jim

Re: directory names in linker

[Ruslan Shevchenko]

Jim Wilson wrote:

>         After installing egcs-2.91.14 and compiling programs with
>         -belph, I receive error:
>         crtbegin.o: can not open file for reading
>
> -b is a gcc option that does not do what you think it does.  See the gcc
> documentation.
>
> Try using -melf/-mcoff instead.  I believe -melf is the default, so you
> shouldn't need to specify it.
>

I think egcs must have backward compability with gcc.for example, -b,elph
is from Makefile for sun Tcl-8.0

Of course, we can say, that it is bug in sun configure,
but if they checked it with gcc, why it is not must work
with egcs ?


> Jim



--

    @=
     //RSSH                              mailto:Ruslan@Shevchenko.Kiev.UA

Re: directory names in linker

[Jim Wilson]

I don't know what you are talking about, but -belf has never done what you
think it does, and this has nothing to do with EGCS vs gcc.  Please see
the gcc documentation.

-melf is the correct option for both EGCS and gcc.

It would be possible to build a copy of gcc where -belf did something useful,
but that would require doing a lot of stuff by hand.  Perhaps someone once
distributed a binary package for gcc that was hand constructed in such a way
that -belf worked.  However, you can't expect -belf to work for a compiler that
you build yourself unless do the same hackery.  Since you have not done so,
in your build, the -belf option won't work for you.

Or perhaps you are confusing SCO C compiler options with gcc options.  Maybe
-belf if the correct SCO C compiler option?

Jim

-belf Re: directory names in linker

[Robert Lipe]

> I don't know what you are talking about, but -belf has never done what you
> think it does, and this has nothing to do with EGCS vs gcc.  Please see
> the gcc documentation.

I was mystified, too.   I was going to pipe up, but since he didn't bother
to name the host or target, I didn't bother to comment.

> It would be possible to build a copy of gcc where -belf did something useful,
> but that would require doing a lot of stuff by hand.  Perhaps someone once
> distributed a binary package for gcc that was hand constructed in such a way
> that -belf worked.  However, you can't expect -belf to work for a compiler that

For SCO OpenServer, some dude did indeed distribute a wildly popular (a couple
of tens of thousands distributed via download and CD) version of gcc that did
support '-belf', just like the OpenServer native compiler did.

I can't remember who that dude was, but I have it on Good Authority that
it was actually based on a Cygnus progressive tree becuase that's what
the dude happened to have. :-)

In fact, for this target, it's even explictly mentioned in the EGCS doc:
	http://egcs-www.cygnus.com/install/specific.html
with some additional info in the SCO prgrammer FAQ at
	http://www.dgii.com/cgi-bin/scoprgfaq/faq.pl

RJL