Could you please ensure that the kernel versions are compatible?
From the error messages it seems to be a compilation targeted for 64-bit system whereas you new host is 32-bit installation.
Also do a touch recursively to all the files to update the timestamp of all the files in your sandbox to ensure that make utility finds everything on your new host for compilation; the error-2 unimplemented: 64-bit mode not compiled in ... and the initial ones make: *** No targets. Stop.
.. of the error which went off automatically for you and you could atleast run the compilation (posted in your last one ...) gives me an impression of the mismatch time/date set in both of your machine there by Make not finding objects to compile.
Run (from the top directory of your sandbox):
Code:
find . -type f -exec touch {} \;
Further ensure that target is set for 32 bit compilation and kernel version mismatch is properly appended in your code.
If possible post your code here in the forum as a tar/zip attachment.
This User Gave Thanks to Praveen_218 For This Post:
Hi I have installed Suse Linux 9.3 desktop on my computer. I found out I need to install 'gcc', and I was able to download the source code. I then tried to follow some instructions from WEB search to compile and build gcc, and I am getting the following error:
---
linux:/gcc/gcc-2.95.3 #... (1 Reply)
dears i working in solaris and when i type make for report it gives me the error kindly can you help me what is the reason
-bash-3.00$ make BPSEXT130
make: Warning: File `BPSEXT130.rc' has modification time 12 s in the future
make BPSEXT130.c
make: Entering directory... (3 Replies)
Hi All,
While installing a Service Pack on my Unix Solaris machine, i got the following error:
UX:acomp: ERROR: "space.c", line 16: undefined symbol: CHROOT_SECURITY
UX:acomp: ERROR: "space.c", line 16: non-constant initializer: op "NAME"
UX:idmkunix: ERROR: Compile/link of 'Driver_atup.o... (9 Replies)
Hi All,
Currently my project source code is compatible with HP-UX11.0 and Sun Solaris5.8. I m trying to build the source code in AIX 5.2 using gcc 4.2.2 compiler.
Can anyone suggest me after seeing the rules file, what options do i need to specify to get rid of the cb error
I m... (0 Replies)
Hi,
I am starting to learn how to use KDevelop. I have a console program with .cc, .h and Makefile. To work it in KDevelop, I firstly create a C++ Simple Hello World program, remove the single existing target in the project
and also the auto-created main.cpp. Then I copy my .cc and .h files into... (1 Reply)
I'm getting the following Error:
prepare_pcap.c: In function `prepare_pkts':
prepare_pcap.c:127: error: dereferencing pointer to incomplete type
prepare_pcap.c:138: error: dereferencing pointer to incomplete type
====================================
This is the part of the relevant... (8 Replies)
I installed java at usr/local/jdk directory. My Java Version is 1.6.0_05. I have installed apache ant version 1.8.1 in folder opt/ant successfully. And later on I have installed RED 5.0.9 final version at /opt/ant directory.
But I am getting error while building ant at RED5 , I got following... (1 Reply)
Today I tried to generate ndis Solaris driver.
Problem is when I try to compile ndiswapper following instructions on opensolaris site.
ndis wrapper (Community Group laptop.ndis) - XWiki
My version of Solaris
$ uname -a
SunOS pc001 5.10 Generic_142910-17 i86pc i386 i86pc
... (0 Replies)
Hi,
So I downloaded this kernel source and was able to build it successfully.
But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself.
I added the SDK in the main Makefile:
init-y := init/
#added SDK... (0 Replies)
Hi
I have a build.xml file and I can run it on Windows via cmd. Now I want to write a script to invoke the same. Is there a way to do this? (1 Reply)
Discussion started by: ankur328
1 Replies
LEARN ABOUT REDHAT
lfcompile64
lfcompile64(5) Standards, Environments, and Macros lfcompile64(5)NAME
lfcompile64 - transitional compilation environment
DESCRIPTION
All 64-bit applications can manipulate large files by default. The transitional interfaces described on this page can be used by 32-bit and
64-bit applications to manipulate large files.
In the transitional compilation environment, explicit 64-bit functions, structures, and types are added to the API. Compiling in this
environment allows both 32-bit and 64-bit applications to access files whose size is greater than or equal to 2 Gbyte ( 2**31 bytes).
The transitional compilation environment exports all the explicit 64-bit functions (xxx64()) and types in addition to all the regular func-
tions (xxx()) and types. Both xxx() and xxx64() functions are available to the program source. A 32-bit application must use the xxx64()
functions in order to access large files. See the lf64(5) manual page for a complete listing of the 64-bit transitional interfaces.
The transitional compilation environment differs from the large file compilation environment, wherein the underlying interfaces are bound
to 64-bit functions, structures, and types. An application compiled in the large file compilation environment is able to use the xxx()
source interfaces to access both large and small files, rather than having to explicitly utilize the transitional xxx64() interface calls
to access large files. See the lfcompile(5) manual page for more information regarding the large file compilation environment.
Applications may combine objects produced in the large file compilation environment with objects produced in the transitional compilation
environment, but must be careful with respect to interoperability between those objects. Applications should not declare global variables
of types whose sizes change between compilation environments.
For applications that do not wish to conform to the POSIX or X/Open specifications, the 64-bit transitional interfaces are available by
default. No compile-time flags need to be set.
Access to Additional Large File Interfaces
Applications that wish to access the transitional interfaces as well as the POSIX or X/Open specification-conforming interfaces should use
the following compilation methods and set whichever feature test macros are appropriate to obtain the desired environment (see stan-
dards(5)).
o Set the compile-time flag _LARGEFILE64_SOURCE to 1 before including any headers.
o Use the getconf(1) command with one or more of the following arguments:
+------------------+----------------------------------------+
| argument | purpose |
|LFS64_CFLAGS | obtain compilation flags necessary to |
| | enable the transitional compilation |
| | environment |
|LFS64_LDFLAGS | obtain link editor options |
|LFS64_LIBS | obtain link library names |
|LFS64_LINTFLAGS | obtain lint options |
+------------------+----------------------------------------+
EXAMPLES
In the following examples, the transitional compilation environment is accessed by invoking the getconf utility with one of the arguments
listed in the table above. The additional large file interfaces are accessed either by specifying -D_LARGEFILE64_SOURCE or by invoking the
getconf utility with the arguments listed above.
The example that uses the form of command substitution specifying the command within parentheses preceded by a dollar sign can be executed
only in a POSIX-conforming shell such as the Korn Shell (see ksh(1)). In a shell that is not POSIX-conforming, such as the Bourne Shell
(see sh(1)) and the C Shell (see csh(1)), the command must be enclosed within grave accent marks.
Example 1: An example of compiling a program using transitional interfaces such as lseek64() and fopen64():
$ c89 -D_LARGEFILE64_SOURCE
$(getconf LFS64_CFLAGS) a.c
$(getconf LFS64_LDFLAGS)
$(getconf LFS64_LIBS)
Example 2: An example of running lint on a program using transitional interfaces:
% lint -D_LARGEFILE64_SOURCE
`getconf LFS64_LINTFLAGS` ...
`getconf LFS64_LIBS`
SEE ALSO getconf(1), lseek(2), fopen(3C), lf64(5), standards(5)SunOS 5.10 26 Jan 1998 lfcompile64(5)