[Top][All Lists]

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

[Chicken-janitors] [Chicken-bugs] #394: C compiler invocation options sh

From: Chicken Scheme
Subject: [Chicken-janitors] [Chicken-bugs] #394: C compiler invocation options should take precedence
Date: Thu, 20 Dec 2007 19:05:15 -0000

#394: C compiler invocation options should take precedence
 Reporter:  kon       |       Owner:     
     Type:  defect    |      Status:  new
 Priority:  minor     |   Milestone:     
Component:  compiler  |     Version:  2.7
 Keywords:            |  
 Ran into a minor issue w/ the current version. Because of the
 ordering of the link cmd options the checkout (runtests) of the build
 failed w/ a

 gcc a.o -o a.out -L/usr/local/lib -L.. -lm -lchicken
 /usr/bin/ld: Undefined symbols:
 collect2: ld returned 1 exit status

 Since the INSTALL_LIB_DIR comes before the invocation command-line
 options the chicken lib in /usr/local/lib was found & used for
 resolution, rather than the new lib in the build dir.

 Urgh - yes.

 There might be a problem here for general use. I wonder if
 recognizable invocation bag-type options, such as -L & -I, should
 order before the built-ins? Would a programmer expect an explicit "-
 L.." in the compiler invocation to take precedence?

 I think it would. Needs some mucking with csc's handling of options
 (which isn't particularly nice to begin with). Can you write a ticket?
 I'll look into this.

Ticket URL: <>
Chicken Scheme <>
The CHICKEN Scheme-to-C compiler

reply via email to

[Prev in Thread] Current Thread [Next in Thread]