Okay, so what actually is your problem? What you have described is a bit like ringing your local mechanic to say "There's something wrong with my car" and they have to guess is it out of fuel, headlights, engine won't start (lots of causes there) or you have forgotten your keys and tried someone else's keys from a similar car instead, or a multitude of other things down to "I can't find my way home"
Sharing your code would probably help along with the commands you are using and the output/errors. Please wrap the various parts in CODE tags to make there clear to read and preserve multiple spacing for indenting or fixed-width data.
We're all here to learn and getting the relevant information will help us all.
- which package do you try to compile?
- which compiler do you use?
- what EXACTLY are the diagnostic messages (sorry, but to find the culprit from "sometimes something doesn't work" is nigh impossible)?
Quote:
When we try to copy file "/usr/bin/sh" from AIX6.1 to replace it on AIX7.2, we can compile sucessfully.
IMHO it is a miracle that this would run at all because of different shared library versions involved. In any case /usr/bin/sh in AIX since (IIRC) v 4.1 has always been a Korn shell 88 and the ksh version hasn't changed since 5.3 at all. So, apart from version problems with shared libraries as described above, you should get the same results with both shell versions when running scripts.
I hope this helps.
bakunin
These 2 Users Gave Thanks to bakunin For This Post:
Sorry for making you confused. What I mean is: Is there any differences, big -diferences between AIX 7.2 and the others AIX version ( the shell environtment, the policy ... ) which can make these things happen.
I'm not sure what's the culprit - the AIX 7.2, the compiler program or the script compatibility or something else. So I wrote " I have no idea why".
Attack file - including : script, command to run script and logs. Hope you can find something.
OK, thanks for the follow-up. Not everything makes sense yet but we are making progress.
Quote:
Originally Posted by bobochacha29
Is there any differences, big -diferences between AIX 7.2 and the others AIX version ( the shell environtment, the policy ... ) which can make these things happen.
Not to my knowledge. But let us state for the record what we have so far:
You try to run a configure script for a nondescript software using IBMs XlC compiler and you encounter a syntax error:
Code:
[...snipped...]
appending configuration tag "F77" to libtool
./configure[24690]: if: not found
./configure[24690]: then: not found
./configure[24692]: else: not found
./configure[24694]: fi: not found
./configure[24700]: if: not found
./configure[24700]: then: not found
./configure[24702]: else: not found
./configure[24704]: fi: not found
./configure[24707]: if: not found
./configure[24707]: then: not found
./configure[24714]: else: not found
./configure[24720]: fi: not found
./configure[24722]: case: not found
./configure[24723]: syntax error at line 24723 : `)' unexpected
./configure[24723]: syntax error at line 19 : `)' unexpected
These configure-scripts are created automatically so a syntax error just because someone made a typo or so is quite unlikely.
Now my first question is if there might be something wrong with your environment: check /etc/environment of the system you compile at for anything unusual because the settings there are put into every processes environment. Next, remove any configuration files (~/.profile, ~/.kshrc, ~/.bashrc, ...., just rename them) and start a "blank" session with a minimal environment. Check this for any unusual stuff (i.e. weird aliases, redefined system commands and the like), set the minimum PATH necessary for compilation and try to run the configure script again.
Did you use the same configure-script in both the failed and the successful case or did you unpack the source into different directories? If the latter is the case: did all involved file systems have enough space or might some file have become truncated during the unpacking?
So far, these are my first ideas. I hope this helps.
Did you use the same configure-script in both the failed and the successful case or did you unpack the source into different directories
bakunin
Yes, same configure-script and same directories.
Thanks for your help.We even created a new server one, installed AIX from the beginning, installed the compiler, copied source, unpacked and then run the script. First, everything seemed good. We run the script several times successfully. Then suddenly, it failed.
This is the first time we run this on AIX 7.2, so maybe the problem here is the compatibility. We are still checking now.
First, everything seemed good. We run the script several times successfully. Then suddenly, it failed.
OK, here is another idea: these configure-scripts write their results to a file which is reused in consecutive runs. This means that these consecutive runs of the configure-script are not exactly the same as the first one. Question: does this problem also happen if you delete this file before a new run?
If it doesn't the reason might be (one probable reason) some fancy UMASK setting which makes the results files noticeable but not accessible.
Hi everyone:
I have a server running AIX 6.1, I've upgraded the TL from 6100-0100 to 6100-04-02-1007, however since then all the executables I compile are 32-bit mode by default, how can I solve this?
I'm using VisualAge C/C++ 10.0
thanks in advance (4 Replies)
Hello, I asked this question in the AIX subforum but never received an answer, probably because the AIX forum is not that heavily trafficked. Anyway, here it is..
I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs... (9 Replies)
Hello all. I have never had any issues like this when compiling applications from source. When I try to compile samba-3.5.0pre2, configure runs with no issues, but when the time comes to make, this happens:
make: make 1254-025 There must be an existing description file or specify a target.
... (4 Replies)
Hi, i'm trying to work with a trial version of PurifyPlus 7 with fixpack 10 from Rational that needs to run over an AIX 5.3 platform, 64-bit. I had success on compiling and running the hello_world programs and even a hash test program i found over the net, but purify can achieve the same with the... (0 Replies)
Hi
When im trying to do make --version and make --help in HP-UX
it throws error
Make: Unknown flag argument -. Stop.
a soft link is present in this directory /usr/bin/make
and hard link is in /usr/ccs/bin/make
what could be the reason can any1 ..please tell me how to solve this... (1 Reply)
Compiling samba 3.0.27a under AIX
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure... (2 Replies)
I try to compile Samba 3.0.27a under AIX with LDAP and KErberos.
The configure work fine:
CFLAGS:
-I/opt/pware/include -I/opt/pware/lib/ -I/opt/pware/open_ldap_exec/lib/ -I/software/samba/oldap/usr/lib -I/software/samba/oldap/usr/include
./configure --prefix=/opt/pware/samba/3.0.27a... (1 Reply)
Hi, I'm trying to compile a Perl module for AIX 5.3. Now, Perl by default wants to use cc_r as compiler but I only have gcc installed on this system.
How can I get gcc to be thread safe? Or can I use gcc without any options and expect it to behave the same as cc_r? (0 Replies)
Hello,
i will compile php and apache on an aix 5.1. Configure works fine.
When i start the make the following error appears:
/usr/include/sys/context.h:155: parse error before "sigset64_t"
/usr/include/sys/context.h:158: parse error before '}' token
make: 1254-004 The error code from the... (1 Reply)