Gentoo Archives: gentoo-user

From: saf@archivum.info (saf)
To: gentoo-user@l.g.o
Subject: [gentoo-user] emerge mc: undefined reference to `write_socket'
Date: Sun, 22 Jan 2006 17:15:32
Message-Id: 20060122171113.GA6677@archivum.info
1 Hi all,
2
3 thanks for your support on this mailing list.
4 Gentoo is a very great Linux distribution.
5
6 I have a question about Midnight Commander:
7 I can't emerge mc because of a compiler error.
8 Does somebody knows how to fix it?
9 I tried already to remove samba in the USE flags, but it changes nothing.
10
11 When I try to emerge mc, I get this error:
12
13 i686-pc-linux-gnu-gcc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -mar
14 ch=athlon-xp -O9 -pipe -mfpmath=sse,387 -mmmx -msse -fomit-frame-pointer -funrol
15 l-loops -m3dnow -I/usr/include/gssapi -Wall -o man2hlp man2hlp.o -lglib-2.0
16
17 ../vfs/libvfs-mc.a(smbfs.o): In function `chkpath':
18 smbfs.c:(.text+0x5867): undefined reference to `write_socket'
19 collect2: ld returned 1 exit status
20 make[2]: *** [mc] Error 1
21 make[2]: *** Waiting for unfinished jobs....
22 make[2]: Leaving directory `/var/tmp/portage/mc-4.6.0-r14/work/mc-4.6.0/src'
23 make[1]: *** [all-recursive] Error 1
24 make[1]: Leaving directory `/var/tmp/portage/mc-4.6.0-r14/work/mc-4.6.0'
25 make: *** [all] Error 2
26
27 My make.conf file:
28 # Copyright 1999-2004 Gentoo Foundation
29 # Distributed under the terms of the GNU General Public License v2
30 # $Header: /var/cvsroot/gentoo-src/portage/cnf/make.conf.x86,v 1.5 2004/10/10 23:27:28 carpaski Exp $
31 # Contains local system settings for Portage system
32
33 # Please review 'man make.conf' for more information.
34
35 # Build-time functionality
36 # ========================
37 #
38 # The USE variable is used to enable optional build-time functionality. For
39 # example, quite a few packages have optional X, gtk or GNOME functionality
40 # that can only be enabled or disabled at compile-time. Gentoo Linux has a
41 # very extensive set of USE variables described in our USE variable HOWTO at
42 # http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=1
43 #
44 # The available list of use flags with descriptions is in your portage tree.
45 # Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
46 #
47 # 'ufed' is an ncurses/dialog interface available in portage to make handling
48 # useflags for you. 'emerge app-portage/ufed'
49 #
50 # Example:
51
52 USE="kde gtk2 gnome java alsa 3dnow dvd cdr emacs usb tetex ipv6 truetype javascript dvdr X aalib aac acl acpi aim msn arts bash-completion bmp bzip2 crypt cups dga dri dvdread encode ethereal fortran ftp gb gif gmp gpm guile gnustep gphoto2 imlib javascript jpeg kdeenablefinal libwww lm_sensors mbox mime mmap mono mp3 mpeg msn mysql ncurses nls oci8 ogg opengl pdflib perl png posix python qt readline quicktime samba scanner sdl ssl slang soap speex spell sse svga nptl vcd videos truetype unicode usb v4l vorbis win32codecs wmf wxwindows xine xface xml2 xmms xpm yahoo zlib gcj objc"
53
54 # Host Setting
55 # ============
56 #
57 # Change this line as appropriate (i686, i586, i486 or i386).
58 # All modern systems (even Athlons) should use "i686-pc-linux-gnu".
59 # All K6's are i586.
60 CHOST="i686-pc-linux-gnu"
61
62 # Host and optimization settings
63 # ==============================
64 #
65 # For optimal performance, enable a CFLAGS setting appropriate for your CPU.
66 #
67 # Please note that if you experience strange issues with a package, it may be
68 # due to gcc's optimizations interacting in a strange way. Please test the
69 # package (and in some cases the libraries it uses) at default optimizations
70 # before reporting errors to developers.
71 #
72 # -mcpu=<cpu-type> means optimize code for the particular type of CPU without
73 # breaking compatibility with other CPUs.
74 #
75 # -march=<cpu-type> means to take full advantage of the ABI and instructions
76 # for the particular CPU; this will break compatibility with older CPUs (for
77 # example, -march=athlon-xp code will not run on a regular Athlon, and
78 # -march=i686 code will not run on a Pentium Classic.
79 #
80 # CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
81 # athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
82 # (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron),
83 # pentium3, and pentium4.
84 #
85 # Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
86 #
87 # CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
88 # (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
89 #
90 # CRITICAL WARNINGS: ****************************************************** #
91 # K6 markings are deceptive. Avoid setting -march for them. See Bug #24379. #
92 # Pentium-M CPU's should not enable sse2 until at least gcc-3.4. Bug 50616. #
93 # ************************************************************************* #
94 #
95 # General CFLAGS variable
96 #
97 CFLAGS="-march=athlon-xp -O9 -pipe -mfpmath=sse,387 -mmmx -msse -fomit-frame-pointer -funroll-loops -m3dnow"
98
99 # To compile valgrind:
100 # CFLAGS="-O2 -pipe"
101
102 #CFLAGS="-march=pentium3 -O3 -pipe"
103
104 # If you set a CFLAGS above, then this line will set your default C++ flags to
105 # the same settings.
106
107 CXXFLAGS="${CFLAGS}"
108
109 # Advanced Masking
110 # ================
111 #
112 # Gentoo is using a new masking system to allow for easier stability testing
113 # on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
114 # on the platform they are set for. A special form has been added that
115 # indicates packages and revisions that are expected to work, but have not yet
116 # been approved for the stable set. '~arch' is a superset of 'arch' which
117 # includes the unstable, in testing, packages. Users of the 'x86' architecture
118 # would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
119 # '~ppc', '~sparc' are the unstable KEYWORDS for their respective platforms.
120 #
121 # Please note that this is not for development, alpha, beta, nor cvs release
122 # packages. "Broken" packages will not be added to testing and should not be
123 # requested to be added. Alternative routes are available to developers
124 # for experimental packages, and it is at their discretion to use them.
125 #
126 # DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
127 # IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
128 #
129 ACCEPT_KEYWORDS="~x86"
130
131 # Portage Directories
132 # ===================
133 #
134 # Each of these settings controls an aspect of portage's storage and file
135 # system usage. If you change any of these, be sure it is available when
136 # you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
137 #
138 # PORTAGE_TMPDIR is the location portage will use for compilations and
139 # temporary storage of data. This can get VERY large depending upon
140 # the application being installed.
141 #PORTAGE_TMPDIR=/var/tmp
142 #
143 # PORTDIR is the location of the portage tree. This is the repository
144 # for all profile information as well as all ebuilds. This directory
145 # itself can reach 200M. WE DO NOT RECOMMEND that you change this.
146 #PORTDIR=/usr/portage
147 #
148 # DISTDIR is where all of the source code tarballs will be placed for
149 # emerges. The source code is maintained here unless you delete
150 # it. The entire repository of tarballs for gentoo is 9G. This is
151 # considerably more than any user will ever download. 2-3G is
152 # a large DISTDIR.
153 #DISTDIR=${PORTDIR}/distfiles
154 #
155 # PKGDIR is the location of binary packages that you can have created
156 # with '--buildpkg' or '-b' while emerging a package. This can get
157 # upto several hundred megs, or even a few gigs.
158 #PKGDIR=${PORTDIR}/packages
159 #
160 # PORT_LOGDIR is the location where portage will store all the logs it
161 # creates from each individual merge. They are stored as NNNN-$PF.log
162 # in the directory specified. This is disabled until you enable it by
163 # providing a directory. Permissions will be modified as needed IF the
164 # directory exists, otherwise logging will be disabled. NNNN is the
165 # increment at the time the log is created. Logs are thus sequential.
166 #PORT_LOGDIR=/var/log/portage
167 #
168 # PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
169 # concern that they will be deleted by rsync updates. Default is not
170 # defined.
171 PORTDIR_OVERLAY=/usr/local/portage
172
173 # Fetching files
174 # ==============
175 #
176 # If you need to set a proxy for wget or lukemftp, add the appropriate "export
177 # ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
178 # all users on your system should use them.
179 #
180 # Portage uses wget by default. Here are some settings for some alternate
181 # downloaders -- note that you need to merge these programs first before they
182 # will be available.
183 #
184 # Default fetch command (5 tries, passive ftp for firewall compatibility)
185 #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
186 #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
187 #
188 # Using wget, ratelimiting downloads
189 #FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
190 #RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
191 #
192 # Lukemftp (BSD ftp):
193 #FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
194 #RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
195 #
196 # Prozilla (turbo downloader)
197 #FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
198 #
199 # Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
200 # The list is a space separated list which is read left to right. If you use
201 # another mirror we highly recommend leaving the default mirror at the end of
202 # the list so that portage will fall back to it if the files cannot be found
203 # on your specified mirror. We _HIGHLY_ recommend that you change this setting
204 # to a nearby mirror by merging and using the 'mirrorselect' tool.
205 #GENTOO_MIRRORS="<your_mirror_here> http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
206
207
208 #GENTOO_MIRRORS="ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo"
209
210
211 #
212 # Portage uses PORTAGE_BINHOST to specify mirrors for prebuilt-binary packages.
213 # The list is a single entry specifying the full address of the directory
214 # serving the tbz2's for your system. Running emerge with either '--getbinpkg'
215 # or '--getbinpkgonly' will cause portage to retrieve the metadata from all
216 # packages in the directory specified, and use that data to determine what will
217 # be downloaded and merged. '-g' or '-gK' are the recommend parameters. Please
218 # consult the man pages and 'emerge --help' for more information. For FTP, the
219 # default connection is passive -- If you require an active connection, affix
220 # an asterisk (*) to the end of the host:port string before the path.
221 PORTAGE_BINHOST="http://grp.mirror.site/gentoo/grp/1.4/i686/athlon-xp/"
222 # This ftp connection is passive ftp.
223 #PORTAGE_BINHOST="ftp://login:pass@××××××××××.site/pub/grp/i686/athlon-xp/"
224 # This ftp connection is active ftp.
225 #PORTAGE_BINHOST="ftp://login:pass@××××××××××.site:21*/pub/grp/i686/athlon-xp/"
226
227 # Synchronizing Portage
228 # =====================
229 #
230 # Each of these settings affects how Gentoo synchronizes your Portage tree.
231 # Synchronization is handled by rsync and these settings allow some control
232 # over how it is done.
233 #
234 #
235 # SYNC is the server used by rsync to retrieve a localized rsync mirror
236 # rotation. This allows you to select servers that are geographically
237 # close to you, yet still distribute the load over a number of servers.
238 # Please do not single out specific rsync mirrors. Doing so places undue
239 # stress on particular mirrors. Instead you may use one of the following
240 # continent specific rotations:
241 #
242 # Default: "rsync://rsync.gentoo.org/gentoo-portage"
243 # North America: "rsync://rsync.namerica.gentoo.org/gentoo-portage"
244 # South America: "rsync://rsync.samerica.gentoo.org/gentoo-portage"
245 # Europe: "rsync://rsync.europe.gentoo.org/gentoo-portage"
246 # Asia: "rsync://rsync.asia.gentoo.org/gentoo-portage"
247 # Australia: "rsync://rsync.au.gentoo.org/gentoo-portage"
248 #SYNC="rsync://rsync.gentoo.org/gentoo-portage"
249 #
250 # RSYNC_RETRIES sets the number of times portage will attempt to retrieve
251 # a current portage tree before it exits with an error. This allows
252 # for a more successful retrieval without user intervention most times.
253 #RSYNC_RETRIES="3"
254 #
255 # RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
256 # on a connection. Most users will benefit from this setting as it will
257 # reduce the amount of 'dead air' they experience when they run across
258 # the occasional, unreachable mirror. Dialup users might want to set this
259 # value up around the 300 second mark.
260 #RSYNC_TIMEOUT=180
261
262 # Advanced Features
263 # =================
264 #
265 # MAKEOPTS provides extra options that may be passed to 'make' when a
266 # program is compiled. Presently the only use is for specifying
267 # the number of parallel makes (-j) to perform. The suggested number
268 # for parallel makes is CPUs+1.
269
270 MAKEOPTS="-j2"
271
272 #
273 # PORTAGE_NICENESS provides a default increment to emerge's niceness level.
274 # Note: This is an increment. Running emerge in a niced environment will
275 # reduce it further. Default is unset.
276 #PORTAGE_NICENESS=3
277 #
278 # AUTOCLEAN enables portage to automatically clean out older or overlapping
279 # packages from the system after every successful merge. This is the
280 # same as running 'emerge -c' after every merge. Set with: "yes" or "no".
281 # This does not affect the unpacked source. See 'noclean' below.
282 #AUTOCLEAN="yes"
283 #
284 # FEATURES are settings that affect the functionality of portage. Most of
285 # these settings are for developer use, but some are available to non-
286 # developers as well.
287 #
288 # 'autoaddcvs' causes portage to automatically try to add files to cvs
289 # that will have to be added later. Done at generation times
290 # and only has an effect when 'cvs' is also set.
291 # 'buildpkg' causes binary packages to be created of all packages that
292 # are being merged.
293 # 'ccache' enables ccache support via CC.
294 # 'collision-protect'
295 # prevents packages from overwriting files that are owned by
296 # another package or by no package at all.
297 # 'cvs' causes portage to enable all cvs features (commits, adds),
298 # and to apply all USE flags in SRC_URI for digests -- for
299 # developers only.
300 # 'digest' causes digests to be generated for all packages being merged.
301 # 'distcc' enables distcc support via CC.
302 # 'distlocks' enables distfiles locking using fcntl or hardlinks. This
303 # is enabled by default. Tools exist to help clean the locks
304 # after crashes: /usr/lib/portage/bin/clean_locks.
305 # 'fixpackages' allows portage to fix binary packages that are stored in
306 # PKGDIR. This can consume a lot of time. 'fixpackages' is
307 # also a script that can be run at any given time to force
308 # the same actions.
309 # 'gpg' enables basic verification of Manifest files using gpg.
310 # This features is UNDER DEVELOPMENT and reacts to features
311 # of strict and severe. Heavy use of gpg sigs is coming.
312 # 'keeptemp' prevents the clean phase from deleting the temp files ($T)
313 # from a merge.
314 # 'keepwork' prevents the clean phase from deleting the WORKDIR.
315 # 'maketest' causes ebuilds to perform testing phases if they are capable
316 # of it. Some packages support this automaticaly via makefiles.
317 # 'noauto' causes ebuild to perform only the action requested and
318 # not any other required actions like clean or unpack -- for
319 # debugging purposes only.
320 # 'noclean' prevents portage from removing the source and temporary files
321 # after a merge -- for debugging purposes only.
322 # 'nostrip' prevents the stripping of binaries.
323 # 'notitles' disables xterm titlebar updates (which contain status info).
324 # 'sandbox' enables sandboxing when running emerge and ebuild.
325 # 'strict' causes portage to react strongly to conditions that are
326 # potentially dangerous, like missing/incorrect Manifest files.
327 # 'userpriv' allows portage to drop root privileges while it is compiling,
328 # as a security measure. As a side effect this can remove
329 # sandbox access violations for users.
330 # 'usersandbox' enables sandboxing while portage is running under userpriv.
331 #FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
332 #FEATURES="buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork autoaddcvs"
333 #FEATURES="sandbox ccache distcc distlocks autoaddcvs"
334
335 FEATURES="ccache"
336
337 #
338 # CCACHE_SIZE sets the space use limitations for ccache. The default size is
339 # 2G, and will be set if not defined otherwise and ccache is in features.
340 # Portage will set the default ccache dir if it is not present in the
341 # user's environment, for userpriv it sets: ${PORTAGE_TMPDIR}/ccache
342 # (/var/tmp/ccache), and for regular use the default is /root/.ccache.
343 # Sizes are specified with 'G' 'M' or 'K'.
344 # '2G' for 2 gigabytes, '2048M' for 2048 megabytes (same as 2G).
345 CCACHE_SIZE="10G"
346 #
347 # DISTCC_DIR sets the temporary space used by distcc.
348 #DISTCC_DIR="${PORTAGE_TMPDIR}/.distcc"
349 #
350 # RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
351 # the portage tree. Specific chunks of the tree may be excluded from
352 # consideration. This may cause dependency failures if you are not careful.
353 # The file format is one pattern per line, blanks and ';' or '#' lines are
354 # comments. See 'man rsync' for more details on the exclude-from format.
355 #RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes
356 #GENTOO_MIRRORS="ftp://ftp.uni-erlangen.de/pub/mirrors/gentoo ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://chod.cwru.edu/gentoo ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ http://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp;//mirror.switch.ch/mirror/gentoo/"
357
358 GENTOO_MIRRORS="ftp://ftp6.uni-erlangen.de/pub/mirrors/gentoo http://ftp6.uni-erlangen.de/pub/mirrors/gentoo ftp://vlaai.snt.ipv6.utwente.nl/pub/os/linux/gentoo/ ftp://mirror.switch.ch/mirror/gentoo/"
359
360 #GENTOO_MIRRORS="ftp://ftp.uoi.gr/mirror/OS/gentoo/ http://adelie.polymtl.ca/ http://130.59.10.34/ftp/mirror/gentoo/"
361
362 --
363 Best regards,
364 Stephan FERRARO
365 NOOFS Core Developper - http://www.noofs.org/
366 GnuPG public key: gpg --keyserver www.keyserver.net --recv-key 94B2664F

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
[gentoo-user] Re: emerge mc: undefined reference to `write_socket' Francesco Talamona <ti.liame@×××××.it>
Re: [gentoo-user] emerge mc: undefined reference to `write_socket' Rumen Yotov <gentoo@×××××××××××.org>