[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: build fails on hppa (gcc 3.X problem?)

W liście z pon, 25-03-2002, godz. 17:31, Philip Blundell pisze: 
> You need to find out where that "-Wl,-b" is coming from.  It needs to
> either be followed by a valid BFD name, or omitted altogether.
Questions are steps of thinking...

Q1: WTF is BDF (lirycs?) ?

I configured gcc/g++ 3.0 on my machine, exported CC and CXX variables
to point them, recompiled the package and:
- it compiled w/o errors
- there were NO "-Wl,-b" string anywhere.
- above, at the end of another string it is appended "-Wl,-E" but
it passes this stage, of course at my i386 w/ gcc/g++ 3.0 it
didn't appeared ;-?

Q2: How then is hppa differently configured if adds such strings
"just like that" ? 

Q3: I'd want to look at the Makefile on hppa after I ./configure 
(and environment variables too), but I am not DD (yet) and I don't
have access to any other machine than my old AMD300.
- is there any possibility to an account on any hppa machine w/ debian?
- could anyone apt-get source xnc on hppa box and send me Makefile
after ./configure ?

Q4: After looking at my (i386) Makefile I think that one of those
variables is responsible, I see there:
and the line that does "gcc -o nc...." is:
nc: $(OBJS) $(ROBJS) $(JDEP)
        $(CXX) -o $@ $(OBJS) $(ROBJS) $(LOCAL_LIBRARIES) $(JLIB)
But it _works_ (strange ;-)

in ./plugins/five/makefile I see:
        $(CXX) -o $@ $(IOBJS) -shared $(SHAREFLAGS) $(DEB) $(STRIPPING)

where PROGRAM=libxncfive.so
SHAREFLAGS= -fpic (it's the same as on hppa - I think)
DEB= (is empty, so it seems to be on hppa - notoice many spaces in log!)
STRIPPING= (is empty and is THE MAIN SUSPECT here)

Q4: Why is this STRIPPING set else on hppa than on my i386 box ?
-Wl seems to have sth to do with warning's handling, but -b... :

-b machine
  The argument machine specifies the target machine for compilation. 
This is useful when you have installed GCC as a cross-compiler.
The value to use for machine is the same as was specified as the machine
type when configuring GCC as a cross-compiler.  For example, if a
cross-compiler was configured with configure i386v, meaning to compile
for an 80386 running SystemV, then you would specify -b i386v to run
that cross compiler.When you do not specify -b, it normally means to
compile for the same type of machine that you are using.

I didn't mean to crosscompile. Or maybe Debian desn't have hppa box
and it does cross-compilation and it causes the problem here ????????


Anyone enlighten me what's going on here please

					Grzegorz Prokopski

To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to: